Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mongodb.org/manual/reference/command/replSetGetStatus/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/command/replSetGetStatus
*Location*: https://docs.mongodb.org/manual/reference/command/replSetGetStatus/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/command/replSetGetStatus
Description
This page doesn't explain why the configVersion constantly goes negative and the cluster starts losing data. This is a serious problem and telling us to just revert to backups doesn't help. Why bother adding replication if you're not going to bother to try to make it work?