[SERVER-43401] Add a StaleConfig error code to transaction_reject_writes_for_moved_chunks test case Created: 20/Sep/19  Updated: 06/Dec/22  Resolved: 14/Oct/19

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 9

 Description   

The BF-14549 failure happens when recipient shard fails to update its routing table once the moveChunk completes.
As such it issues a StaleConfig error on the attempt to insert instead of the expected MigrationConflict (https://github.com/mongodb/mongo/blob/v4.2/jstests/sharding/transactions_reject_writes_for_moved_chunks.js#L129)
The proposed fix is to either add the StaleConfig to the list of allowed errors as its expected behavior or make sure that the recipient routing table is updated before the insert.
In both cases it's a test case change.



 Comments   
Comment by Ratika Gandhi [ 14/Oct/19 ]

Need more details to solve the linked BF

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