-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution EMEA Team 2023-07-24, Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18
-
157
In SERVER-68122 and linked tickets, it was discovered that ephemeral ESE options could become persisted in replicated catalog metadata.
Between SERVER-68122 and SERVER-72227, we have a plan for mitigating the impact of this issue, and preventing the options from getting persisted again in the future.
However, this will leave us with redundant and stale information in the catalog. We should, during a major FCV upgrade, make servers scan their catalogs and remove this stale information. Finally, in a future release, we can remove the mitigations.
- causes
-
SERVER-81986 `list_collections1.js` should ignore `db.system.profile` collection when calling `listCollections` cmd
- Closed
- depends on
-
SERVER-68122 Investigate replicating the collection WiredTiger config string during initial sync
- Closed
-
SERVER-72227 Investigate how ESE WiredTiger configuration string arguments may appear in replicated catalog data
- Closed
- is related to
-
SERVER-81779 Investigate whether to sanitize collection options upon creation during moveChunk/movePrimary/resharding
- Closed
-
SERVER-80490 Cleanup SERVER-72229 FCV upgrade step
- Backlog
- related to
-
SERVER-85925 slow setFCV upgrade operation may write database profiling data to non-admin database
- Closed
-
SERVER-79496 Ban encryption options being provided in createCollection
- Closed