[SERVER-58719] drop collection / database hang on sharded cluster Created: 21/Jul/21 Updated: 14/Oct/21 Resolved: 14/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | adrien petel | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL | ||||||
| Steps To Reproduce: |
|
||||||
| Participants: |
| Description |
|
Since mongodb 5.0.0, on a sharded cluster with 3 config server, 2 shards and 1 mongos, dropping a collection or a database hang indefinitely without succeding On Ubuntu 20.04
|
| Comments |
| Comment by Edwin Zhou [ 14/Oct/21 ] | |||||
|
Thanks for following up felix2626, I'll go ahead and resolve this issue. Best, | |||||
| Comment by adrien petel [ 13/Oct/21 ] | |||||
|
Hi @Edwin Zhou,
using --replSet when creating shards fixed the issue, thanks for pointing it out
| |||||
| Comment by Edwin Zhou [ 11/Oct/21 ] | |||||
|
Hi felix2626, We still need additional information to diagnose the problem. If this is still an issue for you, would you please let us know if you are having issues creating a sharded clusters using a replica set? Best, | |||||
| Comment by Edwin Zhou [ 22/Sep/21 ] | |||||
|
Hi felix2626, Thanks for your report. In your deploy.sh script, it appears that you're attempting to create sharded nodes as standalone nodes, i.e., the command is missing the --replSet flag. Since MongoDB v3.6, shards must be deployed as a replica set.
Can you modify your script to use --replSet when creating shards and let us know if the error persists? For additional guidance on deploying a sharded cluster, please visit our documentation Best, | |||||
| Comment by Eric Sedor [ 28/Jul/21 ] | |||||
|
Thanks felix2626, we'll take a look. | |||||
| Comment by adrien petel [ 28/Jul/21 ] | |||||
|
Hi @eric.sedor,
I've uploaded the logs and diagnostic.data files | |||||
| Comment by adrien petel [ 23/Jul/21 ] | |||||
|
Hi Eric, Here are the steps I use to set up the cluster. This script was working for all previous version of MongoDB ( from 3.6 to 4.4 )
If that's not enough, I'll send the logs and diagnostic data when I get back to my working station
| |||||
| Comment by Eric Sedor [ 21/Jul/21 ] | |||||
|
Hi felix2626, I am not able to reproduce this from scratch so I suspect an issue with the cluster itself, possibly related to the chunk migration failures seen in sh.status() To investigate this as a possible bug, we'd like information from the following nodes in the cluster:
For each of these nodes, please archive (tar or zip) the mongod.log file covering a hanging collection drop attempt, and the $dbpath/diagnostic.data directory (the contents are described here) The specific time (with timezone) of the hanging attempt will also be helpful. I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Eric |