# Recovery translog after server crash not working **URL:** \ **Category:** Elasticsearch\ **Created:** [October 24, 2016, 10:51am UTC](https://discuss.elastic.co/t/recovery-translog-after-server-crash-not-working/63739 "2016-10-24T10:51:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Aguay-val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aguay-val/32/12674_2.png) [@Aguay-val](https://discuss.elastic.co/u/Aguay-val)\ **Post date:** [October 24, 2016, 10:51am UTC](https://discuss.elastic.co/t/recovery-translog-after-server-crash-not-working/63739/1 "2016-10-24T10:51:57Z")
Hi, I'm using elasticsearch with graylog to store my logs. It worked perfectly before my server crash. After recovering my server i restart graylog and elasticsearch. But, after the elasticsearch node has restarted there was a problem onto a primary shard. Elasticsearch tried to recover it with translog files, but after 5 days of working, nothing happens. THe shard is still recovering and my translog folder keep growing. Now it's over 477Go. My index size is only 18Go and my indice of this shards around 5,6Go. I'm pretty new to elasticsearch and i don't know what i can do. ---
**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:** [October 26, 2016, 10:00am UTC](https://discuss.elastic.co/t/recovery-translog-after-server-crash-not-working/63739/2 "2016-10-26T10:00:44Z")
The simple answer is to delete the index, assuming you don't need the data. Otherwise posting logs and more info on your setup would be helpful. ---
**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:09pm UTC](https://discuss.elastic.co/t/recovery-translog-after-server-crash-not-working/63739/3 "2017-07-05T22:09:35Z")