TiFlash unexpectedly crashes
Nobody has claimed this yet.
- 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)
I don't known how it happens, tiflash runs as usual, but it suddenly crashed. logs as below:
the only fatal log copied as this:
[2025/04/26 21:46:46.086 +08:00] [FATAL] [lib.rs:510] ["called `Option::unwrap()` on a `None` value"] [backtrace=" 0: tikv_util::set_panic_hook::{{closure}}\n 1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/boxed.rs:2032:9\n std::panicking::rust_panic_with_hook\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:692:13\n 2: std::panicking::begin_panic_handler::{{closure}}\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:577:13\n 3: std::sys_common::backtrace::__rust_end_short_backtrace\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/sys_common/backtrace.rs:137:18\n 4: rust_begin_unwind\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/panicking.rs:575:5\n 5: core::panicking::panic_fmt\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/core/src/panicking.rs:65:14\n 6: core::panicking::panic\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/core/src/panicking.rs:114:5\n 7: <raftstore::coprocessor::region_info_accessor::RegionCollector as tikv_util::worker::pool::Runnable>::run\n 8: yatp::task::future::RawTask<F>::poll\n 9: <yatp::task::future::Runner as yatp::pool::runner::Runner>::handle\n 10: std::sys_common::backtrace::__rust_begin_short_backtrace\n 11: core::ops::function::FnOnce::call_once{{vtable.shim}}\n 12: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/boxed.rs:2000:9\n <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/boxed.rs:2000:9\n std::sys::unix::thread::Thread::new::thread_start\n at rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/std/src/sys/unix/thread.rs:108:17\n 13: start_thread\n 14: __GI___clone3\n"] [location=/rustc/96ddd32c4bfb1d78f0cd03eb068b1710a8cebeef/library/alloc/src/collections/btree/navigate.rs:73] [thread_name=region-collector-worker-0]
it seems that be related with tikv, but i don't find error about tiflash in tikv logs.
2. What did you expect to see? (Required)
tiflash runs normally.
3. What did you see instead (Required)
tiflash crashes unexpectedly.
4. What is your TiFlash version? (Required)
v7.5.2 deployed in k8s by tidb operator v1.5.3.
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 with the captured RegionCollector worker stack trace, especially the RegionCollector::run frame, lib.rs:510, and the BTree navigation location. Correlate those locations with the TiFlash v7.5.2 and TiKV logs from the Kubernetes deployment. Done means reproducing or isolating the unexpected crash and adding evidence that identifies its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- 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