[
https://issues.apache.org/jira/browse/SOLR-10141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868099#comment-15868099
]
Yonik Seeley commented on SOLR-10141:
-------------------------------------
OK, so I finally tracked down the corruption failures with Caffeine to the
removal listener being called more than once with the same value.
The first time, the underlying block is released and then presumably reused for
a different key. The next time (which should never happen), the underlying
block is unlocked again and can hence be reused by an additional key and we get
into a situation where multiple "live" keys point to the same underlying memory
block (and corruption results).
> Caffeine cache causes BlockCache corruption
> --------------------------------------------
>
> Key: SOLR-10141
> URL: https://issues.apache.org/jira/browse/SOLR-10141
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Yonik Seeley
>
> After fixing the race conditions in the BlockCache itself (SOLR-10121), the
> concurrency test passes with the previous implementation using
> ConcurrentLinkedHashMap and fail with Caffeine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
