It was the long time since last repair that did it. We've scheduled regular
repairs now, and this time the repairs didn't increase the load very much.
So that was it! :-)
/Henrik
On Thu, Nov 8, 2012 at 7:20 PM, Andrey Ilinykh wrote:
> Nothing unusual. When you run repair cassandra streams inc
No, we haven't changed RF, but it's been a very long time since we repaired
last, so we're guessing this is an effect of not running repair regularly,
and that doing it regularly will fix it. It would just be nice to know.
Also, running major compaction after the repair made the data size shrink
b
Did you change the RF or had a node down since you repaired last time ?
2012/11/8 Henrik Schröder
> No, we're not using columns with TTL, and I performed a major compaction
> before the repair, so there shouldn't be vast amounts of tombstones moving
> around.
>
> And the increase happened durin
No, we're not using columns with TTL, and I performed a major compaction
before the repair, so there shouldn't be vast amounts of tombstones moving
around.
And the increase happened during the repair, the nodes gained ~20-30GB each.
/Henrik
On Thu, Nov 8, 2012 at 12:40 PM, horschi wrote:
> H
Hi,
We recently ran a major compaction across our cluster, which reduced the
storage used by about 50%. This is fine, since we do a lot of updates to
existing data, so that's the expected result.
The day after, we ran a full repair -pr across the cluster, and when that
finished, each storage node
