[SERVER-39145] Modify no_disconnect_on_stepdown.js such that it test the write operations are killed during step down. Created: 23/Jan/19  Updated: 29/Oct/23  Resolved: 06/Feb/19

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-02-11
Participants:

 Description   

All the CRUD operations (including linearizable read concern) in no_disconnect_on_stepdown.js test, are
taking the failpoints before we acquire RSTL lock. As a result step down does not kill those write operations.

For eg., consider insert operations, hangDuringBatchInsert failpoint got enabled at line at line 354 whereas we acquire the rstl lock only at line 371.

Currently, no_disconnect_on_stepdown test is testing only closing connection part and not killing operations on step down path. So, add new fail points in those CRUD operations such that the fail points are enabled after holding rstl lock and step down kills those operations and operations get an error code as ErrorCodes::InterruptedDueToStepDown.

Also, worth mentioning that currently we already have a test for linearizable read concern which tests killing operations on step down path.



 Comments   
Comment by Githook User [ 06/Feb/19 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}

Message: SERVER-39145 Modify no_disconnect_on_stepdown.js to test that the write operations are killed during step down.
Branch: master
https://github.com/mongodb/mongo/commit/961b7181588a2dbd9eee67e4f5fcd569602d59b5

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