mongos数据分布不均匀，move chunk失败

最新推荐文章于 2024-07-25 09:08:53 发布

原创最新推荐文章于 2024-07-25 09:08:53 发布 · 1.6k 阅读

1 ·

CC 4.0 BY-SA版权

DB故障处理案例同时被 2 个专栏收录

58 篇文章

订阅专栏

NoSQL/MongoDB

37 篇文章

订阅专栏

文章描述了在MongoDB集群中遇到数据分布不均匀的问题，以及在尝试通过moveChunk进行手动迁移时遇到的错误。错误信息显示由于之前的迁移仍有1236个删除操作未完成，导致moveChunk失败。故障原因被归结为可能的系统bug，并引用了相关Jira问题链接。解决方案是重启整个mongos集群，包括mongos节点、config节点和sharding节点。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

现象

2018-02-06T14:41:05.130+0800 I SHARDING [Balancer] moveChunk result: { cause: { ok: 0.0, errmsg: "can't accept new chunks because there are still 1236 deletes from previous migration" }, ok: 0.0, errmsg: "moveChunk failed to engage TO-shard in the data transfer: :: caused by :: UnknownError: can't accept new chunks because there are still 1236 deletes...", code: 8 }

mongos集群数据分布不均匀，后台日志显示move chunk失败，我尝试手工迁移，报错一样

mongos> sh.moveChunk("recruit.externalResumeStorage", {"rid" : "1836776472", "sourceId" : 6}, "udb-f4rrmx")

{
"cause" : {
"cause" : {
"ok" : 0,
"errmsg" : "can't accept new chunks because there are still 1236 deletes from previous migration"
},
"ok" : 0,
"errmsg" : "moveChunk failed to engage TO-shard in the data transfer: :: caused by :: UnknownError: can't accept new chunks because there are still 1236 deletes from previous migration",
"code" : 8
},
"code" : 8,
"ok" : 0,
"errmsg" : "move failed"
}