Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Do
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

This would solve the issue described in SERVER-50143. We should also add some visibility on how many documents are left (either via the removeShard response object or metrics or some other means)

is fixed by

SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare

Backlog

is related to

SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare

Backlog

SERVER-89179 Create database concurrent with removeShard can create the new db on a removed shard

Closed

Assignee:: Unassigned
Reporter:: Randolph Tan
Participants:: Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jul 18 2024 08:53:28 PM UTC
Updated:: Aug 06 2024 03:01:49 PM UTC
Resolved:: Jul 26 2024 01:15:06 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates