You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/02/26 06:39:18 UTC
[jira] [Created] (SLING-5560) Delay job processing to avoid
unnecessary stale job handling
Chetan Mehrotra created SLING-5560:
--------------------------------------
Summary: Delay job processing 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
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)