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

dropCollection fails because setShardVersion request is incorrect

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.1.4
    • Fix Version/s: 3.1.5
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 5 06/26/16

      Description

      FSM test failure:

      [js_test:fsm_all_sharded_replication] 2015-06-12T21:23:15.394+0000 E QUERY    [main] Error: drop failed: {
      [js_test:fsm_all_sharded_replication] 	"code" : 8071,
      [js_test:fsm_all_sharded_replication] 	"ok" : 0,
      [js_test:fsm_all_sharded_replication] 	"errmsg" : "cleaning up after drop failed: { configdb: { stored: \"WIN-U39SQJVDKF0:29000\", given: \"test-configRS/WIN-U39SQJVDKF0:29000\" }, $gleStats: { lastOpTime: Timestamp 0|0, electionId: ObjectId('557b4adcc213958b09c18d23') }, ok: 0.0, errmsg: \"mongos specified a different config database string : stored : WIN-U39SQJVDKF0:29000 vs given : test-configRS/WIN-U39SQJVDKF0:29000\", code: 125 }"
      [js_test:fsm_all_sharded_replication] }
      

        Attachments

          Activity

            People

            Assignee:
            daniel.alabi@10gen.com Daniel Alabi
            Reporter:
            daniel.alabi@10gen.com Daniel Alabi
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: