# Rolling upgrade from v5.6 to v6.8 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 6, 2019, 6:46pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852 "2019-11-06T18:46:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 6, 2019, 6:46pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/1 "2019-11-06T18:46:03Z")
Hi guys, I read the documentation regarding the rolling upgrade procedure that could be used to do not interrupt service. In my cluster, I have this situation: 3 master nodes 12 data nodes 2 coordinating only nodes 2 kibana 2 logstash Leaving aside KB and LS nodes, can you said to me the correct order to upgrade Elasticsearch's nodes? I mean, should I upgrade all the master nodes and then the data? and coordinating only? ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [November 9, 2019, 12:00am UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/2 "2019-11-09T00:00:55Z")
> [@rschirin](#): > > I mean, should I upgrade all the master nodes and then the data? and coordinating only? Have you seen our [Rolling Upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html#rolling-upgrades) guide? It describes that upgrade sequence in general and also has a link to issues related to 5.6-6.8 upgrade in particular. ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 10, 2019, 11:41am UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/3 "2019-11-10T11:41:29Z")
Hi @Igor_Motov, I already read those article. My doubt was just related to the correct order. If I update the master nodes at the beginning, I will have MASTER with v.6.8 and DATA with v.5.6.x. So, customers will be still able to access documents or not? And after that, when I will start to upgrade DATA nodes, is it ok to have a hybrid situation (5.6.x and 6.8.x both)? ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [November 11, 2019, 2:46pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/4 "2019-11-11T14:46:29Z")
> [@rschirin](#): > > So, customers will be still able to access documents or not? That's the whole idea of rolling restart instead of full cluster restart, isn't it? > [@rschirin](#): > > And after that, when I will start to upgrade DATA nodes, is it ok to have a hybrid situation (5.6.x and 6.8.x both)? Yes, as long as it is a temporary situation. There are some limitations on shard allocation in these mixed clusters, so you shouldn't leave it like this for a prolonged period of time. ---
**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\ **Post date:** [November 11, 2019, 3:03pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/5 "2019-11-11T15:03:45Z")
I suppose that all I have to do is to try 🙂 thanks! ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [November 11, 2019, 3:10pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/6 "2019-11-11T15:10:30Z")
> Do. Or do not. There is no try. Just kidding. That is one of the scenarios that we testing for in every build. However, it is always a good idea to test this in a test environment before doing it in production, just to make sure that you don't have any client code that is not compatible with 6.x. Once a node is upgraded to 6.8, it cannot be downgraded to 5.4. You will have to remove all data from the node and if you upgraded more than one node, the only way to go back is but cleaning the cluster and restoring everything from snapshots. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 9, 2019, 3:10pm UTC](https://discuss.elastic.co/t/rolling-upgrade-from-v5-6-to-v6-8/206852/7 "2019-12-09T15:10:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.