You can't delete by year unless tables are organized by year. For deleting
tables, cassandra keeeps a copy of the file history which you can delete.
Also, you could delete all the extra rows using CQL.
On Wed, Jun 10, 2015 at 7:15 PM, Jeff Ferland j...@tubularlabs.com wrote:
Compaction
Internode messages which are received by a node, but do not get not to be
processed within rpc_timeout are dropped rather than processed. As the
coordinator node will no longer be waiting for a response. If the Coordinator
node does not receive Consistency Level responses before the
The commitlog size is likely a red herring. In 2.0 we had 1gb commitlogs by
default. In 2.1 we have 8gb commitlogs by default. This is configurable at
the yaml.
Not sure what's causing the OOM. Did it generate an hprof file you can
analyze?
On Jun 13, 2015 7:42 AM, Oleksandr Petrov
Sorry I completely forgot to mention it in an original message: we have
rather large commitlog directory (which is usually rather small), 8G of
commitlogs. Draining and flushing didn't help.
On Sat, Jun 13, 2015 at 1:39 PM, Oleksandr Petrov
oleksandr.pet...@gmail.com wrote:
Hi,
We're using
Hi,
We're using Cassandra, recently migrated to 2.1.6, and we're experiencing
constant OOMs in one of our clusters.
It's a rather small cluster: 3 nodes, EC2 xlarge: 2CPUs, 8GB RAM, set up
with datastax AMI.
Configs (yaml and env.sh) are rather default: we've changed only concurrent
compactions
Thanks for showing interest.
Faceting is not yet supported, but it is in our roadmap. Our goal is to add
to Cassandra as many Lucene features as possible.
2015-06-12 18:21 GMT+02:00 Mohammed Guller moham...@glassbeam.com:
The plugin looks cool. Thank you for open sourcing it.
Does it
U said RF=1...missed that..so not sure eventual consistency is creating issues..
Thanks
Anuj Wadehra
Sent from Yahoo Mail on Android
From:Anuj Wadehra anujw_2...@yahoo.co.in
Date:Sat, 13 Jun, 2015 at 11:31 pm
Subject:Re: Dropped mutation messages
I think the messages dropped are the
I think the messages dropped are the asynchronous ones required to maintain
eventual consistency. Client may not be complaining as the data gets commited
to one node synchronously..but dropped when sent to other nodes asynchronously..
We resolved similar issue in our cluster by increasing
