[SERVER-27145] Shard name from a single node mongod not used as shard index in getSerializedCluster concurrency suite file cluster.js Created: 21/Nov/16  Updated: 05/Apr/17  Resolved: 21/Nov/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.4.0-rc4
Fix Version/s: 3.4.1, 3.5.1

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
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
Backport Completed:
Sprint: TIG 2016-12-12
Participants:

 Description   

The shard name, when using a standalone mongod, instead of a replica set is use an index into the shards in getSerializedCluster. The index used are 'shard0', 'shard1',... It should be based on the return from the invocation to ShardingTest as shard.shardName, i.e., 'shard0000'.



 Comments   
Comment by Githook User [ 07/Dec/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27145 Shard name from a single node mongod not used as shard index in getSerializedCluster concurrency suite file cluster.js

(cherry picked from commit 9bb919e988166f5e08aeb0f394842c8afe5ae03f)
Branch: v3.4
https://github.com/mongodb/mongo/commit/66edc250f46519ea7c6b65f628d201ffbfd0dfbf

Comment by Githook User [ 21/Nov/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-27145 Shard name from a single node mongod not used as shard index in getSerializedCluster concurrency suite file cluster.js
Branch: master
https://github.com/mongodb/mongo/commit/9bb919e988166f5e08aeb0f394842c8afe5ae03f

Generated at Thu Feb 08 04:14:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.