[SERVER-32020] rollback_with_socket_error_then_steady_state.js should await secondary nodes before db hash checks Created: 17/Nov/17  Updated: 30/Oct/23  Resolved: 21/Nov/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc5

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Backlog - Replication Team
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

We re-connect all nodes at the end of the test so we can do a db hash check, but we don't wait for any rollbacks to finish, so it is possible we end up calling awaitReplication while a node is in rollback. This leads to us ignoring the node and not waiting for it to catch up. We should await secondary nodes after re-connection and before starting db hash checks.



 Comments   
Comment by Githook User [ 21/Nov/17 ]

Author:

{'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}

Message: SERVER-32020 rollback_with_socket_error_then_steady_state.js should await secondary nodes
Branch: master
https://github.com/mongodb/mongo/commit/b56de392a17c1b074dd71fb437a15d70318f132f

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