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
mailto:holla...@longsight.com>> wrote:
What other storage im
Hey Peter,
This is from the perspective of 2.0.13 but there should be something
similar in your version. Can you enable debug log for cassandra and see if
the log files have additional info. Depending on how soon/later in you test
you get the error, you might also want to modify the "maxBackupInde
Hi,
Does the latest Data Stax Java driver (2.1.5) support lightweight transactions
using object mapping? For example, if I set the write consistency level of the
mapped class to SERIAL through annotation, then does the “save” operation use
lightweight transaction instead of a normal write?
Tha
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 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.
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" a écrit :
> You appear to have multiple java binaries in your path. That needs to be
> resolved.
>
> sent fro
Thank you, we'll see that instrument,
2015-04-06 12:30 GMT+02:00 Srinivasa T N :
> Comparison to OpenTSDB HBase
>
> For one we do not use id’s for strings. The string data (metric names and
> tags) are written to row keys and the appropriate indexes. Because
> Cassandra has much wider rows there
Comparison to OpenTSDB HBase
For one we do not use id’s for strings. The string data (metric names and
tags) are written to row keys and the appropriate indexes. Because
Cassandra has much wider rows there are far fewer keys written to the
database. The space saved by using id’s is minor and by n
Thanks, is it a kind of opentsdb?
2015-04-05 18:28 GMT+02:00 Kevin Burton :
> > Hi, I switched from HBase to Cassandra and try to find problem solution
> for timeseries analysis on top Cassandra.
>
> Depending on what you’re looking for, you might want to check out KairosDB.
>
> 0.95 beta2 just s
