# Experiences with Elastic Upgrades from 1.X

**URL:** <https://discuss.elastic.co/t/experiences-with-elastic-upgrades-from-1-x/134523>\
**Category:** Elasticsearch\
**Created:** [June 5, 2018, 5:50am UTC](https://discuss.elastic.co/t/experiences-with-elastic-upgrades-from-1-x/134523 "2018-06-05T05:50:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johnnycc1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnnycc1/32/26069_2.png) [@Johnnycc1](https://discuss.elastic.co/u/Johnnycc1)\
**Post date:** [June 5, 2018, 5:50am UTC](https://discuss.elastic.co/t/experiences-with-elastic-upgrades-from-1-x/134523/1 "2018-06-05T05:50:15Z")

</div>

Hey Guys,

I have written up my experiences with upgrading a few elasticsearch clusters from V1.X to V6.X over at github.

> **[swarmee/projects](https://github.com/swarmee/projects/tree/master/elasticsearch-V1.X-to-V6.X-upgrades)**
>
> projects - Various Projects Using Elasticsearch

I've included a docker-compose with elastic 1.7.5 (with kibana + sense) & 6.2.4 (with kibana and dev\_tools) so you can run some re-indexing tests quickly and easily.

I have also included a docker-compose for a logstash container which can be used to apply templates to the new cluster and move the data in a simple `docker-compose up` command.

---

<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 3, 2018, 5:50am UTC](https://discuss.elastic.co/t/experiences-with-elastic-upgrades-from-1-x/134523/2 "2018-07-03T05:50:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
