You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2017/10/17 02:29:00 UTC
[jira] [Comment Edited] (SOLR-11478) Solr should remove it's entry
from live_nodes in zk immediately on shutdown and add after solr has loaded
it's cores and is ready to serve requests.
[ https://issues.apache.org/jira/browse/SOLR-11478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206914#comment-16206914 ]
Cao Manh Dat edited comment on SOLR-11478 at 10/17/17 2:28 AM:
---------------------------------------------------------------
bq. AFAIK Solr node that doesn't have any replicas for a collection - forwards all requests for this collection to other nodes. Shouldn't Solr node with replicas in DOWN state do the same? Thus /live_nodes entry can be present and all its replicas be DOWN - but node still be operational. WDYT?
Yeah, that sounds reasonable, but should we handle this in another ticket? Cause It is a different solution.
was (Author: caomanhdat):
bq. AFAIK Solr node that doesn't have any replicas for a collection - forwards all requests for this collection to other nodes. Shouldn't Solr node with replicas in DOWN state do the same? Thus /live_nodes entry can be present and all its replicas be DOWN - but node still be operational. WDYT?
Yeah, that sounds reasonable, but should we handle this in another ticket?
> Solr should remove it's entry from live_nodes in zk immediately on shutdown and add after solr has loaded it's cores and is ready to serve requests.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-11478
> URL: https://issues.apache.org/jira/browse/SOLR-11478
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Binoy Dalal
> Priority: Minor
>
> 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 down.
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org