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 2014/06/06 11:55:01 UTC
[jira] [Commented] (UIMA-3857) DUCC Orchestrator (OR) should should
checkpoint and restore publication sequence number.
[ https://issues.apache.org/jira/browse/UIMA-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019718#comment-14019718 ]
Lou DeGenaro commented on UIMA-3857:
------------------------------------
Code delivered.
OR now keeps a file state/orchestrator.json comprising sequence numbers for State and AbbreviatedState publications.
This file can be erased when doing cold or warm starts, but should be kept when doing hot (re-)start or Orchestrator.
> DUCC Orchestrator (OR) should should checkpoint and restore publication sequence number.
> ----------------------------------------------------------------------------------------
>
> Key: UIMA-3857
> URL: https://issues.apache.org/jira/browse/UIMA-3857
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: 1.1.0-Ducc
>
>
> If only OR reboots while Agents and perhaps other daemons remain running, the OR publication sequence number is reset to zero. As a result, the receivers of these OR publications may reject them as being out-of-sequence.
--
This message was sent by Atlassian JIRA
(v6.2#6252)