lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <>
Subject [jira] [Commented] (SOLR-8145) bin/solr script oom_killer arg incorrect
Date Thu, 03 Mar 2016 00:36:18 GMT


Scott Blum commented on SOLR-8145:

We always run solr in foreground, because we handle app process management at a higher level.
 When we call bin/solr we already have a pidfile setup, stderr and stdout piped, etc-- so
it's vital we run it in foreground to get the `exec` and maintain process identity.  But we
still need oom killer, so that it will die fast and our process watcher will restart it.

> bin/solr script oom_killer arg incorrect
> ----------------------------------------
>                 Key: SOLR-8145
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: scripts and tools
>    Affects Versions: 5.2.1
>            Reporter: Nate Dire
>            Assignee: Timothy Potter
>            Priority: Minor
>             Fix For: 6.0
>         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/ $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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message