[SERVER-43849] Write NotMaster error in upgrade_downgrade_cluster due to stale RS status in mongos Created: 04/Oct/19  Updated: 29/Oct/23  Resolved: 15/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc2, 4.7.0

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on WT-5964 4.2 unable to open properly downgrade... Closed
is depended on by SERVER-42982 Unblacklist multiVersion/upgrade_down... Closed
Duplicate
is duplicated by SERVER-43852 Make upgrade_downgrade_cluster.js sta... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Sharding 2020-04-20
Participants:

 Description   

The upgrade_downgrade_cluster.js intermittently fails due to NonMaster write error. The root cause is that mongos does not retry the write with update ReplicaSetMonitor config.
The suggested fix is to either wait for the isMaster status in mongos before performing the testCRUDAdnAgg
or retry the write on error.

Once the issue is fixed the test should be unblacklisted



 Comments   
Comment by Githook User [ 15/Apr/20 ]

Author:

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

Message: SERVER-43849 Write NotMaster error in upgrade_downgrade_cluster due to stale RS status in mongos

(cherry picked from commit a0482756e33a25a2df17eaf718ca6a3072147531)
Branch: master
https://github.com/mongodb/mongo/commit/90968f34ca6774ba7c71e3bc3453d9a29c55623e

Comment by Githook User [ 14/Apr/20 ]

Author:

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

Message: SERVER-43849 Write NotMaster error in upgrade_downgrade_cluster due to stale RS status in mongos
Branch: v4.4
https://github.com/mongodb/mongo/commit/a0482756e33a25a2df17eaf718ca6a3072147531

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