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] [Updated] (SLING-7830) Defined leader switch
Date Fri, 27 Sep 2019 09:44:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Egli updated SLING-7830:
-------------------------------
    Description: 
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 [~stefanegli]

  was:
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]


> Defined leader switch
> ---------------------
>
>                 Key: SLING-7830
>                 URL: https://issues.apache.org/jira/browse/SLING-7830
>             Project: Sling
>          Issue Type: Improvement
>          Components: Discovery
>    Affects Versions: Discovery Oak 1.2.22
>            Reporter: Carsten Ziegeler
>            Assignee: Stefan Egli
>            Priority: Major
>             Fix For: Discovery Oak 1.2.28
>
>          Time Spent: 20m
>  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 [~stefanegli]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message