lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <>
Subject [jira] [Commented] (SOLR-8777) Duplicate Solr process can cripple a running process
Date Wed, 02 Mar 2016 19:58:18 GMT


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:
>             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

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

View raw message