[SERVER-51052] no_disconnect_on_stepdown.js should enable a failpoint to skip PrimaryOnlyService instance rebuild Created: 18/Sep/20  Updated: 29/Oct/23  Resolved: 20/Sep/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.8.0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-05
Participants:
Linked BF Score: 18

 Description   

Each PrimaryOnlyService rebuilds its instances on stepup by doing a read against the state machine collection via DBDirectClient using an opCtx that is interruptible on stepdown. So it is expected that the read operation is interrupted when this test forces the primary to step down. So this test should use a failpoint to skip PrimaryOnlyService instance rebuild.



 Comments   
Comment by Githook User [ 20/Sep/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-51052 no_disconnect_on_stepdown.js should enable a failpoint to skip PrimaryOnlyService instance rebuild
Branch: master
https://github.com/mongodb/mongo/commit/99b136078c726df92a19d8ed5feb37a920369a16

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