Hi, Aaron
Just sum of total volume for all streams between nodes.
But seems I understand what happened: after repair my column family pass
over several minor compactions, and during these compactions it create
new tombstones (my CF contain data with TTL, so it can discover and mark
new data e
> What is strange - when streams for the second repair starts they have the
> same or even bigger total volume,
What measure are you using ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 22/04/2012, at 10:16 PM, Igor wrote:
> but after
but after repair all nodes should be in sync regardless of whether new
files were compacted or not.
Do you suggest major compaction after repair? I'd like to avoid it.
On 04/22/2012 11:52 AM, Philippe wrote:
Repairs generate new files that then need to be compacted.
Maybe that's where the temp
Repairs generate new files that then need to be compacted.
Maybe that's where the temporary extra volume comes from?
Le 21 avr. 2012 20:43, "Igor" a écrit :
> Hi
>
> I can't understand the repair behavior in my case. I have 12 nodes ring
> (all 1.0.7):
>
> 10.254.237.2LA ADS-LA-1
Hi
I can't understand the repair behavior in my case. I have 12 nodes ring
(all 1.0.7):
10.254.237.2LA ADS-LA-1Up Normal 50.92 GB
0.00% 0
10.254.238.2TX TX-24-RACK Up Normal 33.29 GB
0.00% 1
10.254.236.2VA ADS-VA-1Up
