JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-137  -  Enabling a more flexible way of matching jobs to nodes
Posted Apr 17, 2013 - updated Dec 24, 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
    Not assigned to anyone
  • 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
From this forum thread.

Currently, the algorithm that determines node participation in the dispatching of a job to the nodes does not provide a way to test conditions on the grid's global attributes. For instance, it is not possible to state that a job with priority p cannot use more than x % of the nodes in the grid. This goes beyond the information that is available to an execution policy (no information on the grid state, no information on the job itself).

#2
Comment posted by
 lolo4j
Dec 24, 14:58
This feature is now realized by Feature request JPPF-210 - Add new execution policy executing an arbitrary script