[
https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197594#comment-15197594
]
Carsten Ziegeler commented on SLING-5560:
-----------------------------------------
JobManagerConfiguration.backgroundLoadDelay was used earlier on for the delay.
The whole impl waited that time before doing anything
With introducing the topology, this somehow got mixed up, parts like the
CheckTopologyTask go early, others later. Not sure why it ended up this way.
I think the "simply by single config" approach sounds easy and understandable,
so I would go with that
> 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
>
>
> 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)
