[SERVER-62372] Handle exceptions thrown during onTransitionToPrimary Created: 05/Jan/22  Updated: 27/Oct/23  Resolved: 07/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

The sharding hooks executed when a node transitions to primary can potentially throw exceptions (e.g. this call may throw).

Currently, the node would crash in case this happens because the callback executed as part of OplogApplier::startup() is flagged as noexcept.



 Comments   
Comment by Pierlauro Sciarelli [ 07/Jan/22 ]

Closed, as max.hirschhorn pointed out that the node crashes and that's the correct behavior in case the vector clock can't be recovered on transition to primary

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