[SERVER-53033] Investigate usages on "not master" error messages in sharding unittests Created: 23/Nov/20  Updated: 29/Oct/23  Resolved: 02/Jul/21

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

Type: Improvement Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-07-12
Participants:

 Description   

The following tests seems to attach "not master" error messages to error codes like NotWritablePrimary when constructing errors. We should investigate whether these strings are necessary, otherwise we should change them to "not primary" to be more in line with the new error messages we'll return with the hello command:
dist_lock_catalog_impl_test
replset_dist_lock_manager_test
sharding_catalog_client_test
sharding_catalog_write_retry_test
sessions_collection_sharded_test



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 02/Jul/21 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-53033 Investigate usages on "not master" error messages in sharding unittests
Branch: master
https://github.com/mongodb/mongo/commit/ad76f3d82345b004a54010ba235f17c716eee0fd

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