I am only using LeveledCompactionStrategy, and as I describe in my original
mail, I don’t understand why C* is complaining that it cannot compact when I
have more than 40% free disk space.
On 07 Apr 2015, at 01:10 , Bryan Holladay
holla...@longsight.commailto:holla...@longsight.com wrote:
If you have SSD, you may afford switching to leveled compaction strategy,
which requires much less than 50% of the current dataset for free space
Le 5 avr. 2015 19:04, daemeon reiydelle daeme...@gmail.com a écrit :
You appear to have multiple java binaries in your path. That needs to be
What other storage impacting commands or nuances do you gave to consider
when you switch to leveled compaction? For instance, nodetool cleanup says
Running the nodetool cleanup command causes a temporary increase in disk
space usage proportional to the size of your largest SSTable.
Are sstables
I may have misunderstood, but it seems that he was already using
LeveledCompaction
On Tue, Apr 7, 2015 at 3:17 AM, DuyHai Doan doanduy...@gmail.com wrote:
If you have SSD, you may afford switching to leveled compaction strategy,
which requires much less than 50% of the current dataset for free
Hi,
I have a cluster of 5 nodes. We use cassandra 2.1.3.
The 5 nodes use about 50-57% of the 1T SSD.
One node managed to compact all its data. During one compaction this node used
almost 100% of the drive. The other nodes refuse to continue compaction
claiming that there is not enough disk
You appear to have multiple java binaries in your path. That needs to be
resolved.
sent from my mobile
Daemeon C.M. Reiydelle
USA 415.501.0198
London +44.0.20.8144.9872
On Apr 5, 2015 1:40 AM, Jean Tremblay jean.tremb...@zen-innovations.com
wrote:
Hi,
I have a cluster of 5 nodes. We use
