You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2016/03/03 16:10:18 UTC

[jira] [Commented] (UIMA-4810) DUCC Job Driver (JD) C-Groups size not dynamic?

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

Lou DeGenaro commented on UIMA-4810:
------------------------------------

Presently Reservations are assigned a slot size at allocation time by the JD Scheduler, as specified in ducc.properties.

An improved design would allowed existing reservations to be carved up dynamically as opposed to being stuck at a particular slot size for the lifetime of the Reservation.

> DUCC Job Driver (JD) C-Groups size not dynamic?
> -----------------------------------------------
>
>                 Key: UIMA-4810
>                 URL: https://issues.apache.org/jira/browse/UIMA-4810
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: future-DUCC
>
>
> Updated JD quantum size in ducc.properties to be 800. The next job driver got a cgroup size of 
> 29 Feb 2016 21:50:53,953  INFO Agent.NodeAgent - J[N/A] T[2213] launchCommand  Launching Process - Commandline:/apps/ducc/ducc_runtime/duccling/bin/ducc_ling -u ducc -- /bin/cgset -r memory.limit_in_bytes=734003200 ducc/5752.5752.0 
> the same value as it was when DUCC started: 700 [MB].



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