Hi Marc,
Changes done using "nodetool setcompactionthroughput" will only be
applicable till Cassandra service restart.
The throughput value will revert back to the settings inside cassandra.yaml
post service restart.
On Fri, Feb 17, 2023 at 1:04 PM Marc Hoppins wrote:
> …and if it is altered v
…and if it is altered via nodetool, is it altered until manually changed or
service restart, so must be manually put pack?
From: Aaron Ploetz
Sent: Thursday, February 16, 2023 4:50 PM
To: user@cassandra.apache.org
Subject: Re: Cleanup
EXTERNAL
So if I remember right, setting compaction_throughp
I checked the writetimstamp as suggested and they match to the deletion
timestamp instead of insertion timestamp.
That means the data got resurrected.
I unfortunately cannot put trace on.
Am I correct to conclude that?
From: C. Scott Andreas
Sent: Monday, Februa
So if I remember right, setting compaction_throughput_per_mb to zero
effectively disables throttling, which means cleanup and compaction will
run as fast as the instance will allow. For normal use, I'd recommend
capping that at 8 or 16.
Aaron
On Thu, Feb 16, 2023 at 9:43 AM Marc Hoppins wrote:
Compaction_throughtput_per_mb is 0 in cassandra.yaml. Is setting it in nodetool
going to provide any increase?
From: Durity, Sean R via user
Sent: Thursday, February 16, 2023 4:20 PM
To: user@cassandra.apache.org
Subject: RE: Cleanup
EXTERNAL
Clean-up is constrained/throttled by compactionthrou
Clean-up is constrained/throttled by compactionthroughput. If your system can
handle it, you can increase that throughput (nodetool setcompactionthroughput)
for the clean-up in order to reduce the total time.
It is a node-isolated operation, not cluster-involved. I often run clean up on
all nod
There is no advantage of running cleanup if no new nodes are introduced. So
cleanup time should remain same when adding new nodes.
Cleanup is a local to node so network bandwidth should have no effect on
reducing cleanup time.
Dont ignore cleanup as it can cause you disks occupied without any u
Hulloa all,
I read a thing re. adding new nodes where the recommendation was to run cleanup
on the nodes after adding a new node to remove redundant token ranges.
I timed this way back when we only had ~20G of data per node and it took
approx. 5 mins per node. After adding a node on Tuesday, I
