Moving nodes not working as expected


I want to move a cluster from some high allocated nodes to some not allocated nodes

Screen Shot 2017-08-02 at 11.38.25 AM

In this case want to move from [] -> [].
So I click move nodes-> advanced-> set target allocator

Screen Shot 2017-08-02 at 11.39.00 AM

Then the cluster just allocate back to its own which is not expected.

Screen Shot 2017-08-02 at 11.38.08 AM

Any idea of this?

Hi @weibin.wu
This is strange. I assume that the low-allocated nodes are not in maintenance mode, right?
Can you please try this as a workaround?

  1. Enable Maintenance mode of the high-allocated node
  2. Move the nodes as you did before
  3. Disable Maintenance mode of the node we used in step 1

Thank you

Hi Patroklos:

When I enable the maintenance mode in
And do the same thing as I show, then I got the error when moving nodes.

Aug 2, 2017, 7:27:27 AM GMT (3 minutes ago, by root)
Show details
Cluster operations
Move nodes from allocator
Unexpected error during step: [allocate-instances]:                 
[no.found.constructor.steps.allocation.AllocationFailedException: Allocation failed: 
[NotEnoughCapacity(0,3,Map(zone-0 -> 66560))]]

Hi @weibin.wu
Can you please share here the configuration of your cluster?
In particular, I want to check how many availability zones (AZ) are you using. I guess you are using 2 availability zones (b-1 and b-2) the third zone (a-1) is used for the tie breaker. If this is the case then the behavior you are experiencing in both cases is expected.

During the first attempt, since tiebreaker is hosted on a-1 then our algorithm does not allow ES data to be moved to the same AZ with the tiebreaker.
During the second attempt, we have disabled completely the b-1 zone and since a-1 cannot be used (for the same reason as explained above) the algorithm tries to use the only available/allowed zone which is b-1 and it fails because it can't be used.

Does it make sense?

AZ zone 1: a-1
AZ zone 2: b-1
AZ zone 3: b-2

So in this case, we are not able to move to any node because we only have 3 AZ zone only. Is it?

You can still move nodes inside the same AZ :slight_smile:

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.