[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[
https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-11420:
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.6
Status: Resolved (was: Patch Available)
thanks, committed with a small change (used {{createTableCounter}} to get the
global counts)
> Add the JMX metrics to track the write amplification of C*
> --
>
> Key: CASSANDRA-11420
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11420
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Dikang Gu
>Assignee: Dikang Gu
>Priority: Minor
> Fix For: 3.6
>
> Attachments:
> 0001-Add-the-metrics-to-track-the-write-amplification-of-.patch
>
>
> 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing
> /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db
> (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630,
> position=3690)
> It would be useful to expose the number of flushed bytes to JMX, so that we
> can monitor how many bytes are written by application and flushed to disk.
> I also expose the number of bytes written by compaction to JMX, so the WA can
> be calculated by dividing these two metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[ https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikang Gu updated CASSANDRA-11420: -- Attachment: (was: 0001-Add-the-metrics-of-how-many-bytes-we-flushed-from-me.patch) > Add the JMX metrics to track the write amplification of C* > -- > > Key: CASSANDRA-11420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11420 > Project: Cassandra > Issue Type: Improvement >Reporter: Dikang Gu >Assignee: Dikang Gu >Priority: Minor > Fix For: 3.x > > Attachments: > 0001-Add-the-metrics-to-track-the-write-amplification-of-.patch > > > 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing > /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db > (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, > position=3690) > It would be useful to expose the number of flushed bytes to JMX, so that we > can monitor how many bytes are written by application and flushed to disk. > I also expose the number of bytes written by compaction to JMX, so the WA can > be calculated by dividing these two metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[ https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikang Gu updated CASSANDRA-11420: -- Attachment: 0001-Add-the-metrics-to-track-the-write-amplification-of-.patch patch based on trunk. > Add the JMX metrics to track the write amplification of C* > -- > > Key: CASSANDRA-11420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11420 > Project: Cassandra > Issue Type: Improvement >Reporter: Dikang Gu >Assignee: Dikang Gu >Priority: Minor > Fix For: 3.x > > Attachments: > 0001-Add-the-metrics-to-track-the-write-amplification-of-.patch > > > 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing > /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db > (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, > position=3690) > It would be useful to expose the number of flushed bytes to JMX, so that we > can monitor how many bytes are written by application and flushed to disk. > I also expose the number of bytes written by compaction to JMX, so the WA can > be calculated by dividing these two metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[ https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikang Gu updated CASSANDRA-11420: -- Attachment: (was: 0002-expose-the-bytes-written-by-compaction-to-JMX-as-wel.patch) > Add the JMX metrics to track the write amplification of C* > -- > > Key: CASSANDRA-11420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11420 > Project: Cassandra > Issue Type: Improvement >Reporter: Dikang Gu >Assignee: Dikang Gu >Priority: Minor > Fix For: 3.x > > Attachments: > 0001-Add-the-metrics-to-track-the-write-amplification-of-.patch > > > 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing > /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db > (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, > position=3690) > It would be useful to expose the number of flushed bytes to JMX, so that we > can monitor how many bytes are written by application and flushed to disk. > I also expose the number of bytes written by compaction to JMX, so the WA can > be calculated by dividing these two metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[ https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikang Gu updated CASSANDRA-11420: -- Description: 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, position=3690) It would be useful to expose the number of flushed bytes to JMX, so that we can monitor how many bytes are written by application and flushed to disk. I also expose the number of bytes written by compaction to JMX, so the WA can be calculated by dividing these two metrics was: 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, position=3690) It would be useful to expose the number of flushed bytes to JMX, so that we can monitor how many bytes are written by application and flushed to disk. > Add the JMX metrics to track the write amplification of C* > -- > > Key: CASSANDRA-11420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11420 > Project: Cassandra > Issue Type: Improvement >Reporter: Dikang Gu >Assignee: Dikang Gu >Priority: Minor > Fix For: 3.x > > Attachments: > 0001-Add-the-metrics-of-how-many-bytes-we-flushed-from-me.patch, > 0002-expose-the-bytes-written-by-compaction-to-JMX-as-wel.patch > > > 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing > /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db > (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, > position=3690) > It would be useful to expose the number of flushed bytes to JMX, so that we > can monitor how many bytes are written by application and flushed to disk. > I also expose the number of bytes written by compaction to JMX, so the WA can > be calculated by dividing these two metrics -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-11420) Add the JMX metrics to track the write amplification of C*
[ https://issues.apache.org/jira/browse/CASSANDRA-11420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dikang Gu updated CASSANDRA-11420: -- Summary: Add the JMX metrics to track the write amplification of C* (was: Add the JMX metrics to track number of data flushed from memtable to disk) > Add the JMX metrics to track the write amplification of C* > -- > > Key: CASSANDRA-11420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11420 > Project: Cassandra > Issue Type: Improvement >Reporter: Dikang Gu >Assignee: Dikang Gu >Priority: Minor > Fix For: 3.x > > Attachments: > 0001-Add-the-metrics-of-how-many-bytes-we-flushed-from-me.patch, > 0002-expose-the-bytes-written-by-compaction-to-JMX-as-wel.patch > > > 2016-03-24_02:30:38.39936 INFO 02:30:38 Completed flushing > /data/cassandra/data/keyspace/column-family/column-family-tmp-ka-295782-Data.db > (73.266MiB) for commitlog position ReplayPosition(segmentId=1458717183630, > position=3690) > It would be useful to expose the number of flushed bytes to JMX, so that we > can monitor how many bytes are written by application and flushed to disk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
