[
https://issues.apache.org/jira/browse/SOLR-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441243#comment-15441243
]
Mark Miller commented on SOLR-9284:
-----------------------------------
bq. As long as the name can be removed (in this case, implicitly by Caffeine
cache), the block cache items related to that name needs to be removed as well.
That's the reason a removal listener is necessary.
But that does not address "why". It just restates what you said:
"the block cache items related to that name needs to be removed as well."
I have the same questions though. Even if the name is removed, why do we care
if the data remains in the cache?
*Why* does the underlying data in the cache need to be removed? The underlying
cache locations should simply be reclaimed by the LRU cache replacement policy.
Do we gain much by working to explicitly free anything early in this case?
> The HDFS BlockDirectoryCache should not let it's keysToRelease or names maps
> grow indefinitely.
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-9284
> URL: https://issues.apache.org/jira/browse/SOLR-9284
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: hdfs
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-9284.patch, SOLR-9284.patch
>
>
> https://issues.apache.org/jira/browse/SOLR-9284
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
