You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2012/09/07 22:58:07 UTC

[jira] [Updated] (CASSANDRA-4537) We should emit number of sstables in each level from JMX

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

Yuki Morishita updated CASSANDRA-4537:
--------------------------------------

    Attachment: 4537.txt

Attaching patch that adds SSTableCountPerLevel to ColulmnFamilyStoreMBean, which returns number of SSTable for each level in _int[]_ and prints it with nodetool cfstats.

Output looks like below:
{code}
...
    Column Family: Standard1
    SSTable count: 19
    SSTables in each level: [0, 8, 11, 0, 0, 0, 0, 0]
    Space used (live): 100923462
    Space used (total): 101012612
...
{code}

compactionstats displays info only when compaction is happening, so I chose cfstats to show info.

cfstats output is long, but let CASSANDRA-4191 handle it.
                
> 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.1
>
>         Attachments: 4537.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