[
https://issues.apache.org/jira/browse/UIMA-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024466#comment-16024466
]
Lou DeGenaro commented on UIMA-5428:
------------------------------------
orchestrator:
JobFactory - build JP command line comprising -D's for creation of
DeploymentDescriptor (uima-as) or Aggregate (uima).
user:
Utils - remove method for obtaining process PID, which is no longer used
DeployableGenerator - do not include process PID in file name of deployable (DD
or Aggregate)
DuccAbstractProcessContainer - new method buildDeployable create DD or
Aggregate on behalf of JP
UimaAsProcessContainer - add call to build DD
UimaProcessContainer - add call to build Aggregate
container.dgen
README - note that although JD continues to build DD/Aggregate it is no longer
necessary since JP now does this. Removal of JD builder code is a future work
item.
> 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: Lou DeGenaro
> 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)
