[SERVER-81594] Handle StaleDBVersion errors Created: 29/Sep/23  Updated: 21/Nov/23  Resolved: 21/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Abdul Qadeer Assignee: Abdul Qadeer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Participants:

 Description   

The current code for PM-3190 only deals with StaleConfig errors arising out of stale config metadata. It is also possible to receive a StaleDBVersion error if a movePrimary command is run in between the execution of a large batch of writes. We should kick in the retry protocol for broadcast if we encounter such an error when attempting updateOne or deleteOne relevant to this project.



 Comments   
Comment by Githook User [ 20/Nov/23 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-81594 SERVER-54019 Add tests
Branch: master
https://github.com/mongodb/mongo/commit/a1c223397a0f64e9eb5a730c2d502904d60c1c23

Generated at Thu Feb 08 06:46:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.