[SERVER-30786] safe_secondary_reads_*.js tests are racy Created: 22/Aug/17  Updated: 30/Oct/23  Resolved: 12/Sep/17

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

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

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-02
Participants:
Linked BF Score: 0

 Description   

*_single_migration_waitForDelete.js and *_single_migration_suspend_range_deletion.js need to use majority write concern for the moveChunk ops, so the chunk metadata update write is carried to the secondary before trying a versioned call against the secondary.

_drop_reacreate.js must use forceRoutingTableRefresh on the shard primary followed by the wait for replication shell helper.



 Comments   
Comment by Ramon Fernandez Marina [ 12/Sep/17 ]

Author:

{'username': u'DiannaHohensee', 'name': u'Dianna Hohensee', 'email': u'dianna.hohensee@10gen.com'}

Message:SERVER-30786 Fix races between metadata propagation to secondary and versioned secondary request in safe_secondary_reads_*.js tests
Branch:master
https://github.com/mongodb/mongo/commit/54f04e18005939b0357e411e5a34528301f3c7ef

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