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.

Sign up for GitHub

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

Jump to bottom

Add a setting to activate read-repairs #257

Open
iksaif opened this issue Mar 29, 2017 · 3 comments
Open

Add a setting to activate read-repairs #257

iksaif opened this issue Mar 29, 2017 · 3 comments
Milestone
v0.11.0

Comments

@iksaif
Copy link
Contributor

iksaif commented Mar 29, 2017

Also set compaction options accordingly when doing it. Read repairs will write in the past which means that we need to set these correctly:

  • tombstone_threshold (something high, like 80%)
  • tombstone_compaction_interval (something higher than TTL + gc_grace_period)
@iksaif
Copy link
Contributor Author

iksaif commented Apr 6, 2017

This should probably only be set once we've fixed issues on Cassandra with overlapping fully expired sstables.

@iksaif
Copy link
Contributor Author

iksaif commented Aug 2, 2017

These is a patch for overlapping sstables available on https://issues.apache.org/jira/browse/CASSANDRA-13418

@iksaif iksaif modified the milestones: v0.10.0, v0.11.0 Dec 19, 2017
@iksaif
Copy link
Contributor Author

iksaif commented Jan 31, 2018

Patch is in 3.11.1, so we're good. Now we need to at least write doc on how to configure read repairs.

@Roguelazer Roguelazer mentioned this issue Feb 1, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.11.0
Development

No branches or pull requests
1 participant
@iksaif