Actually there is no delete right now. Only inserts.
I use twcs and not much compaction occurs.
It just miscalculates sstable sizes.
On 12-04-2017 14:58, anuja jain wrote:
Do you perform a lot of deletes or updates on your database?
On restart, it performs major compaction which can reduce the lo
Do you perform a lot of deletes or updates on your database?
On restart, it performs major compaction which can reduce the load on your
node by removing stale data.
Try configuring compaction in you conf to perform minor compaction i.e.
compactions at a regular interval.
Thanks,
Anuja
On Wed, Apr
Hello,
Here is the problem loads, first node shows 206TB data. After cassandra restart
it shows 51TB, like df shows.
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
UN x.x.x.1 206 TB 256 50.6%
Try nodetool tpstats - it can lead you to where your threads are stuck.
There could be various reasons for load factor to go high like disk/cpu
getting choked, you'll probably need to check dstat & iostat output along
with Cassandra Threadpool stats to get a decent idea.
On Wed, Apr 12, 2017 at 1:
Hello,
Nodetool status shows much more than actual data size.
When I restart node, it shows normal a while and increase load in time.
Where should I look?
Cassandra 3.0.8, jdk 1.8.121
Regards,
Osman
This e-mail message, including any attachments, is for the sole use of the
person to whom it h
