Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.2, 3.7.1
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.6, v3.4
Sprint:
Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04
Linked BF Score:
68
Confidence Status:
None
Work Order:
3

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

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

initial_sync_drop_collection.js
3 kB
Oct 24 2017 03:37:15 PM UTC

depends on

SERVER-31695 Support read queries across collection renames

Backlog

is depended on by

SERVER-31466 CollectionCloner fails when a collection is dropped and re-created between getMores

Closed

is duplicated by

SERVER-31264 CollectionCloner should ignore NamespaceNotFound errors

Closed

related to

SERVER-32136 initial_sync_drop_collection.js should wait for system to stablize after restarting node

Closed

SERVER-32783 CollectionCloner::shutdown() should not block on resetting _verifyCollectionDroppedScheduler

Closed

SERVER-32089 Support rename collections during initial sync by retrying

Backlog

(1 related to)

Assignee:: Matthew Russotto
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Sep 26 2017 04:10:13 PM UTC
Updated:: Oct 30 2023 11:13:20 PM UTC
Resolved:: Nov 28 2017 04:33:21 PM UTC
Confidence Status Last Update:: 24/Oct/17 3:02 PM