cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)
Date Tue, 15 Nov 2011 22:05:51 GMT

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

Jonathan Ellis updated CASSANDRA-3495:
--------------------------------------

      Component/s: Tools
    Fix Version/s: 1.0.4
         Assignee: Vijay
    
> capture BloomFilter memory size in Cassandra (JMX)
> --------------------------------------------------
>
>                 Key: CASSANDRA-3495
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3495
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jackson Chung
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.0.4
>
>
> Maybe this could be done in https://issues.apache.org/jira/browse/CASSANDRA-3347 also,
but not sure what's the scope in that jira. It'd be great if the BF memory size can be captured
in the JMX monitoring. 
> Though not sure how you would capture the "heap size" (easily that is) of the object.
There is a BF.serializedSize() , can this be exposed to the BloomFilterTracker and DataTracker...
and use this instead? Anyway, will let the implementor to decide/design 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message