Skip to content
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

Bug: Data directory is already used by another cluster with id "cbe8cac7-e873-461b-85c6-df8d8604600b", path hummock_001/cluster_id/0.) #16819

Closed
kwannoel opened this issue May 20, 2024 · 1 comment · Fixed by #16820
Labels
Milestone

Comments

@kwannoel
Copy link
Contributor

Describe the bug

Error Message: Data directory is already used by another cluster with id "cbe8cac7-e873-461b-85c6-df8d8604600b", path hummock_001/cluster_id/0.).

This is seen when upgrading a cluster from v1.9 to the latest main, via risedev.

Error message/log

called `Result::unwrap()` on an `Err` value: ObjectStore(Internal error: Data directory is already used by another cluster with id "cbe8cac7-e873-461b-85c6-df8d8604600b", path hummock_001/cluster_id/0.)
stack backtrace:
   0: rust_begin_unwind
             at /rustc/4a0cc881dcc4d800f10672747f61a94377ff6662/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /rustc/4a0cc881dcc4d800f10672747f61a94377ff6662/library/core/src/panicking.rs:72:14
   2: core::result::unwrap_failed
             at /rustc/4a0cc881dcc4d800f10672747f61a94377ff6662/library/core/src/result.rs:1654:5
   3: unwrap<alloc::sync::Arc<risingwave_meta::hummock::manager::HummockManager, alloc::alloc::Global>, risingwave_meta::hummock::error::Error>
             at /rustc/4a0cc881dcc4d800f10672747f61a94377ff6662/library/core/src/result.rs:1077:23
   4: {async_fn#0}
             at ./src/meta/node/src/server.rs:480:27
   5: {async_block#1}
             at ./src/meta/node/src/server.rs:336:10

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant