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

TransactionCoordinator doesn't update replica set monitors based on participant responses

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2019-03-25, Sharding 2019-04-08, Sharding 2019-04-22

      Description

      To drive a two phase commit, TransactionCoordinators target shards using the replica set monitors in the ShardRegistry. The TransactionCoordinator does not update these replica set monitors with the response from the targeted host, so if the error is retryable and indicates the targeted host is no longer a primary, e.g. a stepdown error, the TransactionCoordinator will re-target the same node until the corresponding replica set monitor refreshes for some other reason. Instead, the TransactionCoordinator should update the appropriate RSM for each response it receives, like in ShardRemote::_runCommand.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: