Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- former-quick-wins
- quick_wins

Assigned Teams:

Replication
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

applyOperation_inlock() needs the collection lock held before calling the function, which may throw a NamespaceNotFound error. As a result, all callers have to handle NamespaceNotFound correctly for idempotency reasons. We should unify the logic.

is related to

SERVER-73661 Improve applyOperation_inlock() API.

Backlog

SERVER-34319 unify exception and error status handling in applyOplogBatchPerWorker

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Siyuan Zhou
Participants:: [DO NOT USE] Backlog - Replication Team, Matthew Russotto, Ratika Gandhi, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: May 29 2019 07:02:35 PM UTC
Updated:: Apr 13 2023 03:56:20 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates