You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2009/02/19 14:02:02 UTC

[jira] Updated: (SOLR-990) Add pid file to snapinstaller to skip script overruns, and recover from failure

     [ https://issues.apache.org/jira/browse/SOLR-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Otis Gospodnetic updated SOLR-990:
----------------------------------

    Fix Version/s: 1.4
         Assignee: Otis Gospodnetic
          Summary: Add pid file to snapinstaller to skip script overruns, and recover from failure  (was: Add pid file to snapinstaller to skip script overruns, and recover from faliure)

> Add pid file to snapinstaller to skip script overruns, and recover from failure
> -------------------------------------------------------------------------------
>
>                 Key: SOLR-990
>                 URL: https://issues.apache.org/jira/browse/SOLR-990
>             Project: Solr
>          Issue Type: Improvement
>          Components: replication (scripts)
>            Reporter: Dan Rosher
>            Assignee: Otis Gospodnetic
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: SOLR-990.patch, SOLR-990.patch, SOLR-990.patch, SOLR-990.patch
>
>
> The pid file will allow snapinstaller to be run as fast as possible without overruns. Also it will recover from a last failed run should an older snapinstaller process no longer be running. 
> Avoiding overruns means that snapinstaller can be run as fast as possible, but without suffering from the performance issue described here:
> http://wiki.apache.org/solr/SolrPerformanceFactors#head-fc7f22035c493431d58c5404ab22aef0ee1b9909 
> This means that one can do the following
> */1 * * * *     ..../bin/snappuller   && ..../bin/snapinstaller
> Even with a 'properly tuned' setup, there can be times where snapinstaller can suffer from overruns due to a lack of resources, or an unoptimized index using more resources etc.
> currently the pid will live in /tmp ... perhaps it should be in the logs dir?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.