[SERVER-13968] Report invalid collection options in "<db>.system.namespaces" in upgrade checker Created: 16/May/14  Updated: 10/Dec/14  Resolved: 20/May/14

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

Type: Bug Priority: Major - P3
Reporter: Shaun Verch Assignee: Matt Dannenberg
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-6947 db.createCollection creates undefined... Closed
is related to SERVER-13737 CollectionOptions parser should skip ... Closed
is related to SERVER-13927 Copydb breaks on (some) capped collec... Closed
is related to SERVER-13976 Cloner needs to detect failure to cre... Closed
Operating System: ALL
Participants:

 Description   

The tickets SERVER-13737 and SERVER-13927 both are a result of bad collection options.

The issue is that the collection options in "<db>.system.namespaces" can have fields in it that are invalid but not checked in 2.4. Since 2.6 has stricter validation, this causes problems with upgrading (manifested in the two tickets above).

Also need to add startup warning with remediation steps for this scenario.

See SERVER-6947 for an example of how these bad options can get in.



 Comments   
Comment by Daniel Pasette (Inactive) [ 20/May/14 ]

See SERVER-13737 – we've decided to relax the option checking here so this is no longer required.

Generated at Thu Feb 08 03:33:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.