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

ReplicaSetAwareService test should just use dummy services

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-08-24
    • Linked BF Score:
      0

      Description

      The ReplicaSetAwareService test is mistakenly ending up calling the VectorClockMongoD onStepUpComplete.

      So far the test has always worked because such method call always resulted in a NOP, but that will not be the case anymore with the changes that are going to be introduced in SERVER-49193.

        Attachments

          Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-49193 Recover the VectorClock on shard primary step up

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-46201 Implement a generic ReplicaSetStateAwareService

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              kevin.pulo Kevin Pulo
              Reporter:
              pierlauro.sciarelli Pierlauro Sciarelli
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: