[UIMA-5395] DUCC move_ducc flexibility

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.1-Ducc
• Component/s: DUCC
• Assignee: Lou DeGenaro
• Reporter: Lou DeGenaro
• Created: 08/Apr/17 15:39
• Updated: 17/Jun/19 15:28
• Resolved: 08/Apr/17 16:52

Description

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.

Issue Links

• relates to: UIMA-6058 Pear destroy does not destroy the resourceManagers