Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Cluster Scalability
Operating System:
ALL
Linked BF Score:
0
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

In the ReshardingDonorService and ReshardingRecipientService we wait for the change streams monitor to finish and set the status of the monitor on the change streams monitor promise.

We also need to return the status so that proper error handling is done by the state machine if the change streams monitor failed.

Example where we do not return the status

Example of what we should do

is related to

SERVER-108852 Resharding participants don't handle change streams monitor failures immediately

Backlog

SERVER-110364 Resharding data replication should not restart cloner when rebuilt after a failover while building indexes

Closed

Assignee:: Unassigned
Reporter:: Ben Gawel
Participants:: Ben Gawel
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Aug 08 2025 05:59:27 PM UTC
Updated:: Sep 10 2025 07:46:54 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates