uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Burn Lewis (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-4275) DUCC RM: Rework constraints on class usage
Date Fri, 20 Mar 2015 14:32:52 GMT

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

Burn Lewis updated UIMA-4275:
    Component/s: DUCC

> DUCC RM: Rework constraints on class usage
> ------------------------------------------
>                 Key: UIMA-4275
>                 URL: https://issues.apache.org/jira/browse/UIMA-4275
>             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
> The current class constraints are per-allocation and not sufficiently constraining in
that a user can dominate a cluster with many requests for non-preemptable shares.
> There are proposals for user-based limits (max allocations per user), group-based limits
(group membership determines limits), and project-based limits (submission to authorized projects
determines limits).
> The final decision is still open.  This JIRA will track progress and eventually, the
> 2015-03-06
> Consulting with actual users, the preference is for user-based as it is simplest to understand
and administer.  The current plan is to implement a "max GB per user by class" scheme where,
if the class so designates, the maximum allocation per user for a class is configured. GB
is to be the unit of allotment, as the unit "share" is variable by installation choice/need,
and "process" is variable by hardware in a heterogeneous environment.  A user registry will
allow overrides for designated users.  As well an class-inclusion mechanism is to be implemented
which, if configured, will restrict use of classes to specific users.  If no limits or inclusion
is configured for a class, all users will be permitted unrestricted access to the resources
governed by the class.

This message was sent by Atlassian JIRA

View raw message