# Lost index after Cluster fiddling

**URL:** <https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970>\
**Category:** Elasticsearch\
**Created:** [September 25, 2015, 9:27am UTC](https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970 "2015-09-25T09:27:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_Fielding](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_fielding/32/39406_2.png) [@Marc\_Fielding](https://discuss.elastic.co/u/Marc_Fielding)\
**Post date:** [September 25, 2015, 9:27am UTC](https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970/1 "2015-09-25T09:27:58Z")

</div>

Hi Everyone,

I've recently started out with Elastic and had everything running absolutely perfectly on my local dev machine.

Yesterday I thought I'd get an idea of how clusters work, so I installed Elastic on my Raspberry Pi 2, gave it an IP address, the same cluster name and a proper node name.

I noticed connect messages on the console of my windows machine, in Marvel although the little summary at the top showed 2 nodes in the node list it only ever showed the windows machine and both nodes. I used the \_cluster endpoint to investigate and it appeared they'd connected ok.

This morning I wake up, sit down and clicked refresh on a PHP API I was working on(using elastic) and got "No nodes available" despite the one on my local machine apparently being up and green AND the other on the Pi!

After a couple of restarts on both the Pi and the windows box I was still getting the same error so I decided to stop the node on the Pi and switch the configuration of the windows machine back to it's localhost settings(network host to 127.0.0.1).

Now the index I created has completely disappeared!

1. What did I do wrong?

2. Is there any way to fix it?

Kind Regards

Marc

---

<div class="post-metadata">

**Author:** ![Marc\_Fielding](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc_fielding/32/39406_2.png) [@Marc\_Fielding](https://discuss.elastic.co/u/Marc_Fielding)\
**Post date:** [September 25, 2015, 3:25pm UTC](https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970/2 "2015-09-25T15:25:03Z")

</div>

The first issue I couldn't figure out so I overwrote my elastic directory with a fresh download, set the cluster and node name. Fired up under windows and then on my Pi, they're now talking just fine.

The problem with data - Obviously when you change the cluster name Elastic sets up a new directory for the data, so I had elastic-marc.dev yesterday and when things started breaking I changed it to elastic.

I still don't know what caused the problem overnight when everything seemed to get corrupted but will see what happens today!

Regards

Marc

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 25, 2015, 11:33pm UTC](https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970/3 "2015-09-25T23:33:22Z")

</div>

There should be evidence of something in the logs, GC causing node timeouts or something else.

---

<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, 11:47pm UTC](https://discuss.elastic.co/t/lost-index-after-cluster-fiddling/29970/4 "2017-07-05T23:47:59Z")

</div>