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 2017/09/01 13:41:00 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=16150540#comment-16150540 ] 

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

For JD's DUCC should:

1. inspect each job's --driver_jvm_args for -Xmx value.
2. if -Xmx is not specified, then use the value specified for jd.share.quantum in ducc.properties.
3. dynamically allocate a JD share of the correct size.
4. dynamically assign cgroup size in correspondence with the allocated JD share.



> 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.4.14#64029)