JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-193  -  Timeout of bundles dispatched to the nodes
Posted Oct 04, 2013 - updated Oct 11, 2013
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0
Issue description
This is about the ability to expire task sets dispatched to the nodes, based on a schedule specified in the job SLA. This would be an intermediate between the whole job expiration and the timeout of individual tasks that already exist. The schedule would be specified as an additional SLA attribute "dispatchExpirationSchedule".

The developers should be able to determine the action to take upon timeout: either resubmit the tasks or cancel them. This could be specified via an SLA attribute "maxDispatchResubmits": the server would keep track of the number of times a task expired, and when it reaches the maxResubmit threshold the task is cancelled, otherwise it is resubmitted. This should allow us to avoid having tasks rebmitted in an infinite loop.

The whole processing of dispatch tiemout only requires changes in the server and job SLA.

#2
Comment posted by
 lolo4j
Oct 11, 06:37
This feature is now implemented. Doc has been updated and new unit tests added. Changes committed to SVN trunk revision 2901

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.