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

Collection validator rule is mismatched across nodes after failed collMod command

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 3.2.7, 3.3.9
    • 3.2.12, 3.3.15
    • Storage
    • Fully Compatible
    • ALL
    • v3.2
    • TIG 18 (08/05/16), TIG 2016-09-19, TIG 2016-10-10
    • 0

    Description

      This bug affects 3.2.7 and master. It leads to a primary and secondary having different collection validation rules:

      ----
      Collection info for primary
      ----
      [
      	{
      		"name" : "collmod",
      		"options" : {
      			"validator" : {
      				"a" : {
      					"$eq" : "z"
      				}
      			},
      			"validationLevel" : "off",
      			"validationAction" : "error"
      		}
      	}
      ]
       
      ----
      Collection info for secondary
      ----
       
      [
      	{
      		"name" : "collmod",
      		"options" : {
      			"validator" : {
      				"a" : {
      					"$eq" : "z"
      				}
      			},
      			"validationLevel" : "strict",
      			"validationAction" : "error"
      		}
      	}
      ]
      

      Attachments

        Issue Links

          Activity

            People

              robert.guo@mongodb.com Robert Guo
              kamran.khan Kamran K.
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: