oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OODT-12) Allow configurable number of threads to monitor batch stubs
Date Fri, 03 Dec 2010 05:56:10 GMT

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

Chris A. Mattmann updated OODT-12:
----------------------------------

    Description: 
Make CAS-Resource have only a single thread (or possibly a configurable number of threads)
monitor batch stubs, verse currently one server proxy thread per job:

    *  this causes server errors when too many threads for a single process is reached - therefore,
limiting the number of running jobs in the resource manager to the number of threads a singles
java process can create


  was:

    *  this causes server errors when too many threads for a single process is reached - therefore,
limiting the number of running jobs in the resource manager to the number of threads a singles
java process can create


        Summary: Allow configurable number of threads to monitor batch stubs  (was: Make CAS-Resource
have only a single thread (or possibly a configurable number of threads) monitor batch stubs,
verse currently one server proxy thread per job)

- clean up

> Allow configurable number of threads to monitor batch stubs
> -----------------------------------------------------------
>
>                 Key: OODT-12
>                 URL: https://issues.apache.org/jira/browse/OODT-12
>             Project: OODT
>          Issue Type: Improvement
>          Components: resource manager
>    Affects Versions: 0.1-incubating
>            Reporter: Brian Foster
>            Priority: Minor
>             Fix For: 0.2
>
>
> Make CAS-Resource have only a single thread (or possibly a configurable number of threads)
monitor batch stubs, verse currently one server proxy thread per job:
>     *  this causes server errors when too many threads for a single process is reached
- therefore, limiting the number of running jobs in the resource manager to the number of
threads a singles java process can create

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message