MongoDB 学习 -- error以及解决方法
2012-10-11 10:49
344 查看
-- 在创建shardcollection的时候报错
mongos> db.runCommand({shardcollection:'test.test',key:{_id:1}})
{
"assertion" : "invalid parameter: expected an object ()",
"assertionCode" : 10065,
"errmsg" : "db assertion failure",
"ok" : 0
-- 原因:启动mongod的时候添加了replSet的选项导致找不到master
-- 解决:重新启动mongod,将replSet选项取消
-------------------------------------------------------------------------------------------------------------------------------------
-- 由于服务器时间不同步导致auto sharding失败
Fri Jan 6 12:46:09 [Balancer] caught exception while doing balance: error checking clock skew of cluster 10.192.9.110:20000,10.192.
136.242:20000,10.192.9.90:20000 :: caused by :: 13650 clock skew of the cluster 10.192.9.110:20000,10.192.136.242:20000,10.192.9.90:
20000 is too far out of bounds to allow distributed locking.
Fri Jan 6 13:14:24 [conn2] warning: - cmd: { splitChunk: "test1.test1", keyPattern: { _id: 1.0 }, min: { _id: Min
Key }, max: { _id: MaxKey }, from: "10.192.9.110:10000", splitKeys: [ { _id: 0.0 } ], shardId: "test1.test1-_id_MinKey", configdb: "
10.192.9.110:20000,10.192.136.242:20000,10.192.9.90:20000" } result: { errmsg: "Error locking distributed lock for split. :: caused
by :: 13651 error checking clock skew of cluster 10.192.9.110:20000,10.192.136.242:20000,10.192.9....", ok: 0.0 }
cp /usr/share/zoneinfo/GMT /etc/localtime
ntpdate 10.192.0.12 -- 时间服务器
---------------------------------------------------------------------------------------------------------------------
-- config服务一直无缘无故停止
Mon Jan 9 07:04:56 [Balancer] moveChunk result: { cause: { assertion: "Can't take a write lock while out of disk space", assertionCode: 14031, errmsg: "db assertion failure", ok: 0.0 }, errmsg: "moveChunk failed to engage TO-shard in the data transfer: db assertion failure", ok: 0.0 }
Mon Jan 9 07:04:56 [Balancer] balancer move failed: { cause: { assertion: "Can't take a write lock while out of disk space", assertionCode: 14031, errmsg: "db assertion failure", ok: 0.0 }, errmsg: "moveChunk failed to engage TO-shard in the data transfer: db assertion failure", ok: 0.0 } from: s2 to: s1 chunk: { _id: "test.test-_id_16690.0", lastmod: Timestamp 3000|1, ns: "test.test", min: { _id: 16690.0 }, max: { _id: 50791.0 }, shard: "s2" }
问题原因:10.192.9.90磁盘空间满
解决方案:增加磁盘空间
mongos> db.runCommand({shardcollection:'test.test',key:{_id:1}})
{
"assertion" : "invalid parameter: expected an object ()",
"assertionCode" : 10065,
"errmsg" : "db assertion failure",
"ok" : 0
-- 原因:启动mongod的时候添加了replSet的选项导致找不到master
-- 解决:重新启动mongod,将replSet选项取消
-------------------------------------------------------------------------------------------------------------------------------------
-- 由于服务器时间不同步导致auto sharding失败
Fri Jan 6 12:46:09 [Balancer] caught exception while doing balance: error checking clock skew of cluster 10.192.9.110:20000,10.192.
136.242:20000,10.192.9.90:20000 :: caused by :: 13650 clock skew of the cluster 10.192.9.110:20000,10.192.136.242:20000,10.192.9.90:
20000 is too far out of bounds to allow distributed locking.
Fri Jan 6 13:14:24 [conn2] warning: - cmd: { splitChunk: "test1.test1", keyPattern: { _id: 1.0 }, min: { _id: Min
Key }, max: { _id: MaxKey }, from: "10.192.9.110:10000", splitKeys: [ { _id: 0.0 } ], shardId: "test1.test1-_id_MinKey", configdb: "
10.192.9.110:20000,10.192.136.242:20000,10.192.9.90:20000" } result: { errmsg: "Error locking distributed lock for split. :: caused
by :: 13651 error checking clock skew of cluster 10.192.9.110:20000,10.192.136.242:20000,10.192.9....", ok: 0.0 }
cp /usr/share/zoneinfo/GMT /etc/localtime
ntpdate 10.192.0.12 -- 时间服务器
---------------------------------------------------------------------------------------------------------------------
-- config服务一直无缘无故停止
Mon Jan 9 07:04:56 [Balancer] moveChunk result: { cause: { assertion: "Can't take a write lock while out of disk space", assertionCode: 14031, errmsg: "db assertion failure", ok: 0.0 }, errmsg: "moveChunk failed to engage TO-shard in the data transfer: db assertion failure", ok: 0.0 }
Mon Jan 9 07:04:56 [Balancer] balancer move failed: { cause: { assertion: "Can't take a write lock while out of disk space", assertionCode: 14031, errmsg: "db assertion failure", ok: 0.0 }, errmsg: "moveChunk failed to engage TO-shard in the data transfer: db assertion failure", ok: 0.0 } from: s2 to: s1 chunk: { _id: "test.test-_id_16690.0", lastmod: Timestamp 3000|1, ns: "test.test", min: { _id: 16690.0 }, max: { _id: 50791.0 }, shard: "s2" }
问题原因:10.192.9.90磁盘空间满
解决方案:增加磁盘空间
相关文章推荐
- 大数据学习系列之八----- Hadoop、Spark、HBase、Hive搭建环境遇到的错误以及解决方法
- Android学习之 The connection to adb is down, and a severe error has occured. 解决方法
- Win开发当中遇到的各种error以及解决方法
- spring data mongodb学习以及为repository提供可扩展的自定义方法
- 如何在新浪后台绑定回调地址以及Oauth2 error:redirect_uri_mismatch的解决方法
- 【JAVA学习】总结classpath常见问题以及解决方法
- 学习Mysql遇到的问题以及解决方法
- 使用CString的方法(以及用VC写DLL中"error LNK2005: _DllMain@12 already defined"的解决办法)
- axis2的方法调用以及302 Error: Moved Temporarily的解决方法
- unserialize(): Error at offset出现的原因分析以及解决方法
- mongodb 对内存的严重占用以及解决方法
- allegro学习之导入netlist失败以及解决方法
- mongodb 对内存的严重占用以及解决方法
- Centos6 安装mysql5.6 以及ERROR 2002 ERROR 1045 解决方法
- TypeError: unhashable type: 'matrix'解决方法 以及 Python3下map函数的显示问题、 python numpy中nonzero()的用法
- unserialize(): Error at offset出现的原因分析以及解决方法
- 学习MongoDB 三: MongoDB无法启动的解决方法
- 学习中遇到的问题以及解决方法
- unserialize(): Error at offset 0 of 96 bytes出现的原因分析以及解决方法
- linux shell判断一个文件名判断它是目录还是文件以及在windows下出现"syntax error near unexpected token"的解决方法