[
https://issues.apache.org/jira/browse/SOLR-16722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706383#comment-17706383
]
Jan Høydahl commented on SOLR-16722:
------------------------------------
Here's what I found by looking more in the code:
# bin/solr stop will send a STOP command to Jetty's STOP_PORT with
not-so-secret stop key
# Jetty starts the shutdown process
# Solr is notified about the shutdown through a callback in
CoreContainerProvider. At this point, "All servlets and filters will have been
destroyed"
# CoreContainerProvider#close() is called which calls CC#shutdown
# CC shuts down every core on the nodem and then calls zkController#preClose
# ZkController#preClose removes ephemeral live_nodes/myNode and then publishes
down state in state.json
# Wait for shutdown and exit
> API to flag a solr node NOT READY for requests
> ----------------------------------------------
>
> Key: SOLR-16722
> URL: https://issues.apache.org/jira/browse/SOLR-16722
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> Spinoff from solr operator PR
> [https://github.com/apache/solr-operator/issues/529]
> When solr-operator performs a rolling restart or rolling upgrade, it will
> stop one node at a time, but SolrJ (both external and internal) will continue
> sending traffic to the node until requests start failing, since at the time
> SolrJ picks up the "live_nodes" change, it is too late.
> While the operator PR mentioned above will prevent external requests through
> the k8s service to the draining node, it will not prevent internal traffic.
> This issue thus aims to introduce some API or mechanism to flag a Solr node
> as NOT READY for traffic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
