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

How is 2-phase commit done to update config servers?

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • # Replies:
      5
    • Last comment by Customer:
      true
    • Actual Time:
      8
    • Sprint:
      Docs Current Sprint (487)

      Description

      The manual claims that 2-phase commit is used for changes to config servers. A property that 2-phase commit provides is that changes are not visible on any of the servers until all servers have agreed to commit. From reading source in src/mongo/s and src/mongo/s/catalog I don't see how that is provided.

      Assuming I am correct, can the manual be updated to explain the behavior that is provided?

      What I do see is this pattern for updates which runs in two phases but isn't 2-phase commit:
      1) ping all config servers to confirm they are running
      2) send write to all config servers
      3) collect responses from writes. If all fail, then report that (which is OK). If all succeed then report OK. Else report inconsistent write because write was done to some but not all config servers.

      Two questions:
      1) Is there code to cleanup from inconsistent write? Cleanup code won't avoid the race from inconsistent reads, but will shrink the window.

      2) What is done to avoid inconsistent read after inconsistent write? If this were 2-phase commit then inconsistent read (read after inconsistent write) wouldn't be possible.

      Code I read to understand this includes:

      • CatalogManagerLegacy::writeConfigServerDirect
      • ConfigCoordinator::executeBatch
      • SSVRequest::combineResponses
      • DBClientMultiCommand::sendAll

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 24 weeks, 5 days ago
                Date of 1st Reply: