[jira] [Commented] (UIMA-5395) DUCC move_ducc flexibility

["Lou DeGenaro (JIRA)" <de...@uima.apache.org>]

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

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

bash-4.1$ ./move_ducc --help
Usage: move_ducc [options]

Options:
  -h, --help     show this help message and exit
  -d, --debug    display debugging messages
  -o, --offline  indicate current DUCC head node is offline, Note: USE THIS
                 OPTION WITH EXTREME CAUTION else risk corrupting database
  -q, --quiet    do not display informational messages

Run this command on the host which will become the new DUCC head node.

Prerequisites:
1. the current ducc.head node in site.ducc.properties is up
2. the head daemons (broker, database, or, pm, rm, sm, ws) on the ducc.head node are down (e.g. stop_ducc -c head)

Operation:
To the extent possible, the cluster will be checked to see if it is safe to edit the site.ducc.properties file, and if so then a backup of the original file is made then the requisite changes are made to realize the head node move. Likewise, the appropriate ducc.nodes file is backed-up and updated as necessary.


> 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)