not master and slaveOk=false
2017-05-04 14:53
561 查看
在SECONDARY查询出发现如下错误:
这是正常的,因为SECONDARY是不允许读写的,如果非要解决,方法如下:
sns:SECONDARY> show collections 2017-05-04T14:48:57.162+0800 E QUERY [thread1] Error: listCollections failed: { "ok" : 0, "errmsg" : "not master and slaveOk=false", "code" : 13435 } :
这是正常的,因为SECONDARY是不允许读写的,如果非要解决,方法如下:
sns:SECONDARY> rs.slaveOk(); sns:SECONDARY> show collections system.users system.version
相关文章推荐
- NOT MASTER AND SLAVEOK=FALSE
- MongoDb的“not master and slaveok=false”错误及解决方法
- MongoDb的“not master and slaveok=false”错误及解决方法
- 【MongoDB】MongoDb的“not master and slaveok=false”错误及解决方法
- MongoDb的“not master and slaveok=false”错误及解决方法
- MongoDb的“not master and slaveok=false”错误及解决方法
- MongoDb的“not master and slaveok=false”错误及解决方法
- mongoDB Error:not master and slaveOk=false
- MongoDb的“not master and slaveok=false”错误及解决方法
- uncaught exception: error: { "$err" : "not master and slaveOk=false", "code" : 13435 }
- MongoDB的“not master and slaveok=false”错误解决
- MongoDb的"not master and slaveok=false"错误及解决方法
- MongoDb的“not master and slaveok=false”错误及解决方法,读写分离
- MongoCursorException ***not master and slaveOk=false
- "$err" : "not master and slaveok=false", "code" : 13435
- Table definition on master and slave does not match(坑爹的编码)
- Table definition on master and slave does not match
- Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs
- master and slave have equal MySQL server UUIDs 解决方法
- 异常com.mongodb.MongoException: not talking to master and retries used up 处理办法