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

Add onBecomeArbiter to ReplicaSetAwareService

    XMLWordPrintable

Details

    • Fully Compatible
    • Sharding 2020-06-01

    Description

      ReplicaSetAwareServices (added in SERVER-46201) currently have the ability to react to a node becoming primary (both step up, and exiting drain mode), and becoming secondary. This allows such services to tailor their behaviour according to the node's current primary/secondary status, and to react accordingly to these events. It would be similarly useful if they could react to a node becoming an Arbiter, since this is not a startup/config file option, but rather happens when the node activates a replica set configuration in which it is arbiterOnly: true.

      Attachments

        Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-47914 Move clusterTime from LogicalClock to VectorClock

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-48610 ReplicaSetAwareService callbacks don't occur in ReplicationCoordinatorImpl tests

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32639 Arbiters in standalone replica sets can't sign or validate clusterTime with auth on once FCV checks are removed

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

          Activity

            People

              kevin.pulo@mongodb.com Kevin Pulo
              kevin.pulo@mongodb.com Kevin Pulo
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: