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:57:02 UTC
[jira] [Assigned] (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:all-tabpanel ]
Lou DeGenaro reassigned UIMA-3857:
----------------------------------
Assignee: Jim Challenger (was: Lou DeGenaro)
Consider having DUCC scripting (start_ducc & start_sim) erase state/orchestrator.json when cold or warm starting the OR.
> 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: Jim Challenger
> 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)