RS102 should automatically attempt repair

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.0.5
    • Component/s: Replication
    • None
    • Environment:
      Amazon Linux
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a replica falls back to RS102, is it safe to try to fix that automatically by resyncing the DB? Administrator intervention is in most cases a good thing, so I'm just testing the water. I'd imagine there's a worry about data corruption here that I'm overlooking.

      Perhaps this should be an option? (If I hit RS102, resync from scratch?) We missed a few backup replicas because we don't really monitor them, and it would have rocked had they fixed themselves.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Jed Smith
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: