[SERVER-26285] ShardCollection on existing collection can sometimes fail to create more than 1 chunk Created: 23/Sep/16  Updated: 25/Jan/17  Resolved: 04/Oct/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done 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 2016-10-10
Participants:
Linked BF Score: 0

 Description   

It looks like there are some cases when splitVector is not called on the shard and shardCollection ends up just creating a single chunk for a huge collection.



 Comments   
Comment by Githook User [ 04/Oct/16 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-26285 Code cleanup for ShardingUptimeReporter
Branch: master
https://github.com/mongodb/mongo/commit/7e40ab701a38fcca2711e1f9ffb6b7ce403a351b

Comment by Githook User [ 04/Oct/16 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-26285 Make sure that the balancer settings gets refreshed periodically
Branch: master
https://github.com/mongodb/mongo/commit/d8b4ac75423456efd6401264e6d9c6b95d9b21e6

Comment by Randolph Tan [ 29/Sep/16 ]

Looks like the balancer configuration is currently only refreshed during startup and when the autosplit threshold is triggered. It means that there is a potential race between changing the setting in the config server document and the mongos reading the setting with the latest changes immediately after.

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