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

Consider using a looser schema validation on config.settings

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 8.1.0-rc0, 8.0.0, 8.2.0-rc0
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-82609 updated the schema on config.settings to specify what a correct document in this collection should look like fairly strictly. However, there is no indication to the user upon upgrade to versions including this schema whether their documents are already invalid. This can lead to cases in which the user would like to turn on or off the balancer and is blocked from doing so due to their document failing validation for some other field.

      This can be worked around by directly updating the document with bypassDocumentValidation or can be fixed by identifying and fixing the problem in the document. The purpose of having the validation level be strict and the action being error is to ensure that users are notified of problems and prevented from inserting invalid documents.

      However, given that this has caused some issues for users we should consider whether some other configuration of settings would be more beneficial in this case.

            Assignee:
            Unassigned Unassigned
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: