Stefan Egli created SLING-3390:
----------------------------------
Summary: [discovery] silence discovery.impl when in single-node
case
Key: SLING-3390
URL: https://issues.apache.org/jira/browse/SLING-3390
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Discovery Impl 1.0.2
Reporter: Stefan Egli
As proposed on the list at [0] we have two optimizations (actual one, the
second one includes the first one) as described in SLING-3389 that are rather
straight forward.
There is a third optimization which would silence the discovery.impl entirely,
if it realizes that it is in fact alone.
The referred details extracted from [0] are:
"What could be done for level 3:
a) at startup the behavior is as is today, cluster-ready, writing
repository-heartbeats as configured
b) this is done for a configured amount of time at least, eg for 5
minutes (exploring phase) - the idea of this being to avoid any
race-conditions of two nodes starting simultaneously
c) if after this time, the node realizes, that it is alone (and no-one
joined or left during this time), it assumes that it is indeed in a
standalone setup and stops sending heartbeats (solitude phase)
d) if another node starts up in the same cluster, it would as normal
start doing these heartbeats for a few minutes (exploring phase) - giving
the original node time to wake up to the idea that it was never alone
(alien phase) - at which point it quickly starts to go back to sending
heartbeats and voting and all those things (party phase)
phase d) is obviously slightly tricky ..
"
This is considered a nice-to-have at the moment, but here's the ticket for
reference to reconsider later.
[0] http://markmail.org/thread/2ev5sy3b3mr5klc5
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
