[jira] [Closed] (SLING-4765) Add debugging info to duplicate sling.id detection in discovery.impl

["Stefan Egli (JIRA)" <ji...@apache.org>]

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

Stefan Egli closed SLING-4765.
------------------------------

> Add debugging info to duplicate sling.id detection in discovery.impl
> --------------------------------------------------------------------
>
>                 Key: SLING-4765
>                 URL: https://issues.apache.org/jira/browse/SLING-4765
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.1.2
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Impl 1.1.4
>
>
> In case of SLING-2901 or SLING-2892 it sometimes is not exactly clear if indeed a second instance was hooked to the same repository or whether there is something else causing the detection to report a false positive.
> To clarify this, add more debugging infos to the log output when these two situations occur, which should include:
>  * log runtimeId at activate time
>  * besides runtimeId, add pid/ip/port information which can then be logged in case a duplicate situation is detected (to simply proof which other 'ghost' instance was causing the duplicate situation)
>  * when the duplicate situation is detected, print all available information: local runtimeId/lastHeartbeat/pid/ip/port plus the same for what is stored under /var/discovery/impl/clusterInstances/<slingId>
> Basically provide enough infos to proof the ghost duplicate instance (or help detecting that the issue is locally if it is)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)