cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13890) Expose current compaction throughput
Date Sat, 23 Sep 2017 16:06:02 GMT


Jon Haddad commented on CASSANDRA-13890:

I was looking at that, but I don't think it would be very accurate using the numbers as is.
 Doesn't that report all the bytes compacted since the server started?  Or are you suggesting
updating {{compactionBytesWritten}} to track the recent rate (maybe a 5 second moving average)
in addition to the simple metric it already tracks? I think this could work well.

Before your comment I was also looking at adding a start time to {{CompactionInfo}}, then
using {{completed}} to determine the current rate, but it suffers from the same problem as
using raw  {{compactionBytesWritten}} - changing the limit via {{nodetool setcompactionthroughput}}
would immediately change the throttle rate but it wouldn't be reflected in the reported rate
till the current compactions ended, so I'm not wild about this approach.

> Expose current compaction throughput
> ------------------------------------
>                 Key: CASSANDRA-13890
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jon Haddad
>            Assignee: Jon Haddad
>            Priority: Minor
>              Labels: lhf
>             Fix For: 4.0
> Getting and setting the current compaction throughput limit is supported, but there's
no means of knowing if the setting is actually making a difference.
> Let's expose the current throughput being utilized by Cassandra that's in the {{compactionRateLimiter}}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message