You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2016/06/29 11:53:37 UTC
[jira] [Resolved] (SOLR-8777) Duplicate Solr process can cripple a
running process
[ https://issues.apache.org/jira/browse/SOLR-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar resolved SOLR-8777.
-----------------------------------------
Resolution: Fixed
Assignee: Shalin Shekhar Mangar
Fix Version/s: master (7.0)
6.2
Thanks Jessica and Scott!
> Duplicate Solr process can cripple a running process
> ----------------------------------------------------
>
> Key: SOLR-8777
> URL: https://issues.apache.org/jira/browse/SOLR-8777
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.3.1
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-8777.patch, SOLR-8777.patch
>
>
> Thanks to [~mewmewball] for catching this one.
> Accidentally executing the same instance of Solr twice causes the second start instance to die with an "Address already in use", but not before deleting the first instance's live_node entry, emitting "Found a previous node that still exists while trying to register a new live node <node> - removing existing node to create another".
> The second start instance dies and its ephemeral node is then removed, causing /live_nodes/<node> to be empty since the first start instance's live_node was deleted by the second.
--
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