[
https://issues.apache.org/jira/browse/CASSANDRA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3495:
--------------------------------------
Labels: jmx (was: )
> 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
> Affects Versions: 1.0.4
> Reporter: Jackson Chung
> Assignee: Vijay
> Priority: Minor
> Labels: jmx
> Fix For: 1.0.4
>
> Attachments: 0001-Add-BloomFilter-Serialization-size.patch
>
>
> 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
