You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/05/19 02:05:00 UTC

[jira] [Resolved] (CASSANDRA-7989) "nodetool repair" goes to infinite repair, continue beyond the number of tokens handled in a single repair.

     [ https://issues.apache.org/jira/browse/CASSANDRA-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip Thompson resolved CASSANDRA-7989.
----------------------------------------
    Resolution: Cannot Reproduce

No response from reporter for 2 months. Closing as Cannot Reproduce. Please re-open if you can reproduce the issue.

> "nodetool repair" goes to infinite repair, continue beyond the number of tokens handled in a single repair. 
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7989
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7989
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Andrew Johnson
>            Priority: Minor
>             Fix For: 2.0.x
>
>
> DSE 4.0.3 with patch (Cassandra 2.0.9.61)
> Percentage reported stays in 99.999%
> We are computing % complete by
> [ (Current token processed - initial token processed) / (# of token handled by this node) ] * 100 = xx.xx %
> In this case, it goes beyond 100% meaning numerator(repaired number of tokens in this session) is greater than the number of tokens handled by this node (5624 in this node), we caught this and report 99.999%
> AntiEntropySession increments and there are no visible errors nor exceptions in the log once it was stabilized, also a sub process neither terminated nor finished. 
> (Note, when this session started, there were many exceptions - snapshot creation - causing a sub process to be terminated and restarted about 5 times within a hour but once it is stabilized, it kept going since Aug 22.)



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