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/10/14 19:18:20 UTC

[jira] [Commented] (UIMA-5060) DUCC Orchestrator (OR) "warm" restart issues

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

Lou DeGenaro commented on UIMA-5060:
------------------------------------

- Fix leak of JD entries in OR's map of processId-to-jobId.  
- Make ProcessToJobMap its own class and insure code that employs same does not use stale copy.
- Code refactoring for simplification and clarity in ProcessAccounting.

> DUCC Orchestrator (OR) "warm" 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
>             Fix For: 2.2.0-Ducc
>
>
> 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)