Re: Is it a memory issue?

2016-11-06 Thread Ben Slater
a48e-11e6-b985-979fea8d6099Compaction cargts > eventdata.eventdata_event_time_idx 32098562606 42616107664 bytes > 75.32% > Active compaction remaining time : 0h11m12s > > > *From:* Ben Slater <ben.sla...@instaclustr.com> > *Date:* 2016-11-07 11:4

Re: Is it a memory issue?

2016-11-06 Thread wxn...@zjqunshuo.com
: Is it a memory issue? This sounds to me like your writes go ahead of compactions trying to keep up which can eventually cause issues. Keep an eye on nodetool compactionstats if the number of compactions continually climbs then you are writing faster than Cassandra can actually process

Re: Is it a memory issue?

2016-11-06 Thread Ben Slater
This sounds to me like your writes go ahead of compactions trying to keep up which can eventually cause issues. Keep an eye on nodetool compactionstats if the number of compactions continually climbs then you are writing faster than Cassandra can actually process. If this is happening then you

Is it a memory issue?

2016-11-06 Thread wxn...@zjqunshuo.com
Hi All, We have one issue on C* testing. At first the inserting was very fast and TPS was about 30K/s, but when the size of data rows reached 2 billion, the insertion rate decreased very badly and the TPS was 20K/s. When the size of rows reached 2.3 billion, the TPS decreased to 0.5K/s, and