JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-231  -  Assign a priority to the local executor and auto-discovered connections
Posted Mar 08, 2014 - updated Mar 08, 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
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1
Issue description
Currently, the JPPF client's local execution cannot be assigned a priority and always has a priority of 0. This means it cannot be easily used within a failover strategy using priorities of execution channels, unless the priorities of remote channels are set around 0.

We propose to add a configuration property to specify the priority of the local executor, for example "jppf.local.execution.priority".

We also propose to enable assigning a priority to all driver connections established via driver discovery. This makes sense since it is possible to mix discovered connections, manual connections and local executor.

#2
Comment posted by
 lolo4j
Mar 08, 12:44
Interesting. I just realized that the local executor priority is already implemented in the JPPF client code, but we never documented it.
#5
Comment posted by
 lolo4j
Mar 08, 22:04
implemented in trunk revision 3069