Keep in mind that compaction in LCS can only run 1 compaction per level.
Even if it wants to run more compactions in L0 it might be blocked
because it is already running a compaction in L0.
BR
Jan
On 01/16/2016 01:26 AM, Sebastian Estevez wrote:
LCS is IO ontensive but CPU is also relevant.
Hello,
We are running a 3 node cluster with RF=3 and 5 clients in a test environment.
The C* settings are mostly default. We noticed quite high context switching
during our tests. On 100 000 000 keys/partitions we averaged around 260 000 cs
(with a max of 530 000).
We were running 12 000~ tran
@cassandra.apache.org
Subject: Re: high context switches
On Fri, Nov 21, 2014 at 1:21 AM, Jan Karlsson
mailto:jan.karls...@ericsson.com>> wrote:
Nothing really wrong with that however I would like to understand why these
numbers are so high. Have others noticed this behavior? How much context
switch
Hi everybody!
We have a problem that we encountered during testing over the weekend.
During the tests we noticed that repairs started to fail. We are running on a
three node cluster with three in replication. It uses a default C*
installation. This error has occured on multiple non-coordinator n
The request would return with the latest data.
The read request would fire against node 1 and node 3. The coordinator would
get answers from both and would merge the answers and return the latest.
Then read repair might run to update node 3.
QUORUM does not take into consideration whether an an
