Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 29 May 2014 16:31:04 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12717290.1401381024194.39938.1401381064303@arcas>
In-Reply-To: <JIRA.12717290.1401381024194@arcas>
References: <JIRA.12717290.1401381024194@arcas>
Subject: [jira] [Created] (CASSANDRA-7320) Swap local and global default
 read repair chances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-7320:
--------------------------------------------

             Summary: Swap local and global default read repair chances
                 Key: CASSANDRA-7320
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7320
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Aleksey Yeschenko
            Assignee: Aleksey Yeschenko
             Fix For: 2.0.9, 2.1 rc1
         Attachments: 7320.txt

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.


--
This message was sent by Atlassian JIRA
(v6.2#6252)