cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13890) Expose current compaction throughput
Date Sat, 23 Sep 2017 15:24:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177845#comment-16177845
] 

Jon Haddad commented on CASSANDRA-13890:
----------------------------------------

I figured this would be low hanging fruit, but there's a couple snags.  First off, the api
in {{com/google/common/util/concurrent/RateLimiter.java}} only exposes the ability to acquire
"Permits", which is how QPS is regulated.  There's nothing public to determine what current
usage is. 

We're using an older version of Guava, (18), so I checked the current and it doesn't expose
any additional information.

> Expose current compaction throughput
> ------------------------------------
>
>                 Key: CASSANDRA-13890
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13890
>             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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message