# Indexes completely erased **URL:** \ **Category:** Elasticsearch\ **Created:** [April 23, 2011, 7:46am UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280 "2011-04-23T07:46:01Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![byuva](https://avatars.discourse-cdn.com/v4/letter/b/b5ac83/32.png) [@byuva](https://discuss.elastic.co/u/byuva)\ **Post date:** [April 23, 2011, 7:46am UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/1 "2011-04-23T07:46:01Z")
I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) but left the storage containing ES untouched. Upon restarting ES I saw several errors in the log. I was on a fresh install and the log seemed to indicate I had not changed the nofiles limits. After changing this to 32000 and restarting there were no more errors in the log however I was horrified to see that a good chunk of my indexes had been completely erased (that is they still existed by were now completely empty )! A gist of a small portion of my log file can be found at : [https://gist.github.com/938449](https://gist.github.com/938449) -brian ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 23, 2011, 10:14am UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/2 "2011-04-23T10:14:33Z")
When did you build the 0.16 version? How many nodes were in the cluster? On Saturday, April 23, 2011 at 10:46 AM, merrellb wrote: > I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) > but left the storage containing ES untouched. Upon restarting ES I > saw several errors in the log. I was on a fresh install and the log > seemed to indicate I had not changed the nofiles limits. After > changing this to 32000 and restarting there were no more errors in the > log however I was horrified to see that a good chunk of my indexes had > been completely erased (that is they still existed by were now > completely empty )! A gist of a small portion of my log file can be > found at : > > [https://gist.github.com/938449](https://gist.github.com/938449) > > -brian ---
**Author:** ![byuva](https://avatars.discourse-cdn.com/v4/letter/b/b5ac83/32.png) [@byuva](https://discuss.elastic.co/u/byuva)\ **Post date:** [April 23, 2011, 3:04pm UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/3 "2011-04-23T15:04:57Z")
It appears it was build from Master about a month ago (March 16th). I am only running a single node. On Apr 23, 6:14 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > When did you build the 0.16 version? How many nodes were in the cluster? > > On Saturday, April 23, 2011 at 10:46 AM, merrellb wrote: > > > I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) > > but left the storage containing ES untouched. Upon restarting ES I > > saw several errors in the log. I was on a fresh install and the log > > seemed to indicate I had not changed the nofiles limits. After > > changing this to 32000 and restarting there were no more errors in the > > log however I was horrified to see that a good chunk of my indexes had > > been completely erased (that is they still existed by were now > > completely empty )! A gist of a small portion of my log file can be > > found at : > > > [https://gist.github.com/938449](https://gist.github.com/938449) > > > -brian ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 23, 2011, 8:25pm UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/4 "2011-04-23T20:25:33Z")
I think, based on the failure, that this was fixed in latest master (for a single node case). 0.16 will be released today. Sorry about that! On Saturday, April 23, 2011 at 6:04 PM, merrellb wrote: > It appears it was build from Master about a month ago (March 16th). I > am only running a single node. > > On Apr 23, 6:14 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > When did you build the 0.16 version? How many nodes were in the cluster? > > > > On Saturday, April 23, 2011 at 10:46 AM, merrellb wrote: > > > > > I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) > > > but left the storage containing ES untouched. Upon restarting ES I > > > saw several errors in the log. I was on a fresh install and the log > > > seemed to indicate I had not changed the nofiles limits. After > > > changing this to 32000 and restarting there were no more errors in the > > > log however I was horrified to see that a good chunk of my indexes had > > > been completely erased (that is they still existed by were now > > > completely empty )! A gist of a small portion of my log file can be > > > found at : > > > > > [https://gist.github.com/938449](https://gist.github.com/938449) > > > > > -brian ---
**Author:** ![byuva](https://avatars.discourse-cdn.com/v4/letter/b/b5ac83/32.png) [@byuva](https://discuss.elastic.co/u/byuva)\ **Post date:** [April 24, 2011, 4:35am UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/5 "2011-04-24T04:35:33Z")
Thanks Shay. Certainly not fun losing data although I suppose such are the risks of running Master. Glad the fix was able to make it into 0.16. -brian On Apr 23, 4:25 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > I think, based on the failure, that this was fixed in latest master (for a single node case). 0.16 will be released today. Sorry about that! > > On Saturday, April 23, 2011 at 6:04 PM, merrellb wrote: > > > It appears it was build from Master about a month ago (March 16th). I > > am only running a single node. > > > On Apr 23, 6:14 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > When did you build the 0.16 version? How many nodes were in the cluster? > > > > On Saturday, April 23, 2011 at 10:46 AM, merrellb wrote: > > > > > > > I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) > > > > but left the storage containing ES untouched. Upon restarting ES I > > > > saw several errors in the log. I was on a fresh install and the log > > > > seemed to indicate I had not changed the nofiles limits. After > > > > changing this to 32000 and restarting there were no more errors in the > > > > log however I was horrified to see that a good chunk of my indexes had > > > > been completely erased (that is they still existed by were now > > > > completely empty )! A gist of a small portion of my log file can be > > > > found at : > > > > > [https://gist.github.com/938449](https://gist.github.com/938449) > > > > > -brian ---
**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\ **Post date:** [April 24, 2011, 7:44pm UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/6 "2011-04-24T19:44:07Z")
did you change the elasticsearch.json ? On Apr 24, 6:35 am, merrellb [br...@merrells.org](mailto:br...@merrells.org) wrote: > Thanks Shay. Certainly not fun losing data although I suppose such > are the risks of running Master. Glad the fix was able to make it > into 0.16. > > -brian > > On Apr 23, 4:25 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > I think, based on the failure, that this was fixed in latest master (for a single node case). 0.16 will be released today. Sorry about that! > > > On Saturday, April 23, 2011 at 6:04 PM, merrellb wrote: > > > > > It appears it was build from Master about a month ago (March 16th). I > > > am only running a single node. > > > > On Apr 23, 6:14 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > > > > > When did you build the 0.16 version? How many nodes were in the cluster? > > > > > On Saturday, April 23, 2011 at 10:46 AM, merrellb wrote: > > > > > > > > > I recently reinstalled my OS (upgrading from Ubuntu 32-bit to 64-bit) > > > > > but left the storage containing ES untouched. Upon restarting ES I > > > > > saw several errors in the log. I was on a fresh install and the log > > > > > seemed to indicate I had not changed the nofiles limits. After > > > > > changing this to 32000 and restarting there were no more errors in the > > > > > log however I was horrified to see that a good chunk of my indexes had > > > > > been completely erased (that is they still existed by were now > > > > > completely empty )! A gist of a small portion of my log file can be > > > > > found at : > > > > > > [https://gist.github.com/938449](https://gist.github.com/938449) > > > > > > -brian ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:07am UTC](https://discuss.elastic.co/t/indexes-completely-erased/4280/7 "2017-07-06T04:07:44Z")
Closed on July 6, 2017, 4:07am UTC