uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-5395) DUCC move_ducc flexibility
Date Sat, 08 Apr 2017 16:31:41 GMT

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

Lou DeGenaro commented on UIMA-5395:
------------------------------------

bash-4.1$ ./move_ducc
2017-04-08 12:12:33  INFO node=bigdog348 checking ducc head node daemons status
2017-04-08 12:12:38  INFO node=bigdog348 ducc head node daemons are down
2017-04-08 12:12:39  INFO node=bigdog348 nodepool=ducchead
2017-04-08 12:12:39  INFO node=bigdog167 nodepool=--default--
2017-04-08 12:12:39  INFO creating backup file=site.ducc.properties.2017-04-08@12:12:33
2017-04-08 12:12:39  INFO site.ducc.properties updates=3
2017-04-08 12:12:41  INFO creating backup file=ducc.head.nodes.2017-04-08@12:12:33
2017-04-08 12:12:41  INFO updating ducc.head.nodes
2017-04-08 12:12:41  INFO bigdog348 -> bigdog167
2017-04-08 12:12:41  INFO move completed

> DUCC move_ducc flexibility
> --------------------------
>
>                 Key: UIMA-5395
>                 URL: https://issues.apache.org/jira/browse/UIMA-5395
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.2.1-Ducc
>
>
> Presently, concerning move_ducc and node pools: the current head node "A" and target
head node "B" must both be in the same node pool or both not be in any node pool.
> Improvement: additionally allow for "A" to be in a node pool and "B" to not be in a node
pool.  In this case, move_ducc should remove "A" and add "B".
> It will still be disallowed for "A" and "B" to be in different node pools.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message