[SERVER-33924] parallel.js tries to move chunks to non-existent shards Created: 16/Mar/18  Updated: 29/Oct/23  Resolved: 19/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-03-26
Participants:
Linked BF Score: 22

 Description   

jstests/sharding/parallel.js creates 11 chunks for 10000 documents then attempts to distribute them across 3 shards by moving each to a random shard. It does so by manipulating strings, which map to the old naming convention for standalone shards. As of SERVER-32052, shards are replica sets, so these names don't match any shards, and each moveChunk fails (silently because the response is ignored).

This is probably related to the increasing number of NoProgessMade batch write failures in parallel.js, because the balancer is started before beginning a bulk insert and all 11 chunks are on one shard, leading to as many migrations as possible for this test setup.

The test should be updated to pick a random shard correctly, possibly by creating a new helper in ShardingTest.



 Comments   
Comment by Githook User [ 19/Mar/18 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-33924 Make parallel.js move chunks to existent shards
Branch: master
https://github.com/mongodb/mongo/commit/f7492502bfb24d1067e810ba9fd08e62f9a11c13

Comment by Esha Maharishi (Inactive) [ 16/Mar/18 ]

Ah, nice!

On Fri, Mar 16, 2018 at 10:49 AM Jack Mulrow (JIRA) <jira@mongodb.org>

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