[ https://issues.apache.org/jira/browse/CASSANDRA-10302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-10302: ----------------------------------------- Component/s: Repair > Track repair state for more reliable repair > ------------------------------------------- > > Key: CASSANDRA-10302 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10302 > Project: Cassandra > Issue Type: Improvement > Components: Repair > 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