sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7830) Defined leader switch
Date Mon, 20 Aug 2018 11:30:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585813#comment-16585813
] 

Carsten Ziegeler commented on SLING-7830:
-----------------------------------------

[~egli] Ok, thanks now I understand better where you saw the problems - yes, in my approach
a leaderElectionId is set correctly from the beginning - at startup of the instance - and
it will not change afterwords.
So when a leader change is required, the instances starting up will have a "higher" leaderElectionId
from the beginning. The leaderElectionId of the old instances will stay as is.


> 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
>            Priority: Major
>
> 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)

Mime
View raw message