[SERVER-37585] Make kill_primary_passthrough test smarter about killing primaries Created: 08/Oct/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Matthew Russotto Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: stm, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37500 Blacklist geo_s2ordering from replica... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

SERVER-37500 blacklists a test from the replica_sets_kill_primary_jscore_passthrough which adds a lot of data. The problem is that the primary will take longer than the kill interval to recover, which means from the perspective of the test, the primary never comes up and the test fails. It would be better if we could avoid having to do this; the test should wait until the primary has fully recovered before making it eligible to kill again.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Max Hirschhorn [ 12/Oct/18 ]

This had come up in other BF tickets. I think the proper way to do this would involve making the Python thread inside of resmoke.py that's doing the stepdowns communicate with the client thread inside the mongo shell to know when the mongo shell has successfully retried the operation after a failover occurred. It wouldn't be a small amount of work to make this happen.

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