[
https://issues.apache.org/jira/browse/UIMA-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Challenger resolved UIMA-4256.
----------------------------------
Resolution: Won't Fix
On more discussion we realized that we could use cgroups to limit CPU usage so
jobs don't become "hostile." No need to modify RM.
> DUCC: RM allow "hostile" jobs that don't share resources with others
> --------------------------------------------------------------------
>
> Key: UIMA-4256
> URL: https://issues.apache.org/jira/browse/UIMA-4256
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Affects Versions: 1.1.0-Ducc
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 2.0.0-Ducc
>
>
> Certain types of jobs will consume every processor on a host regardless of
> the memory assignment. This update allows the declaration of a "hostile"
> flag in a FAIR_SHARE class definition that instructs the RM not to schedule
> other work on any processor with a job submitted to a hostile class. If this
> is done, the full share count of each host is accounted under the user's
> fair-share allocation regardless of the memory declaration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
