[
https://issues.apache.org/jira/browse/CASSANDRA-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453539#comment-13453539
]
Hudson commented on CASSANDRA-4537:
-----------------------------------
Integrated in Cassandra #2090 (See
[https://builds.apache.org/job/Cassandra/2090/])
Add SSTable count per level to cfstats patch by yukim; reviewed by jbellis
for CASSANDRA-4537 (Revision c64d975cdf9eebddb04801573035a7272f779fed)
Result = ABORTED
yukim :
Files :
* src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
* src/java/org/apache/cassandra/tools/NodeCmd.java
* src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java
* CHANGES.txt
* src/java/org/apache/cassandra/db/ColumnFamilyStore.java
* src/java/org/apache/cassandra/db/compaction/LeveledCompactionStrategy.java
> We should emit number of sstables in each level from JMX
> --------------------------------------------------------
>
> Key: CASSANDRA-4537
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4537
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: sankalp kohli
> Assignee: Yuki Morishita
> Priority: Minor
> Labels: compaction, leveled
> Fix For: 1.2.0 beta 1
>
> Attachments: 4537.txt, 4537-v2.txt
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> We should add methods to this Mbean
> org.apache.cassandra.db.ColumnFamilyStoreMBean
> These metrics will be helpful to see how sstables are distributed in
> different levels and how they move to higher level with time.
> Currently we can see this by looking at the json file but with JMX, we can
> monitor the historic values over time using any monitoring tool.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
