[
https://issues.apache.org/jira/browse/CASSANDRA-10302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654152#comment-16654152
]
Tania S Engel commented on CASSANDRA-10302:
-------------------------------------------
Is there any hope that there will be better repair tracking in 4.0. It really
would be wonderful to have a nodetool command to see any active running repairs
(by the ActiveRepairService?). In our small test cluster of 3, nodetool repair
typically takes 2 minutes, but with a stream failure it can hang, and 13 hours
later you are left wondering.
> Track repair state for more reliable repair
> -------------------------------------------
>
> Key: CASSANDRA-10302
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10302
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Yuki Morishita
> Assignee: Yuki Morishita
> Priority: Major
>
> During repair, coordinator and replica exchange various messages. I've seen
> cases that those messages sometimes get lost.
> We've made repair message to be more durable (CASSANDRA-5393, etc) but still
> messages seem to be lost and hang repair till messaging timeout reaches.
> We can prevent this by tracking repair status on repair participants, and
> periodically check state after certain period of times to make sure
> everything is working fine.
> We alse can add command / JMX API to query repair state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
