Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Linked BF Score:
200
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

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

The current implementation of ReshardingOplogFetcher::_reschedule can lead to a variable length future chains as the function can recursively call itself. Debug builds will hit an invariant if the future chain length reaches 32.

Update to use AsyncTry instead of recursively calling itself.

is duplicated by

SERVER-103750 Avoid variable length future chaining in ReshardingOplogFetcher

Closed

is related to

SERVER-98942 Fix potential variable length future chain in resharding_coordinator_commit_monitor

Closed

related to

SERVER-106341 Fix race condition in ReshardingOplogFetcherTest

In Progress

Assignee:: Ben Gawel
Reporter:: Ben Gawel
Participants:: Ben Gawel, Githook User
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jun 05 2025 12:57:37 PM UTC
Updated:: Jun 20 2025 07:52:56 PM UTC
Resolved:: Jun 10 2025 01:39:24 PM UTC
Confidence Status Last Update:: 05/Jun/25 1:00 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates