[SERVER-48406] Add onBecomeArbiter to ReplicaSetAwareService Created: 26/May/20  Updated: 29/Oct/23  Resolved: 28/May/20

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-47914 Move clusterTime from LogicalClock to... Closed
Related
related to SERVER-32639 Arbiters in standalone replica sets c... Closed
is related to SERVER-48610 ReplicaSetAwareService callbacks don'... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-06-01
Participants:

 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.



 Comments   
Comment by Githook User [ 28/May/20 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-48406 Add onBecomeArbiter to ReplicaSetAwareService
Branch: master
https://github.com/mongodb/mongo/commit/3caafb39293f862dd766ecf6388cfd78a72d8bc8

Generated at Thu Feb 08 05:17:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.