You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2019/07/25 17:29:00 UTC
[jira] [Resolved] (SOLR-13653) java (10 & 11) HashMap bug can
trigger AssertionError when using SolrCaches
[ https://issues.apache.org/jira/browse/SOLR-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-13653.
-----------------------------
Resolution: Information Provided
Assignee: Hoss Man
> java (10 & 11) HashMap bug can trigger AssertionError when using SolrCaches
> ---------------------------------------------------------------------------
>
> Key: SOLR-13653
> URL: https://issues.apache.org/jira/browse/SOLR-13653
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Hoss Man
> Priority: Major
> Labels: Java10, java11
>
> we've seen some java11 jenkins builds that have failed due to an AssertionError being thrown by HashMap.put as used in LRUCache -- in at least one case these failures are semi-reproducible. (the occasional "success" is likely due to some unpredictibility in thread contention)
> Some cursory investigation suggests that JDK-8205399, first identified in java10, and fixed in java12-b26...
> https://bugs.openjdk.java.net/browse/JDK-8205399
> There does not appear to be anything we can do to mitigate this problem in Solr.
> It's also not clear to me based on th comments in JDK-8205399 if the underlying problem can cause problems for end users running w/assertions disabled, or if it just results in sub-optimal performance
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org