[
https://issues.apache.org/jira/browse/CASSANDRA-9702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654981#comment-14654981
]
mlowicki commented on CASSANDRA-9702:
-------------------------------------
After upgrade to 2.1.8 we're seeing CASSANDRA-9935 instead.
> Repair running really slow
> --------------------------
>
> Key: CASSANDRA-9702
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9702
> Project: Cassandra
> Issue Type: Bug
> Environment: C* 2.1.7, Debian Wheezy
> Reporter: mlowicki
> Fix For: 2.1.x
>
> Attachments: db1.system.log
>
>
> We're using 2.1.x since the very beginning and we always had problem with
> failing or slow repair. In one data center we aren't able to finish repair
> for many weeks (partially because CASSANDRA-9681 as we needed to reboot nodes
> periodically).
> I've launched it today morning (12 hours now) and monitor using
> https://github.com/spotify/cassandra-opstools/blob/master/bin/spcassandra-repairstats.
> For the first hour it progressed to 9.43% but then it took ~10 hours to
> reach 9.44%. I see very rarely logs related to repair (each 15-20 minutes but
> sometimes nothing new for 1 hour).
> Repair launched with:
> {code}
> nodetool repair --partitioner-range --parallel --in-local-dc {keyspace}
> {code}
> Attached log file from today.
> We've ~4.1TB of data in 12 nodes with RF set to 3 (2 DC with 6 nodes each).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
