-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.21
-
Component/s: None
-
ALL
MongoDB3.6.21版本分片不均,查看日志,有较多以下日志:
2024-10-29T00:04:37.648+0800 W SHARDING [conn60529] Chunk move failed :: caused by :: ConflictingOperationInProgress: Unable to start new migration because this shard is currently receiving chunk [{ obuId: "210230", Time: new Date(1729289141000) }, { obuId: "210256", Time: new Date(1729311613000) }) for namespace test.test_20241019 from shard2
怀疑是SERVER-29423 Sharding balancer schedules multiple migrations with the same conflicting source or destination - MongoDB Jira这个BUG,但是版本对不上,对应时间点config没有报错:
2024-10-29T00:04:30.999+0800 I COMMAND [conn11095402] command config.chunks command: count { count: "chunks", query:
{ jumbo: true }, $readPreference: { mode: "secondaryPreferred" }, $db: "config" } planSummary: COLLSCAN keysExamined:0 docsExamined:2168192 numYields:16939 reslen:229 locks:{ Global: { acquireCount:
{ r: 33880 }}, Database: { acquireCount:
{ r: 16940 }}, Collection: { acquireCount:
{ r: 16940 }} } protocol:op_query 998ms 2024-10-29T00:04:31.217+0800 I NETWORK [conn11127303] end connection 10.88.245.6:46776 (40 connections now open) 2024-10-29T00:04:43.618+0800 I ACCESS [conn673910] Successfully authenticated as principal root on admin from client 10.88.245.9:37374 2024-10-29T00:04:45.007+0800 I ACCESS [conn11095402] Successfully authenticated as principal root on admin from client 10.88.245.5:42944
- backported by
-
SERVER-29423 Sharding balancer schedules multiple migrations with the same conflicting source or destination
- Closed