[SERVER-23316] Sharding tests should not rely on the order of entries returned when querying the config.shards collection Created: 23/Mar/16  Updated: 19/Jul/18  Resolved: 13/Jun/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.0.15, 3.3.9

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-27599 Sharding tests should not rely on the... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding 16 (06/24/16)
Participants:
Linked BF Score: 0

 Description   

Sharding continuous stepdown tests fail occasionally because they query the config.shards collection and assume that the entries will be returned in sorted order, but that is not strictly guaranteed in the case where replication might have applied the insertions concurrently and in different order.



 Comments   
Comment by Githook User [ 05/Jan/17 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-23316 Use shards from ShardingTest instead of querying config.shards for balance_repl.js
Branch: v3.0
https://github.com/mongodb/mongo/commit/f888e8dcce90f70d052099aecff82e62964ae3fe

Comment by Githook User [ 17/Jun/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-23316 Use shards from ShardingTest instead of querying config.shards
for balance_repl.js and move_stale_mongos.js
Branch: master
https://github.com/mongodb/mongo/commit/90195f8f0359fd11d92cca06ad2a3891aa0e354b

Comment by Githook User [ 13/Jun/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-23316 Use shards from ShardingTest instead of querying config.shards for validate_collection.js and stale_mongos_updates_and_removes.js
Branch: master
https://github.com/mongodb/mongo/commit/fd77e162bd656f245e4735385a8077472142c08b

Comment by Dianna Hohensee (Inactive) [ 24/Mar/16 ]

BF-1916 failed because there's only one chunk on one shard after shardCollection, not one on each, so moving the same chunk to both shards is bound to get "that chunk is already on that shard" error. But this issue can totally happen, too

Comment by Githook User [ 23/Mar/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-23316 Use shards from ShardingTest instead of querying config.shards
Branch: master
https://github.com/mongodb/mongo/commit/cd0865b2ce06ae22ca73d78f26248d8374cb6598

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