-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panicked when create table #559
Labels
Comments
@MachaelLee Maybe the commit id of the binary helps troubleshoot because the code location is wrong in the latest main branch. |
2023-03-14T02:31:10.846583855Z 2023-03-14 02:31:10.846 ERRO [common_util/src/panic.rs:42] thread 'ceres-write' panicked 'assertion failed: success' at "analytic_engine/src/space.rs:159"
2023-03-14T02:31:10.846590798Z 0: common_util::panic::set_panic_hook::{{closure}}
2023-03-14T02:31:10.846598388Z at ceresdb/common_util/src/panic.rs:41:18
2023-03-14T02:31:10.846603760Z 1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
2023-03-14T02:31:10.846610344Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/alloc/src/boxed.rs:2002:9
2023-03-14T02:31:10.846638988Z std::panicking::rust_panic_with_hook
2023-03-14T02:31:10.846646204Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/std/src/panicking.rs:692:13
2023-03-14T02:31:10.846651435Z 2: std::panicking::begin_panic_handler::{{closure}}
2023-03-14T02:31:10.846656365Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/std/src/panicking.rs:577:13
2023-03-14T02:31:10.846661186Z 3: std::sys_common::backtrace::__rust_end_short_backtrace
2023-03-14T02:31:10.846669922Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/std/src/sys_common/backtrace.rs:137:18
2023-03-14T02:31:10.846675231Z 4: rust_begin_unwind
2023-03-14T02:31:10.846679676Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/std/src/panicking.rs:575:5
2023-03-14T02:31:10.846683169Z 5: core::panicking::panic_fmt
2023-03-14T02:31:10.846689518Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/core/src/panicking.rs:64:14
2023-03-14T02:31:10.846692993Z 6: core::panicking::panic
2023-03-14T02:31:10.846695905Z at rustc/11d96b59307b1702fffe871bfc2d0145d070881e/library/core/src/panicking.rs:114:5
2023-03-14T02:31:10.846698880Z 7: analytic_engine::space::Space::insert_table
2023-03-14T02:31:10.846701684Z at ceresdb/analytic_engine/src/space.rs:159:9
2023-03-14T02:31:10.846704965Z 8: analytic_engine::instance::open::<impl analytic_engine::instance::Instance>::process_recover_table_command::{{closure}}
2023-03-14T02:31:10.846708301Z at ceresdb/analytic_engine/src/instance/open.rs:200:9
2023-03-14T02:31:10.846711635Z analytic_engine::instance::write_worker::WriteWorker::handle_recover_table::{{closure}}
2023-03-14T02:31:10.846714672Z at ceresdb/analytic_engine/src/instance/write_worker.rs:828:13
2023-03-14T02:31:10.846717503Z analytic_engine::instance::write_worker::WriteWorker::run::{{closure}}
2023-03-14T02:31:10.846720325Z at ceresdb/analytic_engine/src/instance/write_worker.rs:762:51
2023-03-14T02:31:10.846723184Z 9: analytic_engine::instance::write_worker::WriteGroup::new::{{closure}}
2023-03-14T02:31:10.846725951Z at ceresdb/analytic_engine/src/instance/write_worker.rs:619:29
2023-03-14T02:31:10.846729072Z 10: tokio::runtime::task::core::Core<T,S>::poll::{{closure}} A similar failed case, I guess this is the steps cause this issue:
Step 2 happens before server open table, then when step 1 open table A, it will panic at /// Insert table data into space memory state if the table is
/// absent. For internal use only
///
/// Panic if the table has already existed.
pub(crate) fn insert_table(&self, table_data: TableDataRef) {
let success = self
.table_datas
.write()
.unwrap()
.insert_if_absent(table_data);
assert!(success);
} A quickfix is to disable write/read request before server open all shards.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe this problem
Here is the stack
Steps to reproduce
I guess the table had been created and dropped for many times, then panicked when creating the table
Expected behavior
Create table successfully
Additional Information
None
The text was updated successfully, but these errors were encountered: