Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Server Serverless 2022-06-27, Server Serverless 2022-07-11
-
116
Description
When recipients are removed from the donor set and a primary on the recipient side is elected, the shard_split_donor_service will run and check to do the recipient state document cleanup.
However if that logic fails we should handle any potential error and avoid any extra logic to be ran for the recipient cleanup (decision and completion promise).
Additionally we should add logging when the recipient state document is successfully removed which would help troubleshoot any future ticket.
I also think it is worth investigating if we should remove the fsync logic within the assert.soon
We most likely only need to do that when we do the first commitShardSplit. Not at each retrytable error.