lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-10141) Caffeine cache causes BlockCache corruption
Date Wed, 15 Feb 2017 16:33:41 GMT


Yonik Seeley commented on SOLR-10141:

Adding a guard in the test code is easy enough (just check if "live" has already been set
to false), but that then causes an additional problem: a memory leak since size() != (adds-removes)
at the end (i.e. the removal listener is not called for all items).

It looks like the removal listener is called the correct number of times, but not always with
the correct value.  My guess is that it's somehow related to concurrent use of equal keys
with different values.

> Caffeine cache causes BlockCache corruption 
> --------------------------------------------
>                 Key: SOLR-10141
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Yonik Seeley
>         Attachments: SOLR-10141.patch
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message