Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.0
Sprint:
ClusterScalability 30Mar-13Apr
Linked BF Score:
200
CAR Domain/s:
None

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

It is possible to miss recording the final "ReshardDoneCatchUpChangeEventO2Field" entry in the oplog if the recipient steps down after transitioning to the strict-consistency state but before writing this entry to the oplog due to this condition.

is related to

SERVER-108642 Resharding services need to handle failures after state transitions

Open

SERVER-50636 Write reshardDoneCatchUp no-op oplog entry after recipient has caught up to all donor shards

Closed

related to

SERVER-125759 Unit test SkipsDuplicateOplogEntryOnRecoveryInStrictConsistency fails sporadically

Closed

Assignee:: Jordan Glassley
Reporter:: Nandini Bhartiya
Participants:: Githook User, Jordan Glassley, Nandini Bhartiya, TPM Jira Automations Bot
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Apr 03 2026 01:27:32 PM UTC
Updated:: Apr 29 2026 10:20:27 PM UTC
Resolved:: Apr 08 2026 07:37:14 PM UTC