[SERVER-56708] Create collection coordinator blindly ignores all exceptions after failover Created: 06/May/21  Updated: 27/Oct/23  Resolved: 12/May/21

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

Type: Bug Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Marcos José Grillo Ramirez
Resolution: Gone away Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File check_step_down_on_rollback.js     Text File step_down_diff.patch    
Operating System: ALL
Participants:

 Description   

The create collection coordinator ignores all the possible thrown exceptions while reverting partial changes after primary failover. While performing the revert operations, some remote node (either CS or another shard) could through a step-down error. In this case the coordinator is wrongly ignoring it and proceeds assuming the partial changes have been correctly reverted.



 Comments   
Comment by Marcos José Grillo Ramirez [ 12/May/21 ]

Fixed by SERVER-56672

Comment by Tommaso Tocci [ 11/May/21 ]

marcos.grillo I've reviewed the attached test and it seems fine, so I think we can considered this ticket fixed.

Comment by Marcos José Grillo Ramirez [ 11/May/21 ]

This was solved by a combination of SERVER-56672 and SERVER-56560, the attached test ran after applying the attached diff confirms this is no longer happening.

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