[jira] [Resolved] (OODT-244) Allow the Resource Manager scheduler to cycle on a non-integer number of seconds

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OODT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-244.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.11)
                   0.10

Thanks Gabe!

{noformat}
[guest-wireless-207-151-035-079:~/tmp/oodt0.10] mattmann% svn commit -m "Fix for OODT-244: Allow the Resource Manager scheduler to cycle on a non-integer number of seconds contributed by Gabe Resneck."
Sending        CHANGES.txt
Sending        resource/src/main/java/org/apache/oodt/cas/resource/scheduler/LRUScheduler.java
Transmitting file data ..
Committed revision 1700090.
[guest-wireless-207-151-035-079:~/tmp/oodt0.10] mattmann% 
{noformat}


> Allow the Resource Manager scheduler to cycle on a non-integer number of seconds
> --------------------------------------------------------------------------------
>
>                 Key: OODT-244
>                 URL: https://issues.apache.org/jira/browse/OODT-244
>             Project: OODT
>          Issue Type: Improvement
>          Components: resource manager
>            Reporter: Gabe Resneck
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>             Fix For: 0.10
>
>         Attachments: OODT-244_resneck_05-04-11_patch.txt
>
>
> The Scheduler component of the Resource Manager has a given amount of time that it sleep after scheduling (or attempting to, if the queue is empty) a job. Currently, that period of time is a number of seconds is an integer. If users wish to have their instance of the RM run as quickly as possible, they have to set that period to either 1 (which can cause a bottleneck if lots of job come in at once) or 0 (which may cause the system to run into errors). In order to allow for greater granularity, the user should be able to use floats or doubles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)