JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
OPEN  Feature request JPPF-562  -  Fix the preference execution policy
Posted Nov 27, 2018 - updated Nov 27, 2018
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Issue details
  • Type of issue
    Feature request
  • Status
     
    New
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Server
  • Resolution
    Not determined
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.1
Issue description
Currently the Preference execution poliy is applied to each node individually and is identical to the OR execution policy. To sum up: despite its name, it has nothing to do with a "preference".

We propose to make it live up to its name, which implies:

  • it should define a real order of preference for a number of node execution policies, where a node that satisfies policy N in the list will have priority over a node that satisfies policy N + 1
  • it should be applied globally to all the nodes available to the driver
  • because of the previous point, it should be a separate attribute of the job SLA
  • it should be applicable to the client-side as well, where it would define a driver preference rather than a node preference
  • special care should be taken about perfomance, as the algorithm will be in O(nbNodes * nbJobs). Should we allow parallel (with regards to the nodes) evaluation of the policy for each job?



There are no comments