Reputation: 41
My team is using Apache Cassandra 3.0, not DSE, for our 10 node cluster. We have one DC and all nodes are 1 TB each. Right now all the nodes are around 300 GB occupied, The RF is 2. We have not run anti-entropy (manual) repair in a long time. The problem I am facing now is that I started repair on one of the nodes and it is taking forever. Is that normal? Also, the repair failed once and I am noticing increase in the disk space for that node, it is ~400GB now. how can I fix this behavior?
Upvotes: 1
Views: 1056
Reputation: 272
you can use nodetool repair -pr -full -pr will help node only repair the data range where it owns; -full will disable the incremental repair and like other people suggests, incremental repair is not a good fit
Upvotes: 0
Reputation: 16400
incremental repairs will not work in this scenario (default repairs). They have been meant to run from beginning so it never covers too much data. I would strongly recommend using sub range repairs - this can be a little difficult but can be automated with OpsCenters repair service or Reaper
Upvotes: 1