[SERVER-82793] Wait for mongos to discover new primary before executing writes after stepdown in retryable_writes_retry_conflict.js Created: 03/Nov/23  Updated: 06/Nov/23  Resolved: 06/Nov/23

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

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Cluster Scalability 2023-11-13
Participants:
Linked BF Score: 30

 Description   

In retryable_writes_retry_conflict.js, we force a shard stepdown in some of the test cases, and quickly after attempt to execute a write on mongos. Retryable writes are not enabled, so if mongos hasn't yet received the new topology info, this write can fail with NotWritablePrimary e.g. We should ensure mongos knows the new primary before [attempting the writes|retryable_writes_retry_conflict.js].



 Comments   
Comment by Githook User [ 06/Nov/23 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-82793 Wait for mongos to discover new primary before executing writes after stepdown in retryable_writes_retry_conflict.js
Branch: master
https://github.com/mongodb/mongo/commit/7170c510ec7e1f0a532e7f35d7de73e0b66449f7

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