cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1511) log when a "repair" operation completes
Date Thu, 23 Sep 2010 20:55:35 GMT


Stu Hood updated CASSANDRA-1511:

    Attachment: 0004-Execute-TREE_RESPONSE-verbs-in-the-proper-stage-fixe.patch

0001 Waits to mark repair requests completed until all streams have completed
0002 Logs repair session completion even if the client thread dies
0003 Makes repair sessions less noisy
0004 Fixes a race in rendezvous (but unfortunately doesn't fix 1028... argh)

Tested on two nodes: ready for review.

> log when a "repair" operation completes
> ---------------------------------------
>                 Key: CASSANDRA-1511
>                 URL:
>             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
>         Attachments: 0001-Adds-Differencer.CompletionCallback-which-is-notifie.patch,
0002-Repair-sessions-are-collected-on-completion-by-Repai.patch, 0003-Add-a-limited-string-join-function-to-prevent-dumpin.patch,
> 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.

View raw message