Introduce quorum-based chunk deduplication strategy #68
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.
This chunk dedup strategy is specific to Databricks' setup where each time series is written to at least 2 out of 3 replicas. Each chunk should have 3 replicas in most cases, and 2 replicas in the worst acceptable cases. Quorum-based deduplication is used to pick the majority value among 3 replicas. If a chunck has only 2 identical replicas, there might be another chunk with corrupt data. We want to send those two identical replicas to the later quorum-based deduplication process to dominate any corrupt third replica.
Unit test
Integration test with the new feature