-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
Fully Compatible
-
Sharding 2020-06-01
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is depended on by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-32639 Arbiters in standalone replica sets can't sign or validate clusterTime with auth on once FCV checks are removed
-
- Closed
-