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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0-rc1
    • Component/s: Sharding
    • Labels:
      None

      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

            Assignee:
            milkie Eric Milkie
            Reporter:
            spencer Spencer Brody
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: