[SERVER-40071] sharded_backup_restore tests should use retryable writes Created: 11/Mar/19  Updated: 14/Mar/19  Resolved: 14/Mar/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-40091 sharded_backup_restore tests should d... Closed
Operating System: ALL
Sprint: Storage NYC 2019-03-25
Participants:
Linked BF Score: 0

 Description   

This is only a simple test-fix.
sharded_backup_restore tests have a writer thread which continuously sends writes to mongos. If there is an election happening on one of the shards, the write command might have transient "NotMaster" error. To prevent the test from failing due to that error, we should make the write command retryable by starting the session with *

{retryWrites: true}

*



 Comments   
Comment by Xiangyu Yao (Inactive) [ 14/Mar/19 ]

I realized a better test fix would be to disallow stepdown to happen in sharded_backup_restore tests. SERVER-40091 will then fix its own BF and the BF linked to this ticket.

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