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

wait for replication after duplicate key error from insert operations

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide

      This bug is not consistent in appearing (showed up in one of two evergreen builds), but this is the build that provoked it: https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_csrs_continuous_config_stepdown_WT_a1313488c04d5f532044506c78f728bd9f742e7d_16_01_12_22_01_34

      With the changes found in the build, run the following command:
      python buildscripts/resmoke.py --executor=sharding_continuous_config_stepdown --storageEngine=wiredTiger -j4 jstests/sharding/dump_coll_metadata.js

      Show
      This bug is not consistent in appearing (showed up in one of two evergreen builds), but this is the build that provoked it: https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_csrs_continuous_config_stepdown_WT_a1313488c04d5f532044506c78f728bd9f742e7d_16_01_12_22_01_34 With the changes found in the build, run the following command: python buildscripts/resmoke.py --executor=sharding_continuous_config_stepdown --storageEngine=wiredTiger -j4 jstests/sharding/dump_coll_metadata.js
    • Sharding F (01/29/16), Sharding 10 (02/19/16), Sharding 11 (03/11/16)
    • 0

      Caught this bug testing sharding_csrs_continuous_config_stepdown_WT suite with forced primary config server stepdown.

      Log: https://logkeeper.mongodb.org/build/56958221be07c46e4dc77637/test/569582219041300b2719d2b6#L5946

      Error message: 

      [js_test:dump_coll_metadata] 2016-01-12T22:46:19.709+0000 assert: command failed: {
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.709+0000 	"ok" : 0,
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 	"errmsg" : "Creating first chunks failed: DuplicateKey error :: caused by :: DuplicateKey: E11000 duplicate key error collection: config.chunks index: _id_ dup key: { : \"foo.bar-_id_MinKey\" } was returned after a retry attempt, but no documents were found. This means a concurrent change occurred together with the retries.",
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 	"code" : 11000
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 } : undefined
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 _getErrorWithCode@src/mongo/shell/utils.js:23:13
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 doassert@src/mongo/shell/assert.js:13:14
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.710+0000 assert.commandWorked@src/mongo/shell/assert.js:242:5
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.711+0000 @jstests/sharding/dump_coll_metadata.js:17:1
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.711+0000 @jstests/sharding/dump_coll_metadata.js:4:2
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.711+0000 
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.711+0000 2016-01-12T22:46:19.671+0000 E QUERY    [thread1] Error: command failed: {
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.711+0000 	"ok" : 0,
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.712+0000 	"errmsg" : "Creating first chunks failed: DuplicateKey error :: caused by :: DuplicateKey: E11000 duplicate key error collection: config.chunks index: _id_ dup key: { : \"foo.bar-_id_MinKey\" } was returned after a retry attempt, but no documents were found. This means a concurrent change occurred together with the retries.",
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.712+0000 	"code" : 11000
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.713+0000 } : undefined :
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.713+0000 _getErrorWithCode@src/mongo/shell/utils.js:23:13
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.713+0000 doassert@src/mongo/shell/assert.js:13:14
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.714+0000 assert.commandWorked@src/mongo/shell/assert.js:242:5
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.714+0000 @jstests/sharding/dump_coll_metadata.js:17:1
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.714+0000 @jstests/sharding/dump_coll_metadata.js:4:2
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.714+0000 
[js_test:dump_coll_metadata] 2016-01-12T22:46:19.714+0000 failed to load: jstests/sharding/dump_coll_metadata.js

      This does not appear to be caused by rollback (nothing in the logs about rollback).

      Error comes from CatalogManagerReplicaSet::insertConfigDocument

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: