sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7830) Defined leader switch
Date Thu, 16 Aug 2018 08:31:00 GMT

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

Stefan Egli commented on SLING-7830:
------------------------------------

Assuming we're talking about discover.oak here?

Re scenario 1: I'm wondering if it would already possible today by manually changing the property
under {{/var/discovery/oak/clusterInstances/823d89a4-b625-4939-8457-39600a1a09c8/@leaderElectionId}}
- but as of now that's not a recommended way yet, so would have to first be tested/verified.
In any case, discovery API doesn't define a leader switch, so we'd have to discuss a new API
for this.

> 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