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.1.2
ubuntu
Run Jepsen test configured with the set workload and the kill/pause/partition nemesis.
No fatal
./tikv set/20230330T224351.032Z/n2/kv.log:[2023/03/30 22:54:59.466 +00:00] [FATAL] [server.rs:955] ["failed to start node: Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "not leader", details: [] }))"]
The text was updated successfully, but these errors were encountered:
While starting the server, we also got another fatal: [FATAL] [main.go:117] ["run server failed"] [error="[PD:etcd:ErrEtcdKVGet]rpc error: code = Unknown desc = context deadline exceeded: rpc error: code = Unknown desc = context deadline exceeded"] [stack="main.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/cmd/pd-server/main.go:117\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"]
[FATAL] [main.go:117] ["run server failed"] [error="[PD:etcd:ErrEtcdKVGet]rpc error: code = Unknown desc = context deadline exceeded: rpc error: code = Unknown desc = context deadline exceeded"] [stack="main.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/pd/cmd/pd-server/main.go:117\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"]
Sorry, something went wrong.
No branches or pull requests
Bug Report
What version of TiKV are you using?
V6.1.2
What operating system and CPU are you using?
ubuntu
Steps to reproduce
Run Jepsen test configured with the set workload and the kill/pause/partition nemesis.
What did you expect?
No fatal
What happened?
./tikv set/20230330T224351.032Z/n2/kv.log:[2023/03/30 22:54:59.466 +00:00] [FATAL] [server.rs:955] ["failed to start node: Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "not leader", details: [] }))"]
The text was updated successfully, but these errors were encountered: