spacejam/sled

panic: cannot find pid in view_for_key, looking for key

jpds opened this issue · 0 comments

jpds commented

I hit this panic using Sled as the backend on one of my Garage clusters:

======== PANIC (internal Garage error) ========
panicked at 'cannot find pid 253041 in view_for_key, looking for key [0, 115, 111] in tree', .cargo/registry/src/github.com-1ecc6299db9ec823/sled-0.34.7/src/tree.rs:1767:9

Panics are internal errors that Garage is unable to handle on its own.
They can be caused by bugs in Garage's code, or by corrupted data in
the node's storage. If you feel that this error is likely to be a bug
in Garage, please report it on our issue tracker a the following address:

        https://git.deuxfleurs.fr/Deuxfleurs/garage/issues

Please include the last log messages and the the full backtrace below in
your bug report, as well as any relevant information on the context in
which Garage was running when this error occurred.

GARAGE VERSION: git:v0.8.1-196-g703ac43-modified [features: k2v, sled, metrics, bundled-libs]

BACKTRACE:
   0: garage::main::{{closure}}::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys_common::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: sled::tree::Tree::view_for_key
   7: sled::tree::Tree::get_inner
   8: sled::transaction::TransactionalTree::get
   9: <garage_db::sled_adapter::SledTx as garage_db::ITx>::get
  10: garage_table::merkle::MerkleUpdater<F,R>::read_node_txn
  11: garage_table::merkle::MerkleUpdater<F,R>::update_item_rec
  12: garage_table::merkle::MerkleUpdater<F,R>::update_item_rec
  13: <garage_db::TxFn<F,R,E> as garage_db::ITxFn>::try_on
  14: <garage_db::sled_adapter::SledDb as garage_db::IDb>::transaction
  15: tokio::runtime::task::raw::poll
  16: std::sys_common::backtrace::__rust_begin_short_backtrace
  17: core::ops::function::FnOnce::call_once{{vtable.shim}}
  18: std::sys::unix::thread::Thread::new::thread_start
  19: <unknown>

This was previously reported at #1039 but is still present in the latest sled release.