[SERVER-63620] Evaluate locations that throw WriteConflictExceptions without a real write conflict Created: 14/Feb/22  Updated: 06/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Josef Ahmad Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: storex-ranked, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-60839 Introduce a TemporarilyUnavailable er... Closed
is related to SERVER-77542 Internal operations should handle Tem... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

We sometimes use write conflict exceptions for events that are actually unrelated to write conflicts (example). Audit these locations and determine whether they warrant a using a different error code and handling policy (e.g. TemporarilyUnavailable).



 Comments   
Comment by Connie Chen [ 25/Oct/22 ]

The work in this ticket should be to complete the audit and then file tickets separately for instances to use a different error code. 

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