Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to solve the "not master and slaveok=false" error in MongoDb. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

A "not master and slaveok=false" error occurs when using mongodb because secondary does not allow reading and writing.

Because the mongodb acts as the master / slave in the system, the master / slave switches, which may also lead to this problem.

The query is normal after replacing the ip in the command mongo-- username=root-- password=123456-- host=192.168.0.100 admin with the main ip.

Description of the problem:

First of all, this is normal, because SECONDARY does not allow reading and writing, and in applications that write more and read less, Replica Sets is used to achieve read-write separation. By specifying the slaveOk at connection time or in the main library, the Secondary shares the read pressure, and the Primary only takes on the write operation.

Unreadable by default for secondary nodes in replica set

Set up slaveok=ok on the main library

This is the end of the article on how to solve the "not master and slaveok=false" error in MongoDb. I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.