Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <23679861.74001277557730335.JavaMail.jira@thor>
Date: Sat, 26 Jun 2010 09:08:50 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1190) Remove automatic repair sessions
In-Reply-To: <6550134.86791276552033016.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882834#action_12882834 ] 

Hudson commented on CASSANDRA-1190:
-----------------------------------

Integrated in Cassandra #477 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/477/])
    allow multiple repair sessions per node.  patch by Stu Hood; reviewed by jbellis for CASSANDRA-1190


> Remove automatic repair sessions
> --------------------------------
>
>                 Key: CASSANDRA-1190
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1190
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 0.6.3, 0.7
>
>         Attachments: 0001-Remove-natural-repair-throttling-in-preparation-for-.patch, 0002-Rename-readonly-compaction-to-validation-and-make-it.patch, 0003-Add-session-info-to-RPCs-to-handle-concurrent-repair.patch, for-0.6-0001-Remove-natural-repair-throttling-in-preparation-for-.patch, for-0.6-0002-Rename-readonly-compaction-to-validation-and-make-it.patch
>
>
> Currently both manual and automatic repair sessions use the same timeout value: TREE_STORE_TIMEOUT. This has the very negative effect of setting a maximum time that compaction can take before a manual repair will fail.
> For automatic/natural repairs (triggered by two nodes autonomously finishing major compactions around the same time), you want a relatively low TREE_STORE_TIMEOUT value, because trees generated a long time apart will cause a lot of unnecessary repair. The current value is 10 minutes, to optimize for this case.
> On the other hand, for manual repairs, TREE_STORE_TIMEOUT needs to be significantly higher. For instance, if a manual repair is triggered for a source node A storing 2 TB of data, and a destination node B with an empty store, then node B needs to wait long enough for node A to finish compacting 2 TB of data, which might take > 12 hours. If a node B times out the local tree before node A sends its tree, then the repair will not occur.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.