[SERVER-58018] Creating a collection on standalone node that was part of a replica set may lead to fassert Created: 23/Jun/21  Updated: 06/Dec/22  Resolved: 06/Jul/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Xuerui Fa Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-14626 [SERVER] Creating a collection on sta... Closed
Related
Assigned Teams:
Replication
Participants:
Case:

 Description   

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.

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.


Generated at Thu Feb 08 05:43:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.