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 2015/08/25 17:18:46 UTC

[jira] [Commented] (UIMA-4570) If a log directory exists DUCC renames it and sweeps away the job spec

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

Lou DeGenaro commented on UIMA-4570:
------------------------------------

Removal is fine.  The original intent was to not mistakenly destroy potentially valuable information from previous runs.  Caveat emptor.

> If a log directory exists DUCC renames it and sweeps away the job spec
> ----------------------------------------------------------------------
>
>                 Key: UIMA-4570
>                 URL: https://issues.apache.org/jira/browse/UIMA-4570
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Priority: Minor
>             Fix For: future-DUCC
>
>
> The result is that ducc-mon cannot find the job specification.
> Since this renaming of the log directory is only useful in the unusual case of reinstalling DUCC without preserving the orchestrator sequence number, we should remove the logsweeper ... or somehow make it run before any other component opens the log directory.  Without it, if job numbers are reused, the log directory would have stale out-of-date log files ... easily avoided if the directory is removed before restarting DUCC.



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