Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <7673955.240601284677195350.JavaMail.jira@thor>
Date: Thu, 16 Sep 2010 18:46:35 -0400 (EDT)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1511) log when a "repair" operation
 completes
In-Reply-To: <3774674.234721284661473401.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-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910374#action_12910374 ] 

Stu Hood commented on CASSANDRA-1511:
-------------------------------------

I think removing automatic repair sessions broke 1090, since the local node requests a stream from each remote node, but it can't block for the stream to complete.

> log when a "repair" operation completes
> ---------------------------------------
>
>                 Key: CASSANDRA-1511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1511
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Robert Coli
>            Assignee: Stu Hood
>            Priority: Trivial
>             Fix For: 0.7.0
>
>
> Operators who run "repair" operations need to know when they are completed. Nickmbailey suggests that this depends on his work to add callbacks for streaming operations. When this is done, a simple log message at level INFO when all differencers are done would be of use!

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