[SERVER-73445] Use driver retryability in shard merge hook. Created: 30/Jan/23  Updated: 04/Oct/23  Resolved: 04/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-73129 Tenant migration hook retryability fa... Closed
Assigned Teams:
Serverless
Participants:

 Description   

Like SERVER-73129, we should use driver retryability in shard merge hook.



 Comments   
Comment by Matt Broadstone [ 04/Oct/23 ]

Closing as we have no current plan to make merge resilient to failover.

Comment by Suganthi Mani [ 30/Jan/23 ]

Note: Not an urgent one as shard merge is not resilient to failovers. So, we don't run passthrough suites for shard merge killing the primary or shutting down the primary in the middle of migration.

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