You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/04/16 12:39:58 UTC

[jira] [Created] (SLING-4628) [discovery] Add a JMX method to start a new voting

Stefan Egli created SLING-4628:
----------------------------------

             Summary: [discovery] Add a JMX method to start a new voting
                 Key: SLING-4628
                 URL: https://issues.apache.org/jira/browse/SLING-4628
             Project: Sling
          Issue Type: Improvement
          Components: Extensions
    Affects Versions: Discovery Impl 1.1.0
            Reporter: Stefan Egli
            Assignee: Stefan Egli
            Priority: Minor
             Fix For: Discovery Impl 1.1.2


With SLING-4516 an additional way of controlling the instance ordering in a cluster and thus who will become is leader (which is defined via alphabetical ordering of the {{leaderElectionId}}) is introduced. 

When the {{leaderElectionId}} changes, this does not automatically trigger a new vote however, since it conflicts with the discovery API which demands that the leader be *stable*.

In order to still support use cases where a leader *knowingly and explicitly* wants to be changed (by an admin), a JMX method for starting a new voting should be introduced. This would simply cause a new {{ongoingVotings}} to be created based on the existing set of instances. It would not fiddle with the way the leader is chosen in any way. All it would do is, based on the {{leaderElectionIds}} it would elect a (potentially new) leader.

This would support management possibilities around forcing a different or specific leader to some extend.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)