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 Mon, 25 Sep 2017 01:48:00 GMT


Jon Haddad commented on CASSANDRA-13890:

> The RateLimter for the compactions are actually on reads though, not writes.

It may be useful to have 2 meters, one for reads and one for writes.  It's a bit surprising
that setting the compaction throughput limit to 100MB will take up potentially quite a bit
more I/O due to the write overhead.

I've got a first cut at a branch that adds the metric (only for reads) and updates the nodetool
command.  Since the rate limiter only applies to reads, from a code cleanliness perspective
I'd like to keep everything in the same place and keep it out of the rate limiter.  

WIP branch:

> 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.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

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

View raw message