[
https://issues.apache.org/jira/browse/CASSANDRA-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045189#comment-15045189
]
Marcus Olsson commented on CASSANDRA-10070:
-------------------------------------------
I agree that it would probably be safer for node A to check how long it has
been down itself, but I'm not sure how that can be done reliably. But also if
node A & B couldn't communicate for a time period longer than the hint window
they will not have hints. So in that case they should do a repair even if both
were up the whole time.
Note that I'm not against having the check on the node that was down, it's just
that I think that both the case that a node was down and that two nodes was
unable to communicate should require a repair. If the second case is not
required do you have any suggestions on how the self-check could be implemented?
> Automatic repair scheduling
> ---------------------------
>
> Key: CASSANDRA-10070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10070
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Olsson
> Assignee: Marcus Olsson
> Priority: Minor
> Fix For: 3.x
>
>
> Scheduling and running repairs in a Cassandra cluster is most often a
> required task, but this can both be hard for new users and it also requires a
> bit of manual configuration. There are good tools out there that can be used
> to simplify things, but wouldn't this be a good feature to have inside of
> Cassandra? To automatically schedule and run repairs, so that when you start
> up your cluster it basically maintains itself in terms of normal
> anti-entropy, with the possibility for manual configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
