[
https://issues.apache.org/jira/browse/SOLR-17764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143906#comment-18143906
]
ASF subversion and git services commented on SOLR-17764:
--------------------------------------------------------
Commit 3b22901c4ece2c2dd7bc9e4d3c34f651371e095b in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=3b22901c4ec ]
SOLR-17764: Widen Cloud client's 503 response handling (#5315)
Prior to this commit CloudSolrClient invalidated its cached clusterstate
and retried on only a subset of 503 responses. This narrow handling
gave us incomplete coverage for the node-shutdown case: comm or IO
errors caused by a shutdown would be retried, but 503s from "graceful"
Jetty shutdown were not retried and caused errors.
This commit widens the existing 503 handling to include the sort of 503s
typically seen on node-shutdown. It makes SOLR_JETTY_GRACEFUL a
more viable option for CloudSolrClient users.
> "graceful" jetty shutdown causes ChaosMonkeySafeLeaderWithPullReplicasTest
> failures
> -----------------------------------------------------------------------------------
>
> Key: SOLR-17764
> URL: https://issues.apache.org/jira/browse/SOLR-17764
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
> Labels: pull-request-available
> Attachments:
> E7F93005B9386058.OUTPUT-org.apache.solr.cloud.ChaosMonkeySafeLeaderWithPullReplicasTest.txt
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Reviewing recent jenkins test failure metrics, I noticed that (Nightly) test
> ChaosMonkeySafeLeaderWithPullReplicasTest started failing ~60% of the time
> right around the time that SOLR-17744 was committed.
> Things i have observed:
> * Seeds from failing runs seem to reliably reproduce the failure
> ** These failures do *NOT* reproduce if i revert to just before SOLR-17744
> * Ad-hoc testing I've done of seeds that do _not_ fail on first attempt seem
> to reliably succeed on all subsequent attempts
> ** Suggesting that the root cause is something deterministic in the
> {{{}random(){}}}-ness of the test, and not something dependent on timing or
> concurrency.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
