-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 5.0.0
-
Component/s: None
-
None
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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
[direct: mongos] admin> sh.status()
shardingVersion
{
_id: 1,
minCompatibleVersion: 5,
currentVersion: 6,
clusterId: ObjectId("60f7e17702142e807fc3033d")
}
---
shards
[
{
_id: 'shard0000',
host: 'localhost:27021',
state: 1,
topologyTime: Timestamp(2, 1626857864)
},
{
_id: 'shard0001',
host: 'localhost:27022',
state: 1,
topologyTime: Timestamp(2, 1626857876)
}
]
---
active mongoses
[ { '5.0.0': 1 } ]
---
autosplit
{ 'Currently enabled': 'yes' }
---
balancer
{
'Currently running': 'no',
'Currently enabled': 'yes',
'Failed balancer rounds in last 5 attempts': 0,
'Migration Results for the last 24 hours': { '342': "Failed with error 'aborted', from shard0000 to shard0001" }
}
---
databases
[
{
database: { _id: 'config', primary: 'config', partitioned: true },
collections: {
'config.system.sessions': {
shardKey: { _id: 1 },
unique: false,
balancing: true,
chunkMetadata: [ { shard: 'shard0000', nChunks: 1024 } ],
chunks: [
'too many chunks to print, use verbose if you want to force print'
],
tags: []
}
}
}
]