[SERVER-67228] no_disconnect_on_stepdown.js should not strictly test the number of operations killed Created: 13/Jun/22  Updated: 29/Oct/23  Resolved: 10/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Vishnu Kaushik
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: Repl 2022-06-27, Repl 2022-07-11, Repl 2022-08-08, Repl 2022-08-22, Repl 2022-09-05, Repl 2022-09-19, Repl 2022-07-25, Repl 2022-10-03, Repl 2022-10-17
Participants:
Linked BF Score: 12

 Description   

As the server code keeps evolving, there may be any number of operations started by the primary when it steps up. no_disconnect_on_stepdown.js was written under the assumption that there weren't any operations started by the primary itself.

In this test, we
1) step up a primary
2) issue a write that hangs
3) step down the primary
4) assert that exactly one operation was killed

The assertion breaks if the primary itself launched a few operations on step up. When that's the case, we may kill more than one operation.

We can change the assertion to be "at least one operation is killed" and we can make sure the operation was killed with the right error code.



 Comments   
Comment by Githook User [ 10/Oct/22 ]

Author:

{'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-67228 no_disconnect_on_stepdown.js should not strictly test the number of operations killed
Branch: master
https://github.com/mongodb/mongo/commit/29b77de32daadd7e9d2b84d51de61579fe8953e4

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