[
https://issues.apache.org/jira/browse/CASSANDRA-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay updated CASSANDRA-4150:
-----------------------------
Attachment: 0002-add-bytes-written-metric-v2.patch
0001-CASSANDRA-4139-v2.patch
The problem with the liveRatio is that it is variable and we might have a leak
if we use the ratio...
- Lets say when we add the entry we have a ratio of 1.2 and when the entry is
removed we will have the ratio of 1.1 then we will leak some space for cache
utilization. So it will be better if this number doesn't change.
0001 removes memory meter and does changes to fix the issue.
0002 adds entry weight and small refactor to change the Provider interface as
suggested.
Thanks!
> Looks like Maximum amount of cache available in 1.1 is 2 GB
> -----------------------------------------------------------
>
> Key: CASSANDRA-4150
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4150
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Vijay
> Assignee: Vijay
> Attachments: 0001-CASSANDRA-4139-v2.patch, 0001-CASSANDRA-4150.patch,
> 0002-Use-EntryWeigher-for-HeapCache.patch,
> 0002-add-bytes-written-metric-v2.patch, concurrentlinkedhashmap-lru-1.3.jar
>
>
> The problem is that capacity is a Integer which can maximum hold 2 GB,
> I will post a fix to CLHM in the mean time we might want to remove the
> maximumWeightedCapacity code path (atleast for Serializing cache) and
> implement it in our code.
--
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
