[ 
https://issues.apache.org/jira/browse/SOLR-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620136#comment-17620136
 ] 

Uwe Schindler commented on SOLR-16463:
--------------------------------------

In the above thread I found no exact java stack trace. If someone would post 
the whole hserr file it would be more helpful.
The lucene issue was only found in the Lucene's Facet module (not used by 
Solr), but as the error may happen in similar loops on DocIdSetIterators, it is 
likely that Solr is also affected. I'd really like to get a *full* hserr.pid by 
all those people reporting on mailing list.

The bug will be fixed hopefully in 20, unfortunately not in 19 (otherwise a 19 
docker image with Lucene 9.4 would have been a good choice and helpful for the 
new mmap api if it also enables preview mode).

About the bug: The cause is known and they can easily reproduce it.

> Provide a jre11 version of Solr 9.0 docker image
> ------------------------------------------------
>
>                 Key: SOLR-16463
>                 URL: https://issues.apache.org/jira/browse/SOLR-16463
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Docker
>    Affects Versions: 9.0
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Due to a known bug in current JDK 17 (see 
> [https://lists.apache.org/thread/wg7qtkddd1t5h08okj7gm9qbrpdf0ox6] and 
> [https://bugs.openjdk.org/browse/JDK-8285835)] Solr 9.0 under temurin17 may 
> crash frequently in e.g. a kubernetes environent.
> A known workaround is to build your own Solr docker image on JRE11. Let's 
> provide a convenience official image on temurin11 for 9.0 users, and consider 
> it for the upcoming 9.1 release too if the issue is not resolved by then.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to