[
https://issues.apache.org/jira/browse/CASSANDRA-13890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810707#comment-16810707
]
Benedict commented on CASSANDRA-13890:
--------------------------------------
It is probably out of scope, but it would anyway be nice to produce our own
{{RateLimiter}} because the Guava one doesn't permit taking a permit
asynchronously, and this means we require an extra unnecessary thread for
"zero-copy" streaming. Baking the rate reporting into the {{RateLimiter}} for
use elsewhere we rate limit would also make a lot of sense IMO. If we're
limiting the rate, we probably care about reporting it too.
> Expose current compaction throughput
> ------------------------------------
>
> Key: CASSANDRA-13890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13890
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Low
> Labels: lhf
> Fix For: 4.x
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
