[
https://issues.apache.org/jira/browse/CASSANDRA-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291102#comment-13291102
]
Vijay commented on CASSANDRA-4150:
----------------------------------
Yes we did upgrade it to CLHM 1.3 in both Cassandra 1.1 and Cassandra 1.2 to
fix the original issue mentioned in the ticket.
Ben (author of CLHM) also added EntryWeight<K, V> to CLHM 1.3 on our request.
Which is 0002 part of the patch originally submitted.
To use EntryWeights we needed to calculate the memory size's (We where trying
out multiple options using MemoryMeter or using other mechanisms) of the Key
and Value, we where trying that in this ticket.
Hence CASSANDRA-4315 was opened to continue the work of updating CLHM
Weigher<V> to CLHM EntryWeight<K, V>.
> Allow larger cache capacities than 2GB
> --------------------------------------
>
> 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
> Fix For: 1.1.1
>
> 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
