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

Investigate causal consistency violation when getting errors from config server

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sprint:
      Sharding 2018-04-09

      Description

      Here's a breakdown of what occurred in the build failure where this appears to manifest:

      1. Shard sends _configsvrCommitChunkSplit to config server.
      2. Config server finish executing the command.
      3. Config server steps down from primary and closes all incoming connections.
      4. Shard gets back a network error and retries.
      5. Shard sends the commit command and get a preCondition failure because it has already been successfully applied earlier.
      6. Shard tries to inspect the state by refreshing the chunk state (by querying) but gets back the state before the commit.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: