-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
ORIGINAL TITLE: Investigate changes in SERVER-58018: Creating a collection on standalone node that was part of a replica set may lead to fassert
If the following sequence of events occurs:
1. Node n in replica set is restarted as standalone
2. User creates a replicated collection on n
3. n rejoins the replica set
In this case, the collection created on n in standalone mode would have a different UUID compared to the rest of the replica set. As a result, any subsequent operations on that collection would lead to an fassert.
Should we update the docs around creating a replicated collection in standalone mode to inform users of this potential issue? This may help inform users about having collections with mismatched UUIDs. Thank you!
Description of Linked Ticket
If the following sequence of events occurs:
- Node n in replica set is restarted as standalone
- User creates a replicated collection on n
- n rejoins the replica set
In this case, the collection created on n in standalone mode would have a different UUID compared to the rest of the replica set. As a result, any subsequent operations on that collection would lead to an fassert.
To help alleviate this, one idea is require an explicit UUID when creating this new collection, if the node is currently in standalone mode but was previously part of a replica set.
Alternatively, we can add warning logs when the node attempts to create replicated collections in standalone mode.
- documents
-
SERVER-58018 Creating a collection on standalone node that was part of a replica set may lead to fassert
-
- Closed
-