# Moving nodes not working as expected **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [August 2, 2017, 3:42am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441 "2017-08-02T03:42:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [August 2, 2017, 3:42am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/1 "2017-08-02T03:42:25Z")
Hi ECE: I want to move a cluster from some high allocated nodes to some not allocated nodes ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/d/2d496b53cdb51ce74bd14d46c7a246417cdb1c95.png)Screen Shot 2017-08-02 at 11.38.25 AM In this case want to move from [10.0.2.191] -\> [10.0.1.119]. So I click move nodes-\> advanced-\> set target allocator ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/3/738152836e5a5005baa43c0bee720b3c7e442a54.png)Screen Shot 2017-08-02 at 11.39.00 AM Then the cluster just allocate back to its own which is not expected. ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/b/8bbdc4bc3e0628f0be12e367fc4f3cf0aa42dfcb.png)Screen Shot 2017-08-02 at 11.38.08 AM Any idea of this? ---
**Author:** ![Patroklos\_Papapetrou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patroklos_papapetrou/32/20715_2.png) [@Patroklos\_Papapetrou](https://discuss.elastic.co/u/Patroklos_Papapetrou)\ **Post date:** [August 2, 2017, 6:16am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/2 "2017-08-02T06:16:44Z")
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 ---
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [August 2, 2017, 7:31am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/3 "2017-08-02T07:31:41Z")
Hi Patroklos: When I enable the maintenance mode in 10.0.2.191. And do the same thing as I show, then I got the error when moving nodes. ``` #6 Aug 2, 2017, 7:27:27 AM GMT (3 minutes ago, by root) Show details Cluster operations Move nodes from allocator 10.0.2.191 Unexpected error during step: [allocate-instances]: [no.found.constructor.steps.allocation.AllocationFailedException: Allocation failed: [NotEnoughCapacity(0,3,Map(zone-0 -> 66560))]] ``` ---
**Author:** ![Patroklos\_Papapetrou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patroklos_papapetrou/32/20715_2.png) [@Patroklos\_Papapetrou](https://discuss.elastic.co/u/Patroklos_Papapetrou)\ **Post date:** [August 2, 2017, 7:43am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/4 "2017-08-02T07:43:46Z")
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? ---
**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\ **Post date:** [August 2, 2017, 7:57am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/5 "2017-08-02T07:57:10Z")
Hi 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? ---
**Author:** ![Patroklos\_Papapetrou](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patroklos_papapetrou/32/20715_2.png) [@Patroklos\_Papapetrou](https://discuss.elastic.co/u/Patroklos_Papapetrou)\ **Post date:** [August 2, 2017, 8:00am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/6 "2017-08-02T08:00:10Z")
You can still move nodes inside the same AZ 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 16, 2017, 8:00am UTC](https://discuss.elastic.co/t/moving-nodes-not-working-as-expected/95441/7 "2017-08-16T08:00:26Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.