[
https://issues.apache.org/jira/browse/SOLR-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176360#comment-15176360
]
Scott Blum commented on SOLR-8777:
----------------------------------
I can take a crack at this. My thought would be to attempt the bind the port
earlier on, and exit more quickly. BTW, looking at just the code, it looks
like the live_node isn't the only possible disruption: ZkController.init() also
tries to join overseer election and publish all nodes as down.
> 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
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
