[
https://issues.apache.org/jira/browse/SLING-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586118#comment-16586118
]
Stefan Egli commented on SLING-7830:
------------------------------------
bq. With the above discussed implementation, the deployer of the new instances
has full control whether a leader switch should happen or not. If the same
prefix is provided, the old leader stays the leader.
sure, just trying to understand better and set expectations. I'll go ahead with
the PR in a couple days giving time for a potential review
> Defined leader switch
> ---------------------
>
> Key: SLING-7830
> URL: https://issues.apache.org/jira/browse/SLING-7830
> Project: Sling
> Issue Type: Improvement
> Components: Discovery
> Reporter: Carsten Ziegeler
> Assignee: Stefan Egli
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The current leader selection is based on startup time and sling id (mainly)
> and is stable across changed in the topology for as long as the leader is up
> and running.
> However there are use cases like blue green deployment where new instances
> with a new version are started and taking over the functionality. However
> with the current discovery setup, the leader would still be one of the
> instances with the old version.
> With a new deployed version, tasks currently bound to the leader should run
> on the new version.
> Therefore the leader needs to switch and stay the leader (until it dies).
> We probably need an additional criteria for the leader selection
> /cc [~egli]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
