Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-1030

Need to complete the thought re. failed secondaries

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      http://docs.mongodb.org/manual/administration/sharding-architectures/#sharding-high-availability

      Here's the sentence in question:

      "If the unavailable mongod is a secondary, and it connects within its recovery window."

      My understanding is as follows:

      Within a given shard, if the unavailable mongod is a secondary then reads/writes directed to that shard’s primary will continue without interruption. When that secondary’s operations resume, it must reconnect within it’s recovery window in order to catch up on any writes it may have missed. The recovery window is determined by the size of the oplog. Many users configure an oplog sufficient to maintain a recovery window of multiple days.

      Also, there's mention of "recovery window" that links to oplog sizing. It isn't obvious that the two are related, and the term "recovery window" doesn't appear on the oplog sizing page.

      Attachments

        Activity

          People

            sam.kleinman Sam Kleinman (Inactive)
            kelly.stirman Kelly Stirman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              11 years, 4 weeks, 1 day ago