[
https://issues.apache.org/jira/browse/SOLR-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101716#comment-17101716
]
Bernd Wahlen edited comment on SOLR-13862 at 5/7/20, 2:20 PM:
--------------------------------------------------------------
I am trying again with solr 8.5.1 + 14.0.1 adopt and the same Shenandoah+Memory
settings. I will let you know if the problems are gone.
was (Author: bwahlen):
I am trying again with solr 8.5.1 + 14.0.1 adopt and the same Shenandoah+Memory
settings. I will let you know the problems are gone.
> JDK 13+Shenandoah stability/recovery problems
> ---------------------------------------------
>
> Key: SOLR-13862
> URL: https://issues.apache.org/jira/browse/SOLR-13862
> Project: Solr
> Issue Type: Bug
> Affects Versions: 8.2
> Reporter: Bernd Wahlen
> Priority: Major
>
> after updating my cluster (centos 7.7, solr 8.2, jdk12) to JDK13 (3 nodes, 4
> collections, 1 shard) everything was running good (with lower p95) for some
> hours. Then 2 nodes (not the leader) going to recovery state, but ~"Recovery
> failed Error opening new searcher". I tried rolling restart the cluster, but
> recovery is not working. After i switched to jdk11 recovery works again. In
> summary jdk11 or jdk12 was running stable, jdk13 not.
> This is my solr.in.sh:
> GC_TUNE="-XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC"
> SOLR_TIMEZONE="CET"
>
> GC_LOG_OPTS="-Xlog:gc*:file=/var/log/solr/solr_gc.log:time:filecount=9,filesize=20M:safepoint"
> I also tried ADDREPLICA during my attempt to reapair the cluster, which
> causes Out of Memory on JDK 13 and worked after going back to JDK 11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
