A node whose bootstrap or replace fails is rolled back by the topology coordinator through left_token_ring, and finish_left_token_ring_transition removes it from group0 and bans it. The joining node is racing that: it either observes its own failed request and aborts startup with the message the test expects, or receives the ban notification first and terminates on that instead. Both are legitimat…
A node whose bootstrap or replace fails is rolled back by the topology coordinator through left_token_ring, and finish_left_token_ring_transition removes it from group0 and bans it. The joining node is racing that: it either observes its own failed request and aborts startup with the message the test expects, or receives the ban notification first and terminates on that instead. Both are legitimat…
Update ScyllaDB version to: 2026.2.7
Update ScyllaDB version to: 2026.2.7
Merge '[Backport 2026.1] group0: fix voter deadlock on graceful leade…
Merge '[Backport 2026.1] group0: fix voter deadlock on graceful leade…
Adds the upgrade guide, including the updated metrics. Fixes SCYLLADB-3991 Fixes SCYLLADB-3992 Closes #30941 (cherry picked from commit 558ced9) Closes #31339
Adds the upgrade guide, including the updated metrics. Fixes SCYLLADB-3991 Fixes SCYLLADB-3992 Closes #30941 (cherry picked from commit 558ced9) Closes #31339
Merge '[Backport 2026.2] utils/gcp: drain in-flight requests before c…
Merge '[Backport 2026.2] utils/gcp: drain in-flight requests before c…
compaction: register backlog tracker of compaction groups created aft…
compaction: register backlog tracker of compaction groups created aft…
compaction: register backlog tracker of compaction groups created aft…
compaction: register backlog tracker of compaction groups created aft…
Update ScyllaDB version to: 2026.3.0-rc3
Update ScyllaDB version to: 2026.3.0-rc3
Update pgo profiles - aarch64
Update pgo profiles - aarch64
When incremental compaction is enabled, compaction runs a second "garbage collection" writer alongside the regular one. Its sealed output is parked in _unused_garbage_collected_sstables and is only ever attached to the table - and therefore only ever deleted afterwards - by maybe_replace_exhausted_sstables_by_sst(), which consumes that vector behind a guard: auto exhausted = std::partition(_sstabl…
When incremental compaction is enabled, compaction runs a second "garbage collection" writer alongside the regular one. Its sealed output is parked in _unused_garbage_collected_sstables and is only ever attached to the table - and therefore only ever deleted afterwards - by maybe_replace_exhausted_sstables_by_sst(), which consumes that vector behind a guard: auto exhausted = std::partition(_sstabl…
Merge '[Backport 2026.2] Add CodeRabbit configuration' from Scylladb[…
Merge '[Backport 2026.2] Add CodeRabbit configuration' from Scylladb[…
Merge '[Backport 2026.3] Add CodeRabbit configuration' from Scylladb[…
Merge '[Backport 2026.3] Add CodeRabbit configuration' from Scylladb[…
Commit 9b4c37d ("streaming: pass sstable metadata in stream_blob_meta and clone_sstable_request") appended a new optional member, sstable_meta, to the stream_blob_meta IDL class, which is the argument of the STREAM_BLOB (verb 71) RPC used by file-stream based tablet migration. The member was added without a [[version]] attribute. stream_blob_meta is a non-final (size-framed) IDL class. During dese…
Commit 9b4c37d ("streaming: pass sstable metadata in stream_blob_meta and clone_sstable_request") appended a new optional member, sstable_meta, to the stream_blob_meta IDL class, which is the argument of the STREAM_BLOB (verb 71) RPC used by file-stream based tablet migration. The member was added without a [[version]] attribute. stream_blob_meta is a non-final (size-framed) IDL class. During dese…
In b632316 we fixed an issue in the view_update_generator shutdown procedure where _progress_tracker could be accessed by external callers in process_staging_sstables after it's been destroyed. The admission of external calls and the access to _progress_tracker is now protected by the gate in view_update_generator, which is closed in drain(). This would have fixed the issue under the assumption th…
In b632316 we fixed an issue in the view_update_generator shutdown procedure where _progress_tracker could be accessed by external callers in process_staging_sstables after it's been destroyed. The admission of external calls and the access to _progress_tracker is now protected by the gate in view_update_generator, which is closed in drain(). This would have fixed the issue under the assumption th…
When the index is being built, the ann request returns HTTP 503. So far we treated this as a regular response and forward this back to the client. However the index may return 503 in two different scenarios: The node is SERVING but the index is still being built after creation. The node is BOOTSTRAPPING and not yet ready to serve requests. In the first case treating 503 as a regular response is co…
When the index is being built, the ann request returns HTTP 503. So far we treated this as a regular response and forward this back to the client. However the index may return 503 in two different scenarios: The node is SERVING but the index is still being built after creation. The node is BOOTSTRAPPING and not yet ready to serve requests. In the first case treating 503 as a regular response is co…