# Time to move an elastic node is quiet long **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [June 21, 2017, 8:32am UTC](https://discuss.elastic.co/t/time-to-move-an-elastic-node-is-quiet-long/90225 "2017-06-21T08:32:31Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JohnnyB](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnnyb/32/13450_2.png) [@JohnnyB](https://discuss.elastic.co/u/JohnnyB)\ **Post date:** [June 21, 2017, 8:32am UTC](https://discuss.elastic.co/t/time-to-move-an-elastic-node-is-quiet-long/90225/1 "2017-06-21T08:32:32Z")
Hi ECE Team, Still testing ECE, I try to migrate a node from an allocator to another. My elastic node is empty (except monitoring datas) and was using 89 MB of 96GB before moving. The overall task took 3 minutes and 38 secondes (from 08:13:00 to 08:16:38). The longest task was : 2017-06-21T08:13:47.396Z Starting step: [migrate-data]: fromInstances=List(instance-0000000002) 2017-06-21T08:15:50.542Z Completed step: [migrate-data] with result: () This step took 2m 3s. My ECE run on 4 physical boxes. What are the expected time for such operation ? Is there any throttle that limit the migration of data ? How to adjust this ? Thanks for your feedback. Johnny ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [June 21, 2017, 1:03pm UTC](https://discuss.elastic.co/t/time-to-move-an-elastic-node-is-quiet-long/90225/2 "2017-06-21T13:03:24Z")
I normally count on a couple of minutes + data transfer times (max ~50MB/s but slower lots of small shards) + snapshot times if used (can take several minutes on larger clusters) So your times seem pretty standard (I just moved a 1GB node with a few days of monitoring on my slowish setup and the migrate step took 5m). You can use the `cat/recovery` endpoint to follow what's going on (and in fact the overview page of the UI displays that in graphical form) There's a few things going on: - The main thing is that moving nodes has a longish constant set up time regardless of size, but on typical clusters with 10s or 100s of GB (per shard) that time is not a dominating factor - The larger the cluster, the more CPU it has assigned to it, and the faster the migrations will occur. (You can manually turn the CPU metering on/off for a given cluster from the advanced cluster configuration, `resources.cpu.hard_limit` - that's often something we do to migrate data off small and overloaded clusters) - Also if you have HA clusters then migration is faster because the data is already available on another node (ie from the other replica). - Having physical machines with SSDs does make a decent difference I think - on our SaaS infrastructure, I'd expect the test migration I did to take ~1 minute or less. Alex ---
**Author:** ![JohnnyB](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnnyb/32/13450_2.png) [@JohnnyB](https://discuss.elastic.co/u/JohnnyB)\ **Post date:** [June 21, 2017, 2:55pm UTC](https://discuss.elastic.co/t/time-to-move-an-elastic-node-is-quiet-long/90225/3 "2017-06-21T14:55:33Z")
OK, Thanks for thoses explanations. I understood my test is not representative according to my cluster size... Which is a good news. Johnny ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 2:56pm UTC](https://discuss.elastic.co/t/time-to-move-an-elastic-node-is-quiet-long/90225/4 "2017-07-05T14:56:06Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.