Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-3600

"too stale to catch up" leaves state in RECOVERING

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 1.9.2
    • Component/s: Replication, Usability
    • Labels:
    • Replication

      If "too stale to catch up" means it will never catch up then I think this deserves a different state besides RECOVERING, which implies it will catch up eventually. Maybe the new state should be STALE indicating to the user that he will need to resync it.

            Assignee:
            backlog-server-repl Backlog - Replication Team
            Reporter:
            tonyh Tony Hannan
            Votes:
            7 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: