[SERVER-41055] Do not expose stale errors to user when changing document shard key Created: 08/May/19  Updated: 13/May/19  Resolved: 13/May/19

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

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2019-05-20
Participants:

 Description   

When changing a document's shard key, mongos starts a transaction if the original update was sent as a retryable write. If this transaction fails, mongos reports to the user whatever error the shard reported. If the shard reports a stale error however, we should not report this to the user.


Generated at Thu Feb 08 04:56:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.