Critical replication failures should bring server into RECOVERING state

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.2
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The dreaded "replSet error RS102 too stale to catch up" in my opinion should mark server as RECOVERING or failed in any other way, because currently there is no any other way to determine if replication occured. Silent failures on the other hand lead to potential loss of data in emergency cases.

            Assignee:
            Kristina Chodorow (Inactive)
            Reporter:
            Aristarkh Zagorodnikov
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: