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

Remove CoordinateCommitReturnsNoneIfCoordinatorWasRemoved unit test

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1, 4.2.7
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • v4.2
    • Sharding 2019-09-09
    • 0

      The unit test is no longer valid after SERVER-42772, because now the coordinator is removed from the catalog asynchronously.

      However, we could add some more test coverage:

      • That a coordinator is removed from the catalog on completion. From a quick search, I only foundĀ one unit test of this, and it is for when the coordinator is canceled. We could add coverage for the coordinator completing successfully or with an error.
      • That calling TransactionCoordinatorService::coordinateCommit for a lsid and txnNumber whose coordinator has completed either returns boost::none (because the coordinator has already been removed) or a ready future (the coordinator has yet to be removed).

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: