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

"too stale to catch up" leaves state in RECOVERING

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Won't Do
    • 1.9.2
    • None
    • Replication, Usability
    • Replication

    Description

      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.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. TOOLS-45 MongoStat does not indicate if replica is STALE

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-1933 "too stale to catch up" leaves state as 2

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: