Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v6.5.1 lightning import data to master fail for pd reset the connection #6099

Closed
seiya-annie opened this issue Mar 7, 2023 · 6 comments · Fixed by #6128
Closed

v6.5.1 lightning import data to master fail for pd reset the connection #6099

seiya-annie opened this issue Mar 7, 2023 · 6 comments · Fixed by #6128
Labels

Comments

@seiya-annie
Copy link

Bug Report

What did you do?

tidb cluster upgrade from 6.0.0 to 6.5.1-pre
import data to 6.0.0 cluster using 6.5.1 lightning

What did you expect to see?

import success

What did you see instead?

import fail
print many warning:
{"level":"warn","ts":"2023-03-07T03:08:03.956Z","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000c22380/src-tidb-pd.fb-testbed-comp-2nrpj:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing dial tcp 10.244.7.55:2379: connect: connection refused""}

What version of PD are you using (pd-server -V)?

v6.5.1-pre

@seiya-annie seiya-annie added the type/bug The issue is confirmed as a bug. label Mar 7, 2023
@seiya-annie
Copy link
Author

@seiya-annie
Copy link
Author

@seiya-annie
Copy link
Author

pingcap/tidb#41973

@bufferflies
Copy link
Contributor

bufferflies commented Mar 8, 2023

image

the restart related log :

[2023/03/06 16:56:27.610 +00:00] [INFO] [region.go:679] ["region Version changed"] [region-id=8021] [detail="StartKey Changed:{7480000000000007FFA300000000000000F8} -> {7480000000000007FFA35F728000000000FF27AC410000000000FA}, EndKey:{748000FFFFFFFFFFFFF900000000000000F8}"] [old-version=1056] [new-version=1059]
[2023/03/06 16:56:44.671 +00:00] [INFO] [versioninfo.go:89] ["Welcome to Placement Driver (PD)"]
[2023/03/06 16:56:44.671 +00:00] [INFO] [versioninfo.go:90] [PD] [release-version=v6.7.0-alpha]

@bufferflies
Copy link
Contributor

upstream version:

branch: master
git-hash=bc5234cf4fc81050ed8352aa19293f088798491b]

down stream:

branch: release-6.5
git-hash= 51f382c73ee7bff691874cd44b07ca0a51e2dc73

@nolouch
Copy link
Contributor

nolouch commented Mar 9, 2023

panic

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1e36ed8]

goroutine 3556 [running]:
github.com/tikv/pd/server/schedule.allowLeader(0x2958800?, 0xc00262c1e0?)
	/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/server/schedule/region_scatterer.go:410 +0x58
github.com/tikv/pd/server/schedule.(*RegionScatterer).scatterRegion.func1(0x2956e20?, {{0xc00185ca70, 0x2, 0x2}, 0xc0005f8aa0, 0xc0005f8ac0})
	/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/server/schedule/region_scatterer.go:348 +0x40e
github.com/tikv/pd/server/schedule.(*RegionScatterer).scatterRegion(0xc00087c680, 0xc0023e0700, {0x0, 0x0})
	/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/server/schedule/region_scatterer.go:357 +0x6db
github.com/tikv/pd/server/schedule.(*RegionScatterer).Scatter(0xc00087c680, 0xc0023e0700, {0x0, 0x0})
	/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/server/schedule/region_scatterer.go:301 +0x228
github.com/tikv/pd/server.(*GrpcServer).ScatterRegion(0xc0015080d0, {0x39e53f8?, 0xc00262c0f0?}, 0xc0006679d0)
	/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/server/grpc_service.go:1336 +0x365
github.com/pingcap/kvproto/pkg/pdpb._PD_ScatterRegion_Handler.func1({0x39e53f8, 0xc00262c0f0}, {0x2baa840?, 0xc0006679d0})
	

the root cause:

rule := fit.GetRuleFit(peer.GetId()).Rule
if rule.IsWitness {
return false
}

the peer maybe not in the rule.

ti-chi-bot pushed a commit that referenced this issue Mar 9, 2023
…gion is unhealthy (#6128)

close #6099

Signed-off-by: HunDunDM <hundundm@gmail.com>
ti-chi-bot added a commit that referenced this issue Mar 9, 2023
…gion is unhealthy (#6128) (#6129)

close #6099, ref #6128

Signed-off-by: HunDunDM <hundundm@gmail.com>

Co-authored-by: HunDunDM <hundundm@gmail.com>
ti-chi-bot added a commit that referenced this issue Mar 13, 2023
ref #6099

add defer logs the panic reason and stack

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Mar 13, 2023
ref tikv#6099

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Mar 13, 2023
ref tikv#6099

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot added a commit that referenced this issue Mar 29, 2023
ref #6099, ref #6123

add defer logs the panic reason and stack

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
ti-chi-bot bot added a commit that referenced this issue May 15, 2023
ref #6099, ref #6123

add defer logs the panic reason and stack

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
Co-authored-by: Hu# <jinhao.hu@pingcap.com>
Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants