total tiflash 2 node oom, and cannot restart success
Open
Nobody has claimed this yet.
component/storage
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
may-affects-8.5
severity/major
type/bug
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
try start tiflash node, but restart failed (display is timeout cause start failed)
tiup cluster start cluster_name -N tiflash_1_ip:tiflash_1_port, tiflash_2_ip:tiflash_2_port, --wait-timeout=600
2. What did you expect to see? (Required)
start tiflash success~
3. What did you see instead (Required)
start failed..., and get error log ~
[2023/10/30 21:55:54.648 +08:00] [ERROR] [peer.rs:5327] ["failed to send extra message"] [err_code=KV:Raftstore:Transport] [err=Transport(Full)] [target="id: 5583162 store_i
d: 76 role: Learner"] [peer_id=5581865] [region_id=2876545] [type=MsgRegionWakeUp]
[2023/10/30 21:55:54.648 +08:00] [ERROR] [peer.rs:5327] ["failed to send extra message"] [err_code=KV:Raftstore:Transport] [err=Transport(Full)] [target="id: 188195843 store_id: 76 role: Learner"] [peer_id=188195842] [region_id=188195841] [type=MsgRegionWakeUp]
[2023/10/30 21:55:54.648 +08:00] [ERROR] [peer.rs:5327] ["failed to send extra message"] [err_code=KV:Raftstore:Transport] [err=Transport(Full)] [target="id: 1059335362 store_id: 76 role: Learner"] [peer_id=1059335363] [region_id=1059335361] [type=MsgRegionWakeUp]
[2023/10/30 21:55:54.648 +08:00] [ERROR] [peer.rs:5327] ["failed to send extra message"] [err_code=KV:Raftstore:Transport] [err=Transport(Full)] [target="id: 198476291 store_id: 76 role: Learner"] [peer_id=198476290] [region_id=198476289] [type=MsgRegionWakeUp]
[2023/10/30 21:55:54.664 +08:00] [INFO] [region.rs:103] [" 77:3811747 5411142, peer created"] [is_replicated=false] [role=Follower] [leader_id=254092920] [region_id=3811747]
[2023/10/30 21:55:54.664 +08:00] [INFO] [region.rs:103] [" 77:3839423 5452317, peer created"] [is_replicated=false] [role=Follower] [leader_id=3852964] [region_id=3839423]
[2023/10/30 21:55:54.664 +08:00] [INFO] [region.rs:103] [" 77:3043750 5577411, peer created"] [is_replicated=false] [role=Follower] [leader_id=3055865] [region_id=3043750]
[2023/10/30 21:55:54.664 +08:00] [INFO] [region.rs:103] [" 77:813816241 813816243, peer created"] [is_replicated=false] [role=Follower] [leader_id=1061079565] [region_id=813
816241]
4. What is your TiFlash version? (Required)
7.1.0
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 by reproducing the failed restart with the provided tiup cluster start command on TiFlash 7.1.0. Read the peer.rs and region.rs log entries around Transport(Full), node OOM, and restart timeout; done means identifying a supported cause and restoring successful startup for both TiFlash nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100