Shulou(Shulou.com)06/01 Report--

Version: tokumx-1.5.0

mistake

"errmsg" : "loading local.system.replset config (LOADINGCONFIG)"

local.oplog.rs and local.system.repset tables exist,

Mistake 2

"errmsg" : "local.oplog.rs is not empty on the initiating member. cannot initiate. "

When rs.initiate(config) is performed, the oplog.rs table already exists

Mistake 3

"errmsg" : "all members and seeds must be reachable to initiate set"

The cluster information stored in local.oplog.rses is different from that to be initialized. Delete it.

Mistake 4

replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)

Table system.replset is empty

Mistake 5

No replica set primary available for query with ReadPreference PRIMARY

When a new node is added, the repset cluster information sensed by the frontend will change. When ReadPreference is not specified as Secondary, and secondary is unavailable when adding, primary will continue to wait for a new secondary node, resulting in this error. The status of the current secondary node is down

Mistake 6

"info" : "Config now saved locally. Should come online in about a minute. ",

The prompt indicates that it is saved normally, but it may not be saved normally. You can judge by checking Local.system.repset or log.

Mistake 7

"errmsg" : "took a long time to get write lock, so not initiating. Initiate when server less busy? "

There may be a large Oplog.rs table

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.