[
https://issues.apache.org/jira/browse/SLING-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674443#comment-13674443
]
Stefan Egli edited comment on SLING-2901 at 6/4/13 2:34 PM:
------------------------------------------------------------
Implemented. Javadoc of discovery.api (DiscoveryService) adjusted.
The discovery.impl sends out a TOPOLOGY_CHANGING event before stopping its
bundle on detection of a duplicate sling.id in a cluster.
was (Author: egli):
The discovery.impl sends out a TOPOLOGY_CHANGING event before stopping its
bundle on detection of a duplicate sling.id in a cluster.
> Add robust paranoia check to detect duplicate sling.id in a cluster
> -------------------------------------------------------------------
>
> Key: SLING-2901
> URL: https://issues.apache.org/jira/browse/SLING-2901
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
>
> Follow-up of SLING-2892 which added a simple (but not robust) paranoia check
> for duplicate sling.id detection in a cluster.
> A robust check can be achieved ontop of SLING-2892 by additionally setting a
> 'runtimeId' property (which is a UUID assigned at activation of the
> HeartbeatHandler) right after activation/at first time, and checking for
> changes of that property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
