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)