forked from cockroachdb/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
35 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
title: Technical Advisory 48860 | ||
summary: Data corruption/loss issue with snapshots and delete range | ||
toc: true | ||
--- | ||
|
||
Publication date: May 20, 2020. | ||
|
||
## Description | ||
|
||
Range deletions (as caused by certain [table drops](../v20.1/drop-table.html), [table truncates](../v20.1/truncate.html), and certain rebalancing operations during [node decommissioning](../v20.1/remove-nodes.html) or failover), when occurring concurrently with replica [garbage collection](../v20.1/architecture/storage-layer.html#garbage-collection), can yield permanent data corruption or loss in rare cases. | ||
|
||
## Statement | ||
|
||
A defect in RocksDB allowed it to violate its guarantees for snapshots, causing corruption under specific and extremely rare circumstances. This corruption is irrecoverable using regular node failover and must be addressed by restoring a backup when it occurs. | ||
|
||
This bug has been fixed in versions v19.1.9, v19.2.7, and v20.1.0. All users are encouraged to upgrade (see [Mitigation](#mitigation) below). | ||
|
||
The public issue is tracked as [#48860](https://github.com/cockroachdb/cockroach/issues/48860). | ||
|
||
## Mitigation | ||
|
||
There is no mitigation possible without an upgrade. Cockroach Labs recommends that customers upgrade to the latest release of [v19.1](../v19.1/upgrade-cockroach-version.html), [v19.2](../v19.2/upgrade-cockroach-version.html), or [v20.1](../v20.1/upgrade-cockroach-version.html), all of which are currently under [Maintenance Support](../releases/release-support-policy.html#support-cycle). | ||
|
||
Because CockroachDB v2.1 will reach [End of Life](../releases/release-support-policy.html#support-cycle) on July 1, 2020, no new maintenance release for v2.1 will be issued containing a fix for this bug. Affected deployments running v2.1 should be upgraded to at least the latest release of [v19.1](../v19.1/upgrade-cockroach-version.html). | ||
|
||
## Impact | ||
|
||
All CockroachDB v2.x and v19.x releases up to and including v19.1.8 and v19.2.6 are affected. When encountered, the bug causes data corruption or loss. | ||
|
||
Questions about any technical alert can be directed to our [support team](https://support.cockroachlabs.com/). |