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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.11
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • 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

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: