cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8228) Log malfunctioning host on prepareForRepair
Date Fri, 14 Nov 2014 22:03:34 GMT

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

Yuki Morishita edited comment on CASSANDRA-8228 at 11/14/14 10:03 PM:
----------------------------------------------------------------------

[~rnamboodiri] I suggest to build message for failed node inside {{onFailure}} method of IAsyncCallbackWithFailure
(in thread-safe way).
So you can tell precisely which nodes are failed.


was (Author: yukim):
[~rnamboodiri] I suggest to build message for failed node inside ((onFailure}} method of IAsyncCallbackWithFailure
(in thread-safe way).
So you can tell precisely which nodes are failed.

> Log malfunctioning host on prepareForRepair
> -------------------------------------------
>
>                 Key: CASSANDRA-8228
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8228
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Juho Mäkinen
>            Assignee: Rajanarayanan Thottuvaikkatumana
>            Priority: Trivial
>              Labels: lhf
>         Attachments: cassandra-trunk-8228.txt
>
>
> Repair startup goes thru ActiveRepairService.prepareForRepair() which might result with
"Repair failed with error Did not get positive replies from all endpoints." error, but there's
no other logging regarding to this error.
> It seems that it would be trivial to modify the prepareForRepair() to log the host address
which caused the error, thus ease the debugging effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message