Interestingly it was SOLR-179 (Ryan M) that added the prevention of error propagation because the idea was to start anyway and display a webpage of the error. But it was later partially undone by SOLR-1846 (Hossman), albeit left this bit, probably by mistake -- an oversight. Because it didn't quite work anyway. Regardless, Jetty still stays running albeit in a zombie state, 503; so again, it's not working as designed. This wart can be removed but won't address the matter. FWIW I have a WIP BATS test to try to demonstrate the issue.
Despite whatever rationale Jetty / specs have on staying started, we can take action to shut it down if that's best for Solr (and I think it is). I noticed the Solr Operator uses a liveness probe to /admin/info/system so in practice it may not be all that important in k8s. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
