# Shard movement speed **URL:** \ **Category:** Elasticsearch\ **Created:** [September 15, 2015, 4:04am UTC](https://discuss.elastic.co/t/shard-movement-speed/29294 "2015-09-15T04:04:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![bsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bsarkar/32/42967_2.png) [@bsarkar](https://discuss.elastic.co/u/bsarkar)\ **Post date:** [September 15, 2015, 4:04am UTC](https://discuss.elastic.co/t/shard-movement-speed/29294/1 "2015-09-15T04:04:18Z")
I have an Elasticsearch cluster with three data nodes. For some experiment, I want to move all the shards to a single data node. So I used the [shard allocation filter](https://www.elastic.co/guide/en/elasticsearch/reference/1.6/index-modules-allocation.html#shard-allocation-filtering) feature to achieve that. From Marvel, I see that that Network Transport Bytes Sent speed is around 16MBps each from the two source data nodes and 32MBps on the target data node. I want to know if there is an Elasticsearch configuration to increase the speed to moving shards across data nodes. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 15, 2015, 5:03am UTC](https://discuss.elastic.co/t/shard-movement-speed/29294/2 "2015-09-15T05:03:39Z")
This can be managed via settings described here [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html) Specifically you could increase `cluster.routing.allocation.cluster_concurrent_rebalance`. ---
**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, 11:50pm UTC](https://discuss.elastic.co/t/shard-movement-speed/29294/3 "2017-07-05T23:50:21Z")