docs: add known issue for read repair writing partial objects - #520
Merged
Conversation
Read repair could use a partial view of an object as the source of truth and write it back to the replicas being repaired, so those replicas kept only the properties the query returned and lost the object's vector. The object, its ID and aggregate counts all survive, which is what makes the loss easy to miss. Fixed in 1.37.14 and 1.38.7, and present in every 1.39 release. The 1.36 line and earlier were never patched and now fall outside the supported version range. The entry states that a cluster reporting fully in-sync replicas is not exempt: the problem has been observed where background synchronization had already brought every replica up to date.
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the read-repair defect fixed in 1.37.14 and 1.38.7, where a partial view of an object could be written back to the replicas being repaired, leaving them with only the properties the query returned and no vector. The object, its ID and aggregate counts all survive, so the loss does not show up in a count or an existence check, which is what the entry leads with.
Two deliberate choices worth a reviewer's eye. The affected range is the wider one from the upgrade advisory rather than the narrower range the fix PR measured, erring toward over-warning. And the entry does not scope exposure to lagging replicas, because the fix PR recorded damage on replicas that were fully caught up: a bullet implying async replication protects you was removed.