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 2018/11/28 12:47:00 UTC

[jira] [Assigned] (UIMA-5912) DUCC Agent must employ ducc_ling to create job's log directory

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

Lou DeGenaro reassigned UIMA-5912:
----------------------------------

    Assignee: Jerry Cwiklik  (was: Lou DeGenaro)

> DUCC Agent must employ ducc_ling to create job's log directory
> --------------------------------------------------------------
>
>                 Key: UIMA-5912
>                 URL: https://issues.apache.org/jira/browse/UIMA-5912
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.2.3-Ducc
>
>
> Presently DUCC Orchestrator (OR) creates log directory and sub-directories as <user> (with ducc_ling) according to job specification key "log_directory".  For the non-shared filesystem case, the Agent will start the JP process and the expected log directory will likely not exist on other than the DUCC head node.  As a result, the JP dies.
> To remedy, the Agent should use the same logic that OR does to create the log directory tree for the JP.  If it does not already in its publications, OR must provide Agent with JP log directory; perhaps as a new method getLogDirectory() on the already provided CommandLine object.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)