Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.6.0-rc0
Component/s: Querying, Replication, Storage
Labels:
None

Assigned Teams:

Query Execution
Linked BF Score:
5
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

When we are querying a collection during initial sync, we do the initial find by UUID. However, subsequent getMore commands are done by name, which is a problem if the collection is renamed. We cannot distinguish a dropped collection from a renamed one because in the getMore has only the old name and thus cannot look up the collection or the cursor.

is depended on by

SERVER-31267 CollectionCloner fails if collection is dropped between getMore calls

Closed

SERVER-37720 Allow active index builds during renameCollection

Blocked

related to

SERVER-32089 Support rename collections during initial sync by retrying

Backlog

tested by

SERVER-42606 Create test that initial sync can clone a collection while that collection is renamed

Closed

Assignee:: [DO NOT USE] Backlog - Query Execution
Reporter:: Matthew Russotto
Participants:: [DO NOT USE] Backlog - Query Execution, Andy Schwerin, David Storch, Eric Milkie, Geert Bosch, Matthew Russotto, Spencer Brody
Votes:: 1 Vote for this issue
Watchers:: 21 Start watching this issue

Created:: Oct 24 2017 03:34:05 PM UTC
Updated:: Aug 05 2024 07:42:38 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates