Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- neweng

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

If the collection doesn't exist for an operation we need to apply in SyncTail, SyncTail will take the locks to create the collection here. For update operations, the collection will be implicitly created, for insert operations, a NamespaceNotFound error will be returned, added in ~~SERVER-17634~~. Update operations should return a similar error and we should revisit if we want to take the locks on the collection in SyncTail at all.

is related to

SERVER-27164 Deadlock during oplog application when implicitly creating multiple collections on the same DB

Closed

SERVER-21700 Do not relax constraints during steady state replication

Closed

SERVER-17634 do not apply replicated insert operations on missing collections

Closed

related to

SERVER-27834 Index builds during initial sync should not implicitly create collections

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Judah Schvimer
Participants:: [DO NOT USE] Backlog - Replication Team, Judah Schvimer, Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Nov 29 2016 04:55:15 PM UTC
Updated:: Dec 06 2022 04:10:48 AM UTC
Resolved:: Feb 13 2020 10:22:31 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates