JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-569  -  New job SLA attributes
Posted Dec 23, 2018 - updated Yesterday (08:44)
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
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Core
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.1
Issue description
We propose to add the following attributes to the server-side SLA of a job:
  • whether to accept peer servers in a multi-driver topology (this is already available via the "jppf.peer.driver" boolean property available to an execution policy).
  • max driver depth: in a multi server topology, an upper bound for how many drivers a job can be transfered to before being executed on a node. Done
  • maximum dispatch size: the maximum number of tasks in a job that can be sent at once to a node (driver-side SLA) or to a driver (client-side SLA)
  • allow multiple dispatches to the same node (driver-side SLA) or driver (client-side SLA): a flag to specifiy whether a job can be dispatched to the same node or driver multiple times at any given moment. This is in anticipation of the completion of Feature request JPPF-564 - Asynchronous communication betwen node and driver