cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Deng (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12608) For LCS compaction sessions, have compactionstats to print out src_level and dst_level
Date Sat, 03 Sep 2016 19:18:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wei Deng updated CASSANDRA-12608:
---------------------------------
    Description: It seems that we use reportCompactionTable() function in o.a.c.tools.nodetool.CompactionStats
to print out the information for each compaction session, which already has access to compactionID
according to [this line|https://github.com/apache/cassandra/blob/9895837557137b96bb12d371e42138770539e82d/src/java/org/apache/cassandra/tools/nodetool/CompactionStats.java#L92].
This means it should not be hard to get the source level and destination level from a LCS
compaction ID. If we could add two additional columns "src_level" and "dst_level" whenever
we detect a particular compaction session is using LeveledCompactionStrategy, it would be
very helpful in understanding the progress LCS is making and what all of the concurrent compaction
sessions are doing for people observing the compactions in real-time. For none-LCS compaction
sessions, these two columns can just print empty strings.  (was: It seems that we use reportCompactionTable()
function in o.a.c.tools.nodetool.CompactionStats to print out the information for each compaction
session, which already has access to compactionID according to [this line|https://github.com/apache/cassandra/blob/9895837557137b96bb12d371e42138770539e82d/src/java/org/apache/cassandra/tools/nodetool/CompactionStats.java#L92].
This means it should not be hard to get the source level and destination level from a LCS
compaction ID. If we could add two additional columns "src_level" and "dst_level" whenever
we detect a particular compaction session is using LeveledCompactionStrategy, it would be
very helpful in understanding the progress LCS is making and what all of the concurrent compaction
sessions are doing. For none-LCS compaction sessions, these two columns can just print empty
strings.)

> For LCS compaction sessions, have compactionstats to print out src_level and dst_level
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12608
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12608
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Compaction
>            Reporter: Wei Deng
>            Priority: Minor
>              Labels: lcs, observation
>
> It seems that we use reportCompactionTable() function in o.a.c.tools.nodetool.CompactionStats
to print out the information for each compaction session, which already has access to compactionID
according to [this line|https://github.com/apache/cassandra/blob/9895837557137b96bb12d371e42138770539e82d/src/java/org/apache/cassandra/tools/nodetool/CompactionStats.java#L92].
This means it should not be hard to get the source level and destination level from a LCS
compaction ID. If we could add two additional columns "src_level" and "dst_level" whenever
we detect a particular compaction session is using LeveledCompactionStrategy, it would be
very helpful in understanding the progress LCS is making and what all of the concurrent compaction
sessions are doing for people observing the compactions in real-time. For none-LCS compaction
sessions, these two columns can just print empty strings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message