after br restored point failure, tikv crashed #14338
Labels
Comments
|
/severity critical |
This was referenced Mar 4, 2023
Merged
ti-chi-bot
pushed a commit
that referenced
this issue
Mar 4, 2023
close #14338 Signed-off-by: Qi Xu <tonyxuqqi@outlook.com> Co-authored-by: Qi Xu <tonyxuqqi@outlook.com>
16 tasks
|
/close |
|
@tonyxuqqi: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What version of TiKV are you using?
TiKV
Release Version: 6.5.1
Edition: Community
Git Commit Hash: 112123e
Git Commit Branch: heads/refs/tags/v6.5.0-nightly
UTC Build Time: 2023-03-02 11:06:54
Rust Version: rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Enable Features: pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile: dist_release
What operating system and CPU are you using?
Steps to reproduce
br restore pointfailedWhat did you expect?
tikv ok
What did happened?
{"container":"tikv","namespace":"pitr-testbed-47w8x","log":"[server.rs:1101] ["failed to start node: Engine(Other(\"[components/raftstore/src/store/fsm/store.rs:1166]: \\\"[components/raftstore/src/store/entry_storage.rs:522]: [region 969099] entry at 60 doesn't exist, may lose data.\\\"\"))"]","pod":"downstream-tikv-6","level":"FATAL"}
The text was updated successfully, but these errors were encountered: