[SERVER-35009] Sharded cluster with small chunk size set makes bulk insert jobs fail to return Created: 16/May/18 Updated: 10/Jun/18 Resolved: 18/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Royce Brown | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Create & init config server as a single relica set
Init replica set
Start mongos
Start two shard servers
Set chunksize
Init sharding
We now have a running mongo sharded cluster
Now if we run this script it will never return or maybe take a very long time, have waited 1 hour before killing it. In file load_shard.js
Run script
Script never returns. If you make another connection to mongos and do a sh.status() it looks like data has been written. |
|||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
There is a problem running Mongo 3.6.* in a test sharded clustered, where the chunk size is set small as in 1 or 2M. The problem can be created with the simplest of set up one config & mongos server and two shard servers. It problem still exits though, have tried doing this on version 3.6.0. & 3.6.4 but same results |
| Comments |
| Comment by Ramon Fernandez Marina [ 18/May/18 ] | |||||
|
Thanks for the feedback royce55, and glad to hear the workaround is working for you. I'm going to mark this ticket as a duplicate of SERVER-31837 – please feel free to watch that ticket for updates. Regards, | |||||
| Comment by Mary Gorman [ 18/May/18 ] | |||||
|
LOST message in JIRA
I added the --setParameter orphanCleanupDelaySecs=0 to the shard server startup command line. Thank you for that answer, I searched the internet but there didn't seem to be any record of any one having this problem. Anyway thanks very much, it fixes the problem. Regards | |||||
| Comment by Ramon Fernandez Marina [ 17/May/18 ] | |||||
|
royce55, a colleague points out that this looks like SERVER-31837, and adding --setParameter orphanCleanupDelaySecs=0 to all your shards should help. I tried it and your load script completes in about 10s – can you please try it on your end and report back? Regards, |