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

cleanupOrphan with invalid writeConcern is accepted

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • 2.7.6
    • Sharding
    • ALL

    Description

      The following writeConcerns, when specified for cleanupOrphan, do not generate an error:

      • writeConcern: { w: null }
      • writeConcern: { w: undefined }
      • writeConcern: { w: NaN }

      Cleaning up orphaned on shard test-rs0 {
      	"cleanupOrphaned" : "test.secondaryThrottle_cleanupOrphans",
      	"startingAtKey" : {
      		"shardKey" : 499
      	},
      	"_secondaryThrottle" : true,
      	"writeConcern" : {
      		"w" : null
      	}
      }
       m31100| 2014-09-17T10:13:34.462-0400 I SHARDING [conn233] remotely refreshing metadata for test.secondaryThrottle_cleanupOrphans based on current shard version 2|1||541996e9a9941a160764d0fb, current metadata version is 2|1||541996e9a9941a160764d0fb
       m31100| 2014-09-17T10:13:34.462-0400 I SHARDING [conn233] metadata of collection test.secondaryThrottle_cleanupOrphans already up to date (shard version : 2|1||541996e9a9941a160764d0fb, took 0ms)
       m31100| 2014-09-17T10:13:34.462-0400 I SHARDING [conn233] Deleter starting delete for: test.secondaryThrottle_cleanupOrphans from { shardKey: MinKey } -> { shardKey: 500.0 }, with opId: 13455
       m31100| 2014-09-17T10:13:34.462-0400 I SHARDING [conn233] rangeDeleter deleted 0 documents for test.secondaryThrottle_cleanupOrphans from { shardKey: MinKey } -> { shardKey: 500.0 }

      Attachments

        Activity

          People

            Unassigned Unassigned
            jonathan.abrahams Jonathan Abrahams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: