lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11514) Solr 7.1 does not honor values specified in solr.in.sh
Date Thu, 26 Oct 2017 15:58:00 GMT

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

Shawn Heisey commented on SOLR-11514:
-------------------------------------

I added one of your statements to /etc/default/solr.in.sh on my Ubuntu 16 system, specifically
the ZK_HOST variable.  I see the results of that change on the Solr commandline after restarting
the service.

Because I don't actually have ZK running, much less with the specific hostnames your ZK_HOST
references, that Solr install isn't actually working, but it did start with the correct option.
 In the "ps" output you can see -DzkHost:

{code}
elyograg@smeagol:~$ ps ax | grep solr
34919 ?        Sl     0:02 /usr/lib/jvm/java-8-oracle/bin/java -server -Xms512m -Xmx2g -XX:NewRatio=3
-XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC
-XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark
-XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50
-XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled
-XX:-OmitStackTraceInFastThrow -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps
-XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/solr/logs/solr_gc.log
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -DzkClientTimeout=15000
-DzkHost=solr-zoo01:2601,solr-zoo02:2601,solr-zoo03:2601,solr-zoo04:2601,solr-zoo05:2601 -Dsolr.log.dir=/var/solr/logs
-Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -Djetty.home=/opt/solr/server
-Dsolr.solr.home=/var/solr/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf
-Dlog4j.configuration=file:/var/solr/log4j.properties -Xss256k -Dsolr.jetty.https.port=8983
-Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /var/solr/logs
-jar start.jar --module=http
35035 pts/3    S+     0:00 grep --color=auto solr
{code}

This is Solr 7.1.0, installed with default options.  I have been unable to replicate the problem
you're seeing.


> Solr 7.1 does not honor values specified in solr.in.sh
> ------------------------------------------------------
>
>                 Key: SOLR-11514
>                 URL: https://issues.apache.org/jira/browse/SOLR-11514
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: release-scripts, SolrCloud
>    Affects Versions: 7.1
>         Environment: Linux RHEL 7, 8GB RAM, 60GB HDD, Solr 7.1 in cloud mode (zookeeper
3.4.10)
>            Reporter: Howard Black
>         Attachments: solr, solr.in.sh
>
>
> Just installed Solr 7.1 and zookeeper 3.4.10 into a test environment and it seems that
arguments in the solr.in.sh file in /etc/default are not getting picked up when starting the
server.
> I have this specified in solr.in.sh SOLR_JAVA_MEM="-Xms512m -Xmx6144m" but the JVM shows
-Xms512m -Xmx512m.
> Same goes for SOLR_LOGS_DIR=/mnt/logs  logs are still being written to /opt/solr/server/logs
> The command I used to install Solr is this:
> ./install_solr_service.sh /home/hblack/solr-7.1.0.tgz -i /opt -d /mnt/solr-home -s solr
-u solr



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message