# Elasticsearch 5.0.0-alpha1 --\> 5.0.0-alpha5

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215>\
**Category:** Elasticsearch\
**Created:** [August 29, 2016, 4:46pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215 "2016-08-29T16:46:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![veve90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/veve90/32/6517_2.png) [@veve90](https://discuss.elastic.co/u/veve90)\
**Post date:** [August 29, 2016, 4:46pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/1 "2016-08-29T16:46:46Z")

</div>

Hello,

I have a cluster in 5.0.0-alpha1. Are indexes created with this version compatible 5.0.0-alpha5? can I update without loosing my data?

Thank you!

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [August 29, 2016, 5:10pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/2 "2016-08-29T17:10:57Z")

</div>

Maybe but we don't guarantee it. I know for a fact that the wire protocol has changed so you'll need to shut down the whole cluster then upgrade then start it up again. The on disk structure might be the same depending on the features you've used but it probably isn't.

---

<div class="post-metadata">

**Author:** ![veve90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/veve90/32/6517_2.png) [@veve90](https://discuss.elastic.co/u/veve90)\
**Post date:** [September 2, 2016, 3:41pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/3 "2016-09-02T15:41:06Z")

</div>

I did a yum update...

```
016-09-02 17:39:37,351][INFO][node] [elk] initializing ...
[2016-09-02 17:39:37,418][INFO][env] [elk] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [1.4tb], net total_space [1.9tb], spins? [unknown], types [rootfs]
[2016-09-02 17:39:37,418][INFO][env] [elk] heap size [19.9gb], compressed ordinary object pointers [true]
[2016-09-02 17:39:38,144][INFO][node] [elk] version[5.0.0-alpha5], pid[11148], build[d327dd4/2016-08-04T08:59:39.568Z], OS[Linux/3.10.0-229.14.1.el7.x86_64/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_65/25.65-b01]
[2016-09-02 17:39:38,899][INFO][io.netty.util.internal.PlatformDependent] Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
[2016-09-02 17:39:38,903][INFO][plugins] [elk] loaded module [aggs-matrix-stats]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [ingest-common]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [lang-expression]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [lang-groovy]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [lang-mustache]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [lang-painless]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [percolator]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [reindex]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [transport-netty3]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] loaded module [transport-netty4]
[2016-09-02 17:39:38,904][INFO][plugins] [elk] no plugins loaded

```

and it hangs at no plugins loaded....

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [September 2, 2016, 3:54pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/4 "2016-09-02T15:54:51Z")

</div>

It is hanging _after_ `no plugins loaded`. If you nuke the old data directory does it start? If so then that is ok - not great, but, again, we don't offer on disk compatibility between alpha versions. Same for betas. Only released versions have on disk compatibility and we're quite careful to keep it.

---

<div class="post-metadata">

**Author:** ![veve90](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/veve90/32/6517_2.png) [@veve90](https://discuss.elastic.co/u/veve90)\
**Post date:** [September 2, 2016, 4:26pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/5 "2016-09-02T16:26:27Z")

</div>

it is starting if I change the cluster name, so yes..

---

<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, 10:22pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-0-alpha1-5-0-0-alpha5/59215/6 "2017-07-05T22:22:47Z")

</div>