[
https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216197#comment-15216197
]
Stefan Egli commented on SLING-5560:
------------------------------------
added to trunk in http://svn.apache.org/viewvc?rev=1737012&view=rev
[~cziegeler], I had to fiddle with {{AbstractJobHandlingTest}} in order ot make
it apply a 1sec startup.delay (as the default of 30sec would otherwise fail the
ITs) - and for that I had to undo [your earlier
change|https://github.com/apache/sling/commit/6e0029d5fd43cc661a8430c249c6c89175de6d04#diff-1f2150de3a1dbf64ce76f318afc78565L324]
in the pom.xml and again use pax-exam-container-forked - pls double-check if
that's ok for you, thx.
> 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, SLING-5560.v2.patch,
> SLING-5560.v3.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)
