[SERVER-48313] backup_cursor_extend_waiting_logic.js needs to be disable or be resilient to elections Created: 20/May/20  Updated: 29/Oct/23  Resolved: 08/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
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: Execution Team 2020-06-15
Participants:
Linked BF Score: 11

 Description   

The test instantiates a sharded cluster and inserts a bunch of data, asserting the inserts work. Those assertions fail if there's an election that chooses a new primary.

It's actually valuable that extending a backup cursor is exercised with elections. Unfortunately extending a cursor is expected to fail when terms change on nodes with majority read concern off. I want my cake and to eat it too.

I'm inclined to have that test work in the the eMRC=on and off case and turn off elections (other backup restore tests are actually more likely to have elections). We can leave a TODO for once eMRC=off is removed from the server. The TODO would be to change this test to allow elections, but have the inserts be resilient to failover.



 Comments   
Comment by Githook User [ 05/Jun/20 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-48313: Disable elections for backup_cursor_extend_waiting_logic.js.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/893416a90f284b554ada129d2c3ac5788c7d5fa8

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