[
https://issues.apache.org/jira/browse/CASSANDRA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707423#comment-13707423
]
Jonathan Ellis commented on CASSANDRA-5661:
-------------------------------------------
bq. As each SegmentedFile has to return unique instance using
"createReader(String)" LoadingCache won't do for us, as we need get(K,
Callable) per SSTableReader.
Ben has added a borrow(K, Callable) method.
bq. as MultiWay returns a handle I changed RAR to have a setHandle method
instead of passing SegmentedFile into constructor, which seems a bit hacky to
me as we need to be careful in maintaining that relationship
Can you elaborate?
> Discard pooled readers for cold data
> ------------------------------------
>
> Key: CASSANDRA-5661
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5661
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 2.0
>
> Attachments: CASSANDRA-5661-multiway-per-sstable.patch,
> CASSANDRA-5661.patch, DominatorTree.png, Histogram.png
>
>
> Reader pooling was introduced in CASSANDRA-4942 but pooled
> RandomAccessReaders are never cleaned up until the SSTableReader is closed.
> So memory use is "the worst case simultaneous RAR we had open for this file,
> forever."
> We should introduce a global limit on how much memory to use for RAR, and
> evict old ones.
--
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
