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 Thu, 03 Mar 2016 22:54:18 GMT


Scott Blum commented on SOLR-8777:

Not completely related, but it seems like there's a bug in jetty's SocketConnector.  It uses
the ServerSocket constructor that automatically binds the port, then attempts to set setReuseAddress(),
which makes no sense.  It should use the other constructor, set the reuse_address option,
then call bind() manually.

In other news, I don't know that there's a way to change Jetty's startup sequence.. the best
I could do is try to use reflection to pull the connectors off the Server and start them early.
 But that seems ungood.

I suppose we could spin for a while waiting for the previous ephemeral node to disappear,
and if it doesn't, error out and refuse to start?

> 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