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 2016/08/18 12:30:22 UTC
[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "hot" restart
issues
[ https://issues.apache.org/jira/browse/UIMA-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426355#comment-15426355 ]
Lou DeGenaro commented on UIMA-5060:
------------------------------------
Job Drivers (JDs) should not log "raw" exceptions when unable to communicate with the Orchestrator (OR). Instead, add to log: "Status reporting stopped. Condition may be temporary." and when condition is cleared (if ever) add to log: "Status reporting resumed.".
> DUCC Orchestrator (OR) "hot" restart issues
> -------------------------------------------
>
> Key: UIMA-5060
> URL: https://issues.apache.org/jira/browse/UIMA-5060
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 2.2.0-Ducc
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
>
> Address issues pertaining to the ability to shutdown and restart the OR component without loss of active jobs or services or AP's (aka Managed Reservations).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)