>
>
> We're running with 128G memory and 30G heap size. Maybe it's good idea
> to increase the commitlog_total_space. On the other hand, even with 8G
> commitlog_total_space, replaying CL after restart takes more than 5
> minutes.
>
> In our case, the actual problem is it's causing lots of read re
Thanks Jeff for the quick response.
We're running with 3.0.13 which doesn't have commitlog_segment_recycling
option. So it should be disabled.
I think the CL flush is because commitlog full. The commitlog size is
closing to 8G:
#mbean =
org.apache.cassandra.metrics:name=TotalCommitLogSize,type=Co
On 2017-07-05 14:32 (-0700), Jay Zhuang wrote:
> Hi,
>
> commitlog_total_space_in_mb is increased from 1G to 8G in
> CASSANDRA-7031. Sometimes we saw the number of dropped mutations spikes.
> Not sure if it's a sign that we should increase the
> commitlog_total_space_in_mb?
8G seems pretty ty
Hi,
commitlog_total_space_in_mb is increased from 1G to 8G in
CASSANDRA-7031. Sometimes we saw the number of dropped mutations spikes.
Not sure if it's a sign that we should increase the
commitlog_total_space_in_mb?
For bean:
org.apache.cassandra.metrics:name=WaitingOnSegmentAllocation,type=Commi
