You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/23 16:48:02 UTC
[jira] [Updated] (CASSANDRA-5497) Use allocator information to
improve memtable memory usage estimate
[ https://issues.apache.org/jira/browse/CASSANDRA-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-5497:
--------------------------------------
Fix Version/s: 1.2.5
> Use allocator information to improve memtable memory usage estimate
> -------------------------------------------------------------------
>
> Key: CASSANDRA-5497
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5497
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.1.12, 1.2.5
>
> Attachments: 5497.txt, 5497-v2.txt
>
>
> A user reported that Cassandra's estimate of memtable space used was off by a factor of between 3 and 10 for his counter columnfamilies.
> We may or may not be able to fix the counter estimate (counter merging is a cranky best, and unlike normal merging can involve allocating new objects), but we can definitely use the SlabAllocator information to cap the error in our estimate at a fairly low amount.
--
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