[
https://issues.apache.org/jira/browse/SOLR-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952759#comment-17952759
]
Mark Robert Miller commented on SOLR-17765:
-------------------------------------------
There is no reason to log it. The replicas will be considered down because the
zk live node will be gone - in this case it's already gone, and correctness
wise the only publish down that matters happens on startup.
> Nodes should publish themselves as DOWN ASAP during shutdown
> ------------------------------------------------------------
>
> Key: SOLR-17765
> URL: https://issues.apache.org/jira/browse/SOLR-17765
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-17765.patch
>
>
> While working on SOLR-17744 i noticed this comment in
> {{CoreContainerProvider.close()}} (that seems to date back to SOLR-15590) ...
> {noformat}
> // Mark Miller suggested that we should be publishing that we are down before
> anything else
> // which makes good sense, but the following causes test failures, so that
> improvement can be
> // the subject of another PR/issue. Also, jetty might already be refusing
> requests by this point
> // so that's a potential issue too. Digging slightly I see that there's a
> whole mess of code
> // looking up collections and calculating state changes associated with this
> call, which smells
> // a lot like we're duplicating node state in collection stuff, but it will
> take a lot of code
> // reading to figure out if that's really what it is, why we did it and if
> there's room for
> // improvement.
> // if (cc != null) {
> // ZkController zkController = cc.getZkController();
> // if (zkController != null) {
> // zkController.publishNodeAsDown(zkController.getNodeName());
> // }
> // }
> {noformat}
> ...I'm creating this Jira because I see no other existing Jira addressing
> this idea.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
