Re: [EXTERNAL] Cassandra cluster add new node slowly

wer versions give a bit more info on > progress. > - Don’t forget to run cleanup on existing nodes after the new nodes > are added. > > > > Sean Durity > From: qf zhou [mailto:zhouqf2...@gmail.com] > Sent: Tuesday, January 02, 2018 10:30 PM > To: user@

Cassandra cluster add new node slowly

The cluster has 3 nodes, and the data in each node is about 1.2 T. I want to add two new nodes to expand the cluster. Following the instructions from the datastax website, ie, (http://docs.datastax.com/en/archived/cassandra/3.x/cassandra/operations/opsAddNodeToCluster.html

Re: old big tombstone data file occupy much disk space

Yes, your are right. I am using STCS compaction strategy with some kind of timeseries model. Too much disk space has been occupied. What should I do to stop the disk full ? I only want to keep 100 days data most recently, so I set default_time_to_live = 864(100 days ). I know I need

How to do cassandra routine maintenance

I am using the cluster with 3 cassandra nodes, the cluster version is 3.0.9. Each day about 200~300 million records are inserted into the cluster. As time goes by, more and more data occupied more and more disk space. Currently,the data distribution on each node is as the following: UN

Re: old big tombstone data file occupy much disk space

ing works fine for me. > > Are you sure there is nothing happening behind the scene ? What dies > 'nodetool compactionstats -H' says ? > > On 1 September 2017 at 12:05, qf zhou <mailto:zhouqf2...@gmail.com>> wrote: > When I trigger the compaction wi

Re: old big tombstone data file occupy much disk space

When I trigger the compaction with the full path,  I found nothing in the system.log.  Nothing happens in the  terminal and it just stops there.#calling operation forceUserDefinedCompaction of mbean org.apache.cassandra.db:type=CompactionManager在 2017年9月1日，下午5:06，qf zhou <zhouqf2...@gmail.com&

Re: old big tombstone data file occupy much disk space

:704 - Schema does not exist for file mc-151276-big-Data.db. Skipping. > 在 2017年9月1日，下午4:54，Nicolas Guyomar 写道： > > You should have a log coming from the CompactionManager (in cassandra > system.log) when you try the command, what does it says ? > > On 1 September 2017

Re: old big tombstone data file occupy much disk space

t try : > > echo "run -b org.apache.cassandra.db:type=CompactionManager > forceUserDefinedCompaction mc-100963-big-Data.db" | java -jar > /opt/cassandra/tools/jmx/jmxterm-1.0-alpha-4-uber.jar -l localhost:7199 > > > > On 1 September 2017 at 08:

Re: old big tombstone data file occupy much disk space

t versions, or a jmx method in older > versions > > > -- > Jeff Jirsa > > >> On Aug 31, 2017, at 11:04 PM, qf zhou wrote: >> >> I am using a cluster with 3 nodes and the cassandra version is 3.0.9. I >> have used it about 6 months. Now each n

old big tombstone data file occupy much disk space

I am using a cluster with 3 nodes and the cassandra version is 3.0.9. I have used it about 6 months. Now each node has about 1.5T data in the disk. I found some sstables file are over 300G. Using the sstablemetadata command, I found it: Estimated droppable tombstones: 0.9622972799707109.

Re: Cassandra - Nodes can't restart due to java.lang.OutOfMemoryError: Direct buffer memory

I am usingCassandra 3.9 with cqlsh 5.0.1. > 在 2017年8月31日，下午5:54，Jonathan Baynes 写道： > > again

Cassandra - Nodes can't restart due to java.lang.OutOfMemoryError: Direct buffer memory

I am running a cluster with 3 nodes. Then it occurs the following errors. After I restart one node, the error happens again. I don’t know why. Who Can help me ? Thank you !! ERROR [ReadStage-31] 2017-08-31 15:08:20,878 JVMStabilityInspector.java:141 - JVM state determined to be unstable. Ex