[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/ |
||
| 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. |