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

Bernd Wahlen edited comment on SOLR-13862 at 10/24/19 7:12 AM:
---------------------------------------------------------------

I don't think that heap size is the problem. Start scripts are like this:
{code:java}
su - solr -c "bash -c 'cd /opt/solr-8.2.0; bin/solr start -m 64g -cloud -p 8983 
-s ../solr-data/instance-$(facter fqdn)-1/solr/ -z 
srv-solr1.qeep.net:2181,srv-solr2.qeep.net:2181,srv-solr3.qeep.net:2181 '"{code}
In normal operation heap usage is about 30-40%.


was (Author: bwahlen):
I don't think that heap size is the problem. Start scripts are like this:
{code:java}
su - solr -c "bash -c 'cd /opt/solr-8.2.0; bin/solr start -m 64g -cloud -p 8983 
-s ../solr-data/instance-$(facter fqdn)-1/solr/ -z 
srv-solr1.qeep.net:2181,srv-solr2.qeep.net:2181,srv-solr3.qeep.net:2181 '"{code}

> JDK 13 stability/recovery problems
> ----------------------------------
>
>                 Key: SOLR-13862
>                 URL: https://issues.apache.org/jira/browse/SOLR-13862
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    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

Reply via email to