You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Timothy Potter (JIRA)" <ji...@apache.org> on 2014/09/22 19:28:35 UTC
[jira] [Assigned] (SOLR-6529) Stop command in the start scripts
should only stop the instance that it had started
[ https://issues.apache.org/jira/browse/SOLR-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Potter reassigned SOLR-6529:
------------------------------------
Assignee: Timothy Potter
> Stop command in the start scripts should only stop the instance that it had started
> -----------------------------------------------------------------------------------
>
> Key: SOLR-6529
> URL: https://issues.apache.org/jira/browse/SOLR-6529
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Assignee: Timothy Potter
>
> Currently the stop command looks for all running Solr instances and stops those. I feel this is a bit dangerous.
> When starting a process with the start command we could write out a pid file of the solr process that it started. Then the stop script should stop that process.
> It could error out if the pid file is not present.
> We could still keep the feature of stopping all solr nodes by passing passing -all ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org