[
https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-5560:
-------------------------------
Attachment: SLING-5560.patch
Attached [^SLING-5560.patch] as a suggested implementation of the 'simple by 1
config' approach. It introduces a separate, easy-to-backport (since separate)
class InitDelayingTopologyEventListener that simply does delaying of topology
events, without any other side-effects (intended).
The idea would then be to probably 'donate' that to discovery.commons (in
trunk, but not for the backport)
/cc [~cziegeler], [~chetanm], wdyt? (I yet have to write a separate test class
for the new delaying listener)
> Delay job processing at startup to avoid unnecessary stale job handling
> -----------------------------------------------------------------------
>
> Key: SLING-5560
> URL: https://issues.apache.org/jira/browse/SLING-5560
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Chetan Mehrotra
> Assignee: Stefan Egli
> Fix For: Event 4.1.0
>
> Attachments: SLING-5560.patch
>
>
> While running in a cluster (or in some case non cluster setup also) Topology
> would become stable after "some" time. For e.g. in a 2 node setup by the time
> first node comes up second node might not have started so topology would not
> detect it and first node might think that second node is not there and it can
> then start assigning job for that node to current node under stable job
> processing.
> Instead of doing this just right at startup job processing should start after
> "some" delay such that topology becomes stable. This would avoid this
> unnecessary work and probably even reduce load on the master
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
