Some of the trouble notes that MongoDB operation encounters

Version: tokumx-1.5.0

Error One

"ErrMsg": "Loading local.system.replset config (loadingconfig)"

There are local.oplog.rs and Local.system.repset tables,

Error two

"ErrMsg": "Local.oplog.rs is not empty on the initiating member. Cannot initiate. "

Oplog.rs table already exists when Rs.initiate (config) is in progress

Error three

"ErrMsg": "All members and seeds must is reachable to initiate set"

The cluster information stored in the local.oplog.rses is different from what is to be initialized, and can be deleted

Error Four

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

Table System.replset is empty

Error Five

No replica set primary available for query with Readpreference Primary

When adding a new node, the front-end-aware repset cluster information changes, and when Readpreference is not specified as secondary, and secondary is not available when it is added, the primary continues to wait for the new secondary node. resulting in this error, the current secodnary node status is down

Error Six

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

The prompt is saved normally, but it may not be saved properly and can be judged by looking at Local.system.repset or log

Error Seven

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

There may be a larger oplog.rs table

Some of the trouble notes that MongoDB operation encounters