Hi i have a 3 node cassandra cluster in aws. Each node is m3 large with
160GB hard disk.
It has been 1 month and cassandra already occupied 51GB of my disk space.
Obviously at some point of time i will run out of the disk space as the
data keeps coming in.
So, i would like to go in the path of mou
Anyone has seen similar behavior with LCS, please do let me know, It will
be good to know this can happen.
On Fri, Oct 9, 2015 at 5:19 PM, Anishek Agarwal wrote:
> Looks like some of the nodes have higher sstables on L0 and compaction is
> running there, so only few nodes run compaction at a ti
Obviously QUORUM_OR_ONE is in general no better than ONE. However we hardly
EVER fail back to ONE, and we are making a conscious choice. I’m okay with
hiding it if it is too tempting, but for insert/append only workloads without
deletes or TTL, it is a perfectly good trade off. Why not just use
Downgrading Consistency Policy suffers from effectively being the
downgraded consistency policy aka CL one. I think it's helpful to remember
that Consistency Level is effectively a contract on your consistency, if
you do "quorum or one" you're basically CL ONE. Think of it this way, CL
ONE usually
The DataStax Java driver is based on Netty and is non blocking; if you do
any CQL work you should look into it. At ProtectWise we use it with high
write volumes from Scala/Akka with great success.
We have a thin Scala wrapper around the Java driver that makes it act more
Scalaish (eg, Scala futur
