0
0条评论

我用命令sh.status（）发现报错如下，正常吗？怎么解决？
Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 2 deletes from previous migration’, from s3 to s2
1 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 3 deletes from previous migration’, from s1 to s2
3 : Failed with error ‘chunk too big to move’, from s3 to s2
15 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 1 deletes from previous migration’, from s3 to s2
1 : Failed with error ‘chunk too big to move’, from s1 to s3
4 : Failed with error ‘chunk too big to move’, from s2 to s1
2 : Failed with error ‘chunk too big to move’, from s2 to s3
1 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 1 deletes from previous migration’, from s3 to s1
2 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 1 deletes from previous migration’, from s1 to s2
3 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 1 deletes from previous migration’, from s2 to s1
88 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s2 to s3
16 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s3 to s1
211 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s1 to s2
17 : Failed with error ‘moveChunk failed to engage TO-shard in the data transfer: can’t accept new chunks because there are still 2 deletes from previous migration’, from s1 to s2
35 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s2 to s1
324 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s3 to s2
1 : Failed with error ‘migration already in progress’, from s1 to s3
2 : Failed with error ‘chunk too big to move’, from s1 to s2
1 : Failed with error ‘chunk too big to move’, from s3 to s1
44 : Failed with error ‘could not acquire collection lock for testdb.testCol500 to migrate chunk [{ : MinKey },{ : MaxKey }) :: caused by :: Lock for migrating chunk [{ : MinKey }, { : MaxKey }) in testdb.testCol500 is taken.’, from s1 to s3