Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-13968

Report invalid collection options in "<db>.system.namespaces" in upgrade checker

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Admin, Usability
    • None
    • ALL

      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.

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            sverch Shaun Verch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: