ived this message in error, please contact the sender immediately and
> irrevocably delete this message and any copies.
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Wednesday, February 01, 2012 21:51
> To: user@cassandra.apache.org
> Subject: Re: Consurrent compa
ge and any copies.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Wednesday, February 01, 2012 21:51
To: user@cassandra.apache.org
Subject: Re: Consurrent compactors
(Assuming 1.0* release)
>From the comments in cassandra.yaml
# Number of simultaneous compactions to allow, NOT includ
(Assuming 1.0* release)
From the comments in cassandra.yaml
# Number of simultaneous compactions to allow, NOT including
# validation "compactions" for anti-entropy repair. Simultaneous
# compactions can help preserve read performance in a mixed read/write
# workload, by mitigating the tendency o
Hi,
When concurrent compactors are set to more then 1, it's rare when more than 1
compaction is running in parallel.
Didn't checked the source code, but it looks like when next compaction task
(any of minor, major, or cleanup) is for the same CF, it will not start in
parallel and next tasks ar
