# Upgrading ES 2.x to 5.x - Questions about elasticsearch-migration output **URL:** \ **Category:** Elasticsearch\ **Created:** [November 21, 2016, 1:47pm UTC](https://discuss.elastic.co/t/upgrading-es-2-x-to-5-x-questions-about-elasticsearch-migration-output/66726 "2016-11-21T13:47:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Roland\_L](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Roland\_L](https://discuss.elastic.co/u/Roland_L)\ **Post date:** [November 21, 2016, 1:47pm UTC](https://discuss.elastic.co/t/upgrading-es-2-x-to-5-x-questions-about-elasticsearch-migration-output/66726/1 "2016-11-21T13:47:02Z")
Hi, I'm preparing our migration from ES 2.4.1 to 5.0 and I have a few questions about the results the elasticsearch-migration plugin has given me: - **_node.datacenter\_location_ should be rewritten as _node.attr.datacenter\_location_** : we have been using _node.datacenter\_location_ in _cluster.routing.allocation.awareness.attributes: datacenter\_location_: so if the first one will be changed what do I change the second one to? - **_foreground_ will be moved to the archived namespace on upgrade** : what is this parameter? We don't have it in out elasticsearch.yml and I've never seen it before. - **_indices.recovery.concurrent\_streams_ will be moved to the archived namespace on upgrade** : is there an alternative to this property? It's documented up until 2.x, but it's missing in the 5.0 documentation ([https://www.elastic.co/guide/en/elasticsearch/reference/5.0/recovery.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/recovery.html)). We have 10 nodes (5 per DC) and if the default is still 3 streams it's very low. It would be great if we could raise the number of concurrent streams, our hardware can handle more streams. Thanks, Roland ---
**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\ **Post date:** [November 22, 2016, 10:09am UTC](https://discuss.elastic.co/t/upgrading-es-2-x-to-5-x-questions-about-elasticsearch-migration-output/66726/2 "2016-11-22T10:09:33Z")
Hi Roland, > [@Roland\_L](#): > > node.datacenter\_location should be rewritten as node.attr.datacenter\_location: we have been using node.datacenter\_location in cluster.routing.allocation.awareness.attributes: datacenter\_location: so if the first one will be changed what do I change the second one to? In 5.0 node attributes must have the prefix `node.attr.` so you need to change `node.datacenter_location` to `node.attr.datacenter_location`in the configuration file. But `node.datacenter_location in cluster.routing.allocation.awareness.attributes: datacenter_location` indicates the name of the node attribute to use for shard allocation. In your case it is unchanged. See [Shard Allocation Awareness | Elasticsearch Guide [5.0] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/allocation-awareness.html#allocation-awareness) as an example on 5.0. > [@Roland\_L](#): > > foreground will be moved to the archived namespace on upgrade: what is this parameter? We don't have it in out elasticsearch.yml and I've never seen it before. This means that the migration plugin has found a parameter `foreground` that is unknown and will be moved under the `archived.` namespace in cluster settings after the node starts up. This parameter is unknown to me so I think it's a leftover in your configuration. From Elasticsearch 5.0 on all settings are validated before they are applied. > [@Roland\_L](#): > > indices.recovery.concurrent\_streams will be moved to the archived namespace on upgrade: This settings has been completely removed, it does not exist anymore. Recoveries are now controlled (and throttled) on each node using an allocation decider. You might want to tune the settings as documented in [Cluster Level Shard Allocation | Elasticsearch Guide [5.0] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/shards-allocation.html#_shard_allocation_settings). ---
**Author:** ![Roland\_L](https://avatars.discourse-cdn.com/v4/letter/r/958977/32.png) [@Roland\_L](https://discuss.elastic.co/u/Roland_L)\ **Post date:** [November 22, 2016, 11:24am UTC](https://discuss.elastic.co/t/upgrading-es-2-x-to-5-x-questions-about-elasticsearch-migration-output/66726/3 "2016-11-22T11:24:32Z")
Hi, thank you for the answers! It helped me a lot! > [@tanguy](#): > > it's a leftover in your configuration Well, that's my exact problem. 🙂 I don't find the parameter anywhere. I've looked at all the files in /etc/elasticsearch, I've looked at /\_cluster/state, /\_cluster/status, /\_cluster/health - no **foreground** anywhere... Edit: well, I've found "foreground": it's under /\_nodes/settings for each node. Still no idea where it comes from, because we definitely don't set this. Maybe a default value from 2.x? (I also have a 1.7 cluster running, that one doesn't have this property.) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 20, 2016, 11:24am UTC](https://discuss.elastic.co/t/upgrading-es-2-x-to-5-x-questions-about-elasticsearch-migration-output/66726/4 "2016-12-20T11:24:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.