You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2013/07/25 16:45:48 UTC
[jira] [Closed] (UIMA-2929) Move some of the local site checking in
to the global uima-ducc scripting.
[ https://issues.apache.org/jira/browse/UIMA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Challenger closed UIMA-2929.
--------------------------------
> Move some of the local site checking in to the global uima-ducc scripting.
> --------------------------------------------------------------------------
>
> Key: UIMA-2929
> URL: https://issues.apache.org/jira/browse/UIMA-2929
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 1.0-Ducc
>
>
> - all nodes' ducc_ling must match DUCC head's ducc_ling version
> - a node must have a working java. If the DUCC head does not nothing is started in ducc_start.
> - give a warning if the Orchestrator lock is found during startup
> - check for clock skew from the DUCC head and don't start a node that is not within acceptable bounds
> - on stop_ducc, if the broker is automanaged, stop_ducc needs to hang longer before returning to make sure things are shutdown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira