[jira] [Issue Comment Edited] (OODT-335) Allow for some Resource Manager operations to act on groups of jobs based upon Metadata key-value pairs

["Brian Foster (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127249#comment-13127249 ] 

Brian Foster edited comment on OODT-335 at 10/14/11 2:28 AM:
-------------------------------------------------------------

I think you are looking to add too many features into the resource manager... the resource manager is meant to be dumb... this feature could be added into the workflow manager... the workflow manager (both trunk and wengine versions) understands metadata already and keeps track of the resource manager jobId for every Task they submit... the resource manager already supports delete by JobId -- i.e. XmlRpcResourceManager's: public boolean killJob(String jobId) throws MonitorException... this issue should be attached to the workflow manager and then discuss in that context... the resource manager should only know how to find a node for a job, run the job, and stop the job... everything else belongs in the workflow manager or another wrapper component.
                
      was (Author: bfoster):
    I think you are looking to add too many features into the resource manager... the resource manager is meant to be dumb... this feature could be added into the workflow manager... the workflow manager (both trunk and wengine versions) understands metadata already and keeps track of the resource manager jobId for every Task they submit... the resource manager already supports delete by JobId -- i.e. XmlRpcResourceManager's: public boolean killJob(String jobId) throws MonitorException... this issue should be added to the workflow manager and then discuss in that context... the resource manager should only know how to find a node for a job, run the job, and stop the job... everything else belongs in the workflow manager or another wrapper component.
                  
> Allow for some Resource Manager operations to act on groups of jobs based upon Metadata key-value pairs
> -------------------------------------------------------------------------------------------------------
>
>                 Key: OODT-335
>                 URL: https://issues.apache.org/jira/browse/OODT-335
>             Project: OODT
>          Issue Type: Improvement
>          Components: resource manager
>            Reporter: Gabe Resneck
>            Assignee: Gabe Resneck
>
> While performing operations (such as prioritizing a job or flagging it to not be scheduled) upon specific jobs is well and good, it is not a very powerful tool.  Many times, operators want to perform these functions on groups of jobs, specifically, groups that share a key-value pair of metadata.  For example, this would allow an operator to move all jobs with the value "10/18" for the metadata key "date".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira