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 2017/11/04 11:08:00 UTC
[jira] [Comment Edited] (UIMA-5599) DUCC JD node allocation and
watching improvements
[ https://issues.apache.org/jira/browse/UIMA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238915#comment-16238915 ]
Lou DeGenaro edited comment on UIMA-5599 at 11/4/17 11:07 AM:
--------------------------------------------------------------
JdScheduler should announce in OR's log at INFO level whenever it acquires or divests reservations for JD shares.
Change set delivered.
was (Author: lou.degenaro):
JdScheduler should announce in OR's log at INFO level whenever it acquires or divests reservations for JD shares.
> DUCC JD node allocation and watching improvements
> -------------------------------------------------
>
> Key: UIMA-5599
> URL: https://issues.apache.org/jira/browse/UIMA-5599
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> 1. Services only DUCC, meaning no JD allocation
> 2. DUCC Watcher warning
> a) No JD allocation
> b) Insufficient JD allocation
> 3. Give example of cron job for DUCC Watcher in doc
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)