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

UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.8.0-rc5
    • Fix Version/s: 2.6.8, 3.0.0-rc7
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:

      Description

      Original description:
      sharding/array_shard_key.js fails with a mixed version cluster

      If you run the set with a config as follows:

      var config = {                                              
              mongos: 2,                                          
              shards: 2,                                          
              other: {                                            
                  rs: true,                                      
                  mongosOptions: { binVersion: "2.8"},       
                  configOptions: { binVersion: oldVersion},       
                  rsOptions: {binVersion: ["2.6"], nodes:3}
              }                                                                       
          };                                                      

      The test will fail on the line that reads:

      assert.writeError(coll.update( value, Object.merge( value, { i : [ 3 ] } ) ));

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: