rust client return gRPC 'Connection timed out' when call scan_keys or batch_get api
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
issue detail:
thread 'CPU-worker' panicked at 'called Result::unwrap() on an Err value: Grpc(RpcFailure(RpcStatus { code: 14-UNAVAILABLE, message: "Connection timed out", details: [] }))', /home/qwm/src/fabarta-db/src/store/src/tikv/mod.rs:86:53
Rust Client timeout:
kv_timeout = 60
TiKV config:
[server]
grpc-concurrency = 4
grpc-keepalive-timeout = "10s"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at tikv/mod.rs:86 and trace the scan_keys and batch_get call paths that produce the unwrap panic. Review the Rust client's kv_timeout alongside the TiKV gRPC settings, then reproduce the UNAVAILABLE timeout. Done means the failure is explained and the affected call no longer times out or panics under the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100