[SERVER-38890] Make geo_near_sharded.js and stale_mongos_updates_and_removes.js start shards as replica sets instead of standalones after completion of causally consistent catalog cache refresh methods Created: 08/Jan/19  Updated: 29/Oct/23  Resolved: 01/Oct/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.5, 4.1.6
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-38894 Change tests to use replica set shard... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-10-21
Participants:

 Description   

The tests geo_near_sharded.js and stale_mongos_updates_and_removes.js both reference SERVER-33954 to be able to make the switch from a standalone shard to a shard-as-replica-set. However, SERVER-33954 is already completed. This ticket tracks said change for these tests.



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

Author:

{'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com', 'name': 'Cheahuychou Mao'}

Message: SERVER-38890 Make geo_near_sharded.js and stale_mongos_updates_and_removes.js start shards as replica sets instead of standalones after completion of causally consistent catalog cache refresh methods
Branch: master
https://github.com/mongodb/mongo/commit/6d411c32e4d7c54e13efed45cc52ad27b6d71438

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