lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <>
Subject [jira] [Resolved] (SOLR-11478) Solr should remove itself from live_nodes in zk immediately on shutdown
Date Fri, 20 Oct 2017 08:23:00 GMT


Cao Manh Dat resolved SOLR-11478.
       Resolution: Fixed
    Fix Version/s: master (8.0)

> Solr should remove itself from live_nodes in zk immediately on shutdown
> -----------------------------------------------------------------------
>                 Key: SOLR-11478
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Binoy Dalal
>            Assignee: Cao Manh Dat
>            Priority: Minor
>             Fix For: 7.2, master (8.0)
>         Attachments: SOLR-11478.patch
> Solr currently, upon receiving the stop command, removes its entry from the zk /live_nodes
znode after it has finished processing all inflight requests, just before finally shutting
> In this case, any applications that depend on a solr node's live_node entry to decide
whether or not to query it fail once the stop command has been executed but solr has not yet
fully shut down.
> Something similar occurs during startup of a solr node. The solr node seems to add it's
entry to the /live_nodes in zk once it is up but before it has started accepting requests
and once again, this causes dependent applications to fail in a similar fashion.
> Hence, removal of the node entry and addition of the same to the zk live_nodes immediately
upon shutting down and at the very end upon coming up respectively will greatly benefit applications
that depend the live_nodes znode.

This message was sent by Atlassian JIRA

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

View raw message