cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)
Date Wed, 23 Nov 2011 00:50:39 GMT


Vijay updated CASSANDRA-3495:

    Attachment: 0001-Add-BloomFilter-Serialization-size.patch

Simple patch to add bf disk usage in the cfstats. I was thinking of using memory meter to
measure the inmemory size but the over head in memory is almost constant and hence thought
choose a simpler solution.

Let me know if you guys think otherwise.
> capture BloomFilter memory size in Cassandra (JMX)
> --------------------------------------------------
>                 Key: CASSANDRA-3495
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 1.0.4
>            Reporter: Jackson Chung
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.0.4
>         Attachments: 0001-Add-BloomFilter-Serialization-size.patch
> Maybe this could be done in 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:!default.jspa
For more information on JIRA, see:


View raw message