Skip to content

[state sync] Node crashes if stopped during state sync #12910

Open
@VanBarbascu

Description

2025-01-31T05:49:07.047462Z  INFO actix_server::accept: Accept thread stopped
2025-01-31T05:49:07.112760Z  INFO neard: Waiting for RocksDB to gracefully shutdown
2025-01-31T05:49:07.112806Z  INFO db: Waiting for remaining RocksDB instances to close num_instances=2
thread 'tokio-runtime-worker' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.29.1/src/runtime/blocking/shutdown.rs:51:21:
Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: <tokio::runtime::blocking::pool::BlockingPool as core::ops::drop::Drop>::drop
   3: core::ptr::drop_in_place<tokio::runtime::runtime::Runtime>
   4: alloc::sync::Arc<T,A>::drop_slow
   5: alloc::sync::Arc<T,A>::drop_slow
   6: near_client::sync::state::shard::run_state_sync_for_shard::{{closure}}
   7: near_client::sync::state::StateSync::run::{{closure}}
   8: tokio::runtime::task::raw::poll
   9: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  10: tokio::runtime::task::raw::poll


Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions