[CASSANDRA-7320] Swap local and global default read repair chances

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.9, 2.1 rc1
• Assignee: Aleksey Yeschenko
• Reporter: Aleksey Yeschenko

Authors

Aleksey Yeschenko

Reviewers

Jason Brown

• Created: 29/May/14 16:30
• Updated: 16/Apr/19 09:31
• Resolved: 29/May/14 16:58

Description

See the discussion in CASSANDRA-6887 on why.

Sylvain: "instead of having read_repair_chance=0.1 and dclocal_read_repair_chance=0, to switch to read_repair_chance=0 and dclocal_read_repair_chance=0.1. If you have only one DC, then it won't change from the current default, and if you have multiple-DC, I can agree that not crossing DC boundaries for read repair is a better default."

Not basing on 1.2 because it's rather late for that. Not too late for the 2.0 cycle though, so setting fixver to 2.0.9.

Issue Links

• is duplicated by: CASSANDRA-6866 Read repair path of quorum reads makes cluster to timeout all requests under load