cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajanarayanan Thottuvaikkatumana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8228) Log malfunctioning host on prepareForRepair
Date Thu, 13 Nov 2014 18:30:33 GMT

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

Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-8228:
-------------------------------------------------------------

Apart from the endpoint host addresses, we can also print the repair message details as well.
Each repair messages are not fatty and will be in the following form with the corresponding
end point host address appended to it. 

{code}
"PrepareMessage{" +
                "cfIds='" + cfIds + '\'' +
                ", ranges=" + ranges +
                ", parentRepairSession=" + parentRepairSession +
                ", isIncremental="+isIncremental +
                '}'
{code}

Thanks

> 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
>            Priority: Trivial
>              Labels: lhf
>
> 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