[ https://issues.apache.org/jira/browse/SOLR-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176206#comment-15176206 ]
ASF subversion and git services commented on SOLR-8145: ------------------------------------------------------- Commit b17c57f072b65106f2689d2f9ea6a5ca14e492e0 in lucene-solr's branch refs/heads/master from [~thelabdude] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b17c57f ] SOLR-8145: mention fix in solr/CHANGES.txt > bin/solr script oom_killer arg incorrect > ---------------------------------------- > > Key: SOLR-8145 > URL: https://issues.apache.org/jira/browse/SOLR-8145 > Project: Solr > Issue Type: Bug > Components: scripts and tools > Affects Versions: 5.2.1 > Reporter: Nate Dire > Assignee: Timothy Potter > Priority: Minor > Attachments: SOLR-8145.patch, SOLR-8145.patch, SOLR-8145.patch > > > I noticed the oom_killer script wasn't working in our 5.2 deployment. > In the {{bin/solr}} script, the {{OnOutOfMemoryError}} option is being passed > as an arg to the jar rather than to the JVM. I moved it ahead of {{-jar}} > and verified it shows up in the JVM args in the UI. > {noformat} > # run Solr in the background > nohup "$JAVA" "${SOLR_START_OPTS[@]}" $SOLR_ADDL_ARGS -jar start.jar \ > "-XX:OnOutOfMemoryError=$SOLR_TIP/bin/oom_solr.sh $SOLR_PORT > $SOLR_LOGS_DIR" "${SOLR_JETTY_CONFIG[@]}" \ > {noformat} > Also, I'm not sure what the {{SOLR_PORT}} and {{SOLR_LOGS_DIR}} args are > doing--they don't appear to be positional arguments to the jar. > Attaching a patch against 5.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org