[SERVER-18974] dropCollection fails because setShardVersion request is incorrect Created: 15/Jun/15  Updated: 05/Feb/16  Resolved: 15/Jun/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.4
Fix Version/s: 3.1.5

Type: Bug Priority: Major - P3
Reporter: Daniel Alabi Assignee: Daniel Alabi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 5 06/26/16
Participants:

 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] }



 Comments   
Comment by Githook User [ 15/Jun/15 ]

Author:

{u'username': u'alabid', u'name': u'Daniel Alabi', u'email': u'alabidan@gmail.com'}

Message: SERVER-18974 ConfigCoordinator SetShardVersion request should use correct connection string
Branch: master
https://github.com/mongodb/mongo/commit/68e6858e66219ba8e98b5c7832742a1f8ec0247d

Generated at Thu Feb 08 03:49:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.