# ELK upgrade from 6.6 to 7.4.2 **URL:** \ **Category:** Elasticsearch\ **Created:** [November 12, 2019, 1:03pm UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513 "2019-11-12T13:03:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [November 12, 2019, 1:03pm UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513/1 "2019-11-12T13:03:01Z")
HI, I am currently planning an upgrade from ELK 6.6 to 7.4.2 but I would like to do this as rolling upgrade because having the entire cluster restart or down is not an option. According to the documentation, full cluster restart seems to be the only possible way of upgrading directly from 6.6 to 7.4.2: [https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html) I would like to know if a rolling upgrade is possible and if yes: - What are some of the things I might need to keep in mind for this procedure - Is there any documentation for the best possible practices to be followed for such an rolling upgrade between major versions? - How should the data migration be taken care of when upgrading between 6.6 to 7.4? Can we just follow normal rolling upgrade steps or do we need reindexing or some procedure like that to be followed? Thanks, Radhika ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [November 12, 2019, 3:32pm UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513/2 "2019-11-12T15:32:27Z")
No, a rolling upgrade is not possible from 6.6 all the way to 7.4 in one step. The [docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) list the permitted rolling upgrade paths. The best practices are documented at the link you shared. ---
**Author:** ![rshetty](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rshetty](https://discuss.elastic.co/u/rshetty)\ **Post date:** [November 13, 2019, 3:54am UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513/3 "2019-11-13T03:54:45Z")
Hi David, Thank you for confirming regarding the rolling upgrade. So the only possible way is to either: - Do a rolling upgrade of the 6.6 cluster to 6.7 or 6.8 prior to beginning the rolling up grade to 7.4.2 - Full cluster restart to directly upgrade it from 6.6 to 7.4 as according to the [doc](https://www.elastic.co/guide/en/elasticsearch/reference/current/restart-upgrade.html) Is re-indexing required for 6.6 indices, if we move it to 7.4 or is that only required for indexes prior to 6.x like 5.x or so on? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [November 13, 2019, 4:45am UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513/4 "2019-11-13T04:45:39Z")
This is also answered in the [very same page of the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html): > Elasticsearch can read indices created in the previous major version. If you have indices created in 5.x or before, you must reindex or delete them before upgrading to 7.4.2. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 11, 2019, 4:45am UTC](https://discuss.elastic.co/t/elk-upgrade-from-6-6-to-7-4-2/207513/5 "2019-12-11T04:45:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.