[
https://issues.apache.org/jira/browse/SLING-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586006#comment-16586006
]
Dirk Rudolph commented on SLING-7830:
-------------------------------------
The reason we had to report that was custom implementations of JobConsumer or
anything depending on that. In the scope of AEM that would be custom
implementations of TransportHandler, ReferenceProvider (anything related to
replication) or anything related to workflows etc. Those components might
impact the quality of service and so in a blue-green scenario the blue stack
should run the updated version for verification first before its getting rolled
out to a green stack.
> 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)
