[ https://issues.apache.org/jira/browse/SOLR-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Heisey updated SOLR-7585: ------------------------------- Attachment: SOLR-7585.patch Alternate patch that checks the size of the TreeSet when deciding whether to simple add() or do a more complicated check involving remove/add. This feels like it fixes the underlying problem, rather than exiting the code early. The patch also gets rid of a bunch of warnings about parameterization of objects, and one warning about an unused variable. I chose to suppress the warning instead of removing the variable, because it's a variable that might find a use later. > ConcurrentLFUCache throws NoSuchElementException under a write-heavy load > ------------------------------------------------------------------------- > > Key: SOLR-7585 > URL: https://issues.apache.org/jira/browse/SOLR-7585 > Project: Solr > Issue Type: Bug > Affects Versions: 5.1 > Reporter: Maciej Zasada > Priority: Minor > Attachments: SOLR-7585.patch, SOLR-7585.patch, SOLR-7585.patch > > > Under a write-heavy load {{ConcurrentLFUCache}} throws > {{NoSuchElementException}}. The problem lies within > {{org.apache.solr.util.ConcurrentLFUCache#put}} method, which allows for a > race condition between the check and the call to {{markAndSweep}} method. > Despite that a thread must acquire a lock to perform sweeping, it's still > possible that multiple threads successfully detected a need for calling > markAndSweep. If they execute it sequentially, subsequent runs will fail with > {{NoSuchElementException}}. -- 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