JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-401  -  Ability to dynamically change the SLA and metadata of a job in the server
Posted Jul 01, 2015 - updated Oct 04, 2015
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
    Management / Monitoring
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.1
Issue description
This is inspired by this forum post. We propose to add the ability to update the server-side SLA of an already submitted job dynamically. This could be done via JMX, by adding a method updateJobSLA(String jobUuid, JobSLA newSLA) to the DriverJobManagementMBean interface. In fact, instead of (or in addition to) a single job uuid at a time, we could use a generalized job selector/filter like this:
public interface JobSelector extends Serializable {
  boolean accepts(String jobUuid, String jobName, JobSLA currentSLA, JobMetadata currentMetadata);
}
Then we can add a method like thisd to the mbean:
updateJobSLA(JobSelector selector, JobSLA newSLA)
While we're at it, we could do the same with the job metadata:
updateJobSLA(JobSelector selector, JobSLA newSLA, JobMetadata newMetadata)
A null value for the new sla or metadata would means it shouldn't be changed. This way, it's possible to update both of them atomically.


#3
Comment posted by
 lolo4j
Oct 04, 12:57
Implemented in trunk revision 3838