[SERVER-60975] Make ReplicaSetMonitorRemoved retryable Created: 25/Oct/21  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: neweng, sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-51329 Unexpected non-retryable error when s... Closed
Assigned Teams:
Cluster Scalability
Participants:
Story Points: 2

 Description   

When a driver gets a ReplicaSetMonitorRemoved error we want to be able to retry it since this exception is returned to the client. It's highly likely the operation would succeed on a different (or even the same) server. Ideally we would want a way to express this through a label, say RetryableError, but not tied directly to the type of operation (read/write) like RetryableWriteError does.


Generated at Thu Feb 08 05:51:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.