You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2017/06/02 20:39:04 UTC

[jira] [Closed] (UIMA-5428) DUCC minimally support user log directory not in shared file system

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

Burn Lewis closed UIMA-5428.
----------------------------
    Resolution: Fixed

Dropped DD build in UimaAsProcessContainer as is done when parsing descriptor for the scale out value.  Also dropped DD build in JD ... should drop JD aggregate build too?  Handle descriptor overrides in JP's aggregate build.

> DUCC minimally support user log directory not in shared file system
> -------------------------------------------------------------------
>
>                 Key: UIMA-5428
>                 URL: https://issues.apache.org/jira/browse/UIMA-5428
>             Project: UIMA
>          Issue Type: New Feature
>            Reporter: Lou DeGenaro
>            Assignee: Burn Lewis
>             Fix For: 2.2.1
>
>
> Support submitted work where user specified log directory is not in shared file system.
> For example, if user specifies /tmp/foobar as the log directory for a submitted job, the job will run and the /tmp on each system where the JD and JPs run will contain written files, such as JD and JP logs files.  But no ducc-mon support.  ducc-mon will only be able to see the /tmp of its local file system. Any files located in /tmp on remote machines (e.g. machines other than the DUCC head node) will not be visible via ducc-mon.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)