@cassandra.apache.org
Subject: Re: persistent compaction issue (1.1.4 and 1.1.5)
I've started to use LeveledCompaction some time ago and from my
experience this indicates some SST on lower levels than they should be.
The compaction is going, moving them up level by level, but total count
does not change
@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: persistent compaction issue (1.1.4 and 1.1.5)
I've started to use LeveledCompaction some time ago and from my
experience this indicates some SST on lower levels than they should be.
The compaction is going, moving
issue (1.1.4 and 1.1.5)
I've started to use LeveledCompaction some time ago and from my
experience this indicates some SST on lower levels than they should be.
The compaction is going, moving them up level by level, but total count
does not change as new data goes in.
The numbers are pretty high
What Compaction Strategy are you using ?
Are there any errors in the logs ?
If you restart a node how long does it take for the numbers to start to rise ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 18/09/2012, at 7:39 AM, Michael
Leveled. nothing in the logs. Normal compactions seem to be occurring...these
ones just won't go away.
I've tried a rolling restart and literally tries killing our entire cluster and
bringing up one node at a time in case gossip was causing this. Same result.
The compactions are there
In your data directory there should be a .json file for each column family
that holds the manifest.
Do any of those indicate that you have a large number of SSTables in L0?
This number is also indicated in JMX by the UnLeveledSSTables count for
each column family.
If not it's possible that the
@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: persistent compaction issue (1.1.4 and 1.1.5)
In your data directory there should be a .json file for each column family that
holds the manifest.
Do any of those indicate
I've started to use LeveledCompaction some time ago and from my experience
this indicates some SST on lower levels than they should be. The compaction
is going, moving them up level by level, but total count does not change as
new data goes in.
The numbers are pretty high as for me. Such numbers
@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: persistent compaction issue (1.1.4 and 1.1.5)
I've started to use
@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: persistent compaction issue (1.1.4 and 1.1.5)
I've started to use LeveledCompaction some time ago and from my
experience this indicates some SST on lower levels than they should
Hi All,
I have an issue where each one of my nodes (currently all running at 1.1.5) is
reporting around 30,000 pending compactions. I understand that a pending
compaction doesn't necessarily mean it is a scheduled task however I'm confused
why this behavior is occurring. It is the same on all
11 matches
Mail list logo