JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-104  -  Inconsistent naming of the load-balancing properties
Posted Dec 16, 2012 - updated Dec 27, 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
    Enhancement
  • 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
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
Currently, the configuration of a load-balancing aklgorithm is similar to this: 
# Load-balancing algorithm: proportional, manual, nodethreads, rl, autotuned or user-defined custom algorithm
jppf.load.balancing.algorithm = <algorithm_name>
 
# name the set of algorithm parameters, aka "profile" 
jppf.load.balancing.strategy = <profile_name>
 
# profile / set of parameters
strategy.<profile_name>.<parameter_1> = <value_1>
...
strategy.<profile_name>.<parameter_N> = <value_N>
 I see a few issues with this:
  • the use of the term "strategy" is unintuitive and can lead to some confusion
  • all properties should start with the "jppf." prefix
  • additionally, the documentation and the configuration files of the driver distribution should be in sync
So instead, we should be able to write the load-balancer configuration like this: 
jppf.load.balancing.algorithm = <algorithm_name>
jppf.load.balancing.profile = <profile_name>
jppf.load.balancing.profile.<profile_name>.<parameter_1> = <value_1>
...
jppf.load.balancing.profile.<profile_name>.<parameter_N> = <value_N>


#4
Comment posted by
lolo4j
Feb 18, 00:34
This enhancement is now implemented. Changes committed to SVN trunk revision 2639

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.