[DOCS-7069] Comment on: "manual/reference/command/replSetGetStatus.txt" Created: 02/Feb/16  Updated: 03/Nov/17  Resolved: 05/Oct/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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


Participants:
Days since reply: 7 years, 19 weeks, 1 day ago

 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?



 Comments   
Comment by Ravind Kumar (Inactive) [ 05/Oct/16 ]

Please refer to the MongoDB Google Group for support.

Depending on the outcome of the support case, there may be a clearer path for potential documentation improvements.

Generated at Thu Feb 08 07:53:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.