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

Need to ensure that we never update the ShardRegistry's config OpTime to a visible but uncommitted OpTime

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.2.0-rc1
    • None
    • Sharding
    • None
    • Minor Change
    • ALL
    • Repl B (10/30/15)

    Description

      There are at least two cases where we run a command against a config server without including a read concern (here and here.

      If we don't include the 'majority' read concern, then we'll automatically update our config server optime to the returned 'visible' level, which will not be committed since we didn't query against the committed snapshot.

      This could potentially cause future config server operations to hang waiting for the visible optime to become committed, if it never does.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: