# Expected upgrade times?

**URL:** <https://discuss.elastic.co/t/expected-upgrade-times/39148>\
**Category:** Elasticsearch\
**Created:** [January 13, 2016, 6:44pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148 "2016-01-13T18:44:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jzheaux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jzheaux/32/7138_2.png) [@jzheaux](https://discuss.elastic.co/u/jzheaux)\
**Post date:** [January 13, 2016, 6:44pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148/1 "2016-01-13T18:44:07Z")

</div>

We are currently upgrading from ES 1.6 to 2.1.

ES is taking about 2 minutes per gigabyte of index data, according to the log timestamps.

I've turned off cluster.routing.allocation.enable and done a /\_flush/synced as instructed in the upgrade docs on each node in the cluster.

This seems too slow; what should I be investigating to explain the slowness?

---

<div class="post-metadata">

**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:** [January 13, 2016, 9:24pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148/2 "2016-01-13T21:24:10Z")

</div>

It depends, how much data do you have, what sort of disk, what node resources?

---

<div class="post-metadata">

**Author:** ![jzheaux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jzheaux/32/7138_2.png) [@jzheaux](https://discuss.elastic.co/u/jzheaux)\
**Post date:** [January 14, 2016, 6:22pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148/3 "2016-01-14T18:22:22Z")

</div>

For each node, its about 250GB of index data and 3G memory.

The disk is a RAID using SATA drives, though I'm not as familiar with that part of the stack.

---

<div class="post-metadata">

**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:** [January 14, 2016, 9:42pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148/4 "2016-01-14T21:42:04Z")

</div>

That's not a lot of resources, but maybe increasing some of [these allocation settings](https://www.elastic.co/guide/en/elasticsearch/reference/2.1/shards-allocation.html#_shard_allocation_settings) will help - `cluster.routing.allocation.node_concurrent_recoveries` and `indices.recovery.concurrent_streams`.

---

<div class="post-metadata">

**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:24pm UTC](https://discuss.elastic.co/t/expected-upgrade-times/39148/5 "2017-07-05T23:24:20Z")

</div>