[SERVER-42745] Simplify StaleDbVersion handling on the batch write path on routers Created: 09/Aug/19  Updated: 29/Oct/23  Resolved: 24/Oct/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-10-21, Sharding 2019-11-04
Participants:

 Description   

Currently the batch write path handles receiving StaleDbVersion errors with different versions, but it is never expected for a single round of sending requests to targeted shards to return write errors with StaleDbVersions with different versions.

This is because (1) database version is only attached when targeting a single shard (the primary shard), and (2) the shard will stop processing the batch after encountering the first StaleDbVersion error and will copy the same StaleDbVersion error into the unprocessed writes.

Simplifying the StaleDbVersion handling code on mongos reduces the test surface necessary to get full code coverage.



 Comments   
Comment by Githook User [ 24/Oct/19 ]

Author:

{'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}

Message: SERVER-42745 Simplify StaleDbVersion handling on the batch write path on routers
Branch: master
https://github.com/mongodb/mongo/commit/b4aa65fde0a61a8a8e2f7c439f928215b23c14e0

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