[SERVER-27541] Turn off primary catchup in all continuous stepdown suites Created: 29/Dec/16  Updated: 30/Apr/18  Resolved: 30/Apr/18

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Vesselina Ratcheva (Inactive)
Resolution: Done Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-04-23, Repl 2018-05-07
Participants:
Linked BF Score: 62

 Description   

We already do force stepdowns against the primary, if we also turn the catchupTimeoutMillis to 0 then we should start getting rollbacks in the csrs stepdown suite, which will get us additional test coverage of rollback for free.



 Comments   
Comment by Githook User [ 30/Apr/18 ]

Author:

{'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb', 'name': 'Vesselina Ratcheva'}

Message: SERVER-27541 Turn off primary catchup in all continuous stepdown suites
Branch: master
https://github.com/mongodb/mongo/commit/5d1ace4f94df04670f95eadca17a9275d65625ac

Comment by Judah Schvimer [ 26/Jan/18 ]

No, I think we could do this at any point. The stepdown suite doesn't do concurrent rollbacks so it should be safe.

Comment by Daniel Gottlieb (Inactive) [ 26/Jan/18 ]

Are we only interested in switching this over once recoverable rollback becomes the default for WT?

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