You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jackson Chung (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 19:12:51 UTC

[jira] [Created] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)

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
            Reporter: Jackson Chung
            Priority: Minor


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

        

[jira] [Updated] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)

Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Updated] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)

Posted by "Vijay (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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: 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
>             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

        

[jira] [Updated] (CASSANDRA-3495) capture BloomFilter memory size in Cassandra (JMX)

Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
     [ 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