JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-233  -  Ability for a task to schedule itself for resubmission
Posted Mar 15, 2014 - updated Mar 19, 2014
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
  • Estimated time
    Not estimated
  • Category
    Core
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1
Issue description
This is about enabling tasks to mark themselves as candidates for resubmission during their execution on a node, for example when an error occured and was caught by the task.

The server already has the ability to resubmit individual tasks, in particular using the job sla's dispatch expiration settings. We need to provide an API in the tasks to set a "resubmit" flag, and have the node send that information in the job header, then have the server check for this flag.

If possible, the new API should not break the existing Task/AbstractTask API, so maybe it could be in a specialized subclass or interface, like "Resubmitable".

#2
Comment posted by
 lolo4j
Mar 18, 22:41
Finally I went for adding setResubmit(boolean) and isResubmit() to AbstractTask. What remains to do is add a way to specify the maximum number of resubmits, to avoid jobs being stuck because tasks are resubmitted in an infinite loop. This will most likely be an attribute of the job SLA, like setMaxTaskResubmits(int)
#3
Comment posted by
 lolo4j
Mar 19, 00:53
implemented in trunk revision 3080