janhoy opened a new issue, #529:
URL: https://github.com/apache/solr-operator/issues/529

   As discussed in slack 
https://apachesolr.slack.com/archives/C022UMAPZ0V/p1676970790552379
   
   When the operator restarts the cluster, e.g. during a version upgrade, there 
is no guarantee that a Solr POD is marked as not ready before `solr stop` is 
called. Thus clients may experience connection error during the restart. 
   
   @HoustonPutman suggests we can implement a custom readiness gate 
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-readiness-gate
 to control this better.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to