You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/04/16 12:41:59 UTC
[jira] [Resolved] (SLING-4621) Manually forced leader change (in
otherwise unchanged clusterView) is not reported
[ https://issues.apache.org/jira/browse/SLING-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli resolved SLING-4621.
--------------------------------
Resolution: Fixed
Fixed in http://svn.apache.org/r1674038
> Manually forced leader change (in otherwise unchanged clusterView) is not reported
> ----------------------------------------------------------------------------------
>
> Key: SLING-4621
> URL: https://issues.apache.org/jira/browse/SLING-4621
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Impl 1.1.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Minor
> Fix For: Discovery Impl 1.1.2
>
>
> This is not a normal operation hence minor. But if the leader in an otherwise unchanged clusterView changes from one to the other, this is not reported as a TOPOLOGY_CHANGED. This can normally not happen, as the leader never changes within an unchanged clusterView (leader is stable by contract). But introducing the possibility of changing the leader (via SLING-4516) unveils this defect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)