# Elasticsearch: Unable to start after heavy\[20GB\] data **URL:** \ **Category:** Elasticsearch\ **Created:** [April 11, 2016, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977 "2016-04-11T10:29:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\ **Post date:** [April 11, 2016, 10:29am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/1 "2016-04-11T10:29:47Z")
I am using Elasticsearch, Kibana for monitoring purpose, Yesterday as Elasticsearch was having 15 GB of indexed data, it was taking to much load to return result for the queries by Kibana. It was also showing errors on ES console so what we decided to do is to stop the instance and restart it. But after restarting the elasticsearch, it is staring with proper started message but after sometime is comes with the following message ``` [2016-04-11 15:43:27,890][WARN][cluster.action.shard] [Doctor Druid] [cses sion-2016.04.11_09.22.19][2] received shard failed for [csession-2016.04.11_09.2 2.19][2], node[0XJiUVb5RvOtD153JuxC0A], [P], v[113], s[INITIALIZING], a[id=CG9to IZURPqvXt0DP97uWg], unassigned_info[[reason=ALLOCATION_FAILED], at[2016-04-11T10 :13:27.347Z], details[failed recovery, failure IndexShardRecoveryException[faile d recovery]; nested: TranslogException[failed to create new translog file]; nest ed: FileAlreadyExistsException[D:\ES\elasticsearch\data\elasticsearch\nodes\0\in dices\csession-2016.04.11_09.22.19\2\translog\translog-2.tlog]; ]], indexUUID [l m2b-t02SyWO8P_RfBh1qg], message [master {Doctor Druid}{0XJiUVb5RvOtD153JuxC0A}{1 0.76.133.15}{10.76.133.15:9300} marked shard as initializing, but shard is marke d as failed, resend shard failure], failure [Unknown] [2016-04-11 15:43:28,048][WARN][cluster.action.shard] [Doctor Druid] [cses sion-2016.04.11_09.22.19][2] received shard failed for [csession-2016.04.11_09.2 2.19][2], node[0XJiUVb5RvOtD153JuxC0A], [P], v[113], s[INITIALIZING], a[id=CG9to IZURPqvXt0DP97uWg], unassigned_info[[reason=ALLOCATION_FAILED], at[2016-04-11T10 :13:27.347Z], details[failed recovery, failure IndexShardRecoveryException[faile d recovery]; nested: TranslogException[failed to create new translog file]; nest ed: FileAlreadyExistsException[D:\ES\elasticsearch\data\elasticsearch\nodes\0\in dices\csession-2016.04.11_09.22.19\2\translog\translog-2.tlog]; ]], indexUUID [l m2b-t02SyWO8P_RfBh1qg], message [master {Doctor Druid}{0XJiUVb5RvOtD153JuxC0A}{1 0.76.133.15}{10.76.133.15:9300} marked shard as initializing, but shard is marke d as failed, resend shard failure], failure [Unknown] [2016-04-11 15:43:28,317][WARN][cluster.action.shard] [Doctor Druid] [cses sion-2016.04.11_09.22.19][2] received shard failed for [csession-2016.04.11_09.2 2.19][2], node[0XJiUVb5RvOtD153JuxC0A], [P], v[113], s[INITIALIZING], a[id=CG9to IZURPqvXt0DP97uWg], unassigned_info[[reason=ALLOCATION_FAILED], at[2016-04-11T10 :13:27.347Z], details[failed recovery, failure IndexShardRecoveryException[faile d recovery]; nested: TranslogException[failed to create new translog file]; nest ed: FileAlreadyExistsException[D:\ES\elasticsearch\data\elasticsearch\nodes\0\in dices\csession-2016.04.11_09.22.19\2\translog\translog-2.tlog]; ]], indexUUID [l m2b-t02SyWO8P_RfBh1qg], message [master {Doctor Druid}{0XJiUVb5RvOtD153JuxC0A}{1 0.76.133.15}{10.76.133.15:9300} marked shard as initializing, but shard is marke d as failed, resend shard failure], failure [Unknown] ``` Also, when I start kibana, it displays following error message, ``` D:\ES\kibana\bin>kibana log [15:42:19.509] [info][status][plugin:kibana] Status changed from uniniti alized to green - Ready log [15:42:19.536] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [15:42:19.549] [info][status][plugin:kbn_vislib_vis_types] Status change d from uninitialized to green - Ready log [15:42:19.553] [info][status][plugin:markdown_vis] Status changed from u ninitialized to green - Ready log [15:42:19.562] [info][status][plugin:metric_vis] Status changed from uni nitialized to green - Ready log [15:42:19.568] [info][status][plugin:spyModes] Status changed from unini tialized to green - Ready log [15:42:19.572] [info][status][plugin:statusPage] Status changed from uni nitialized to green - Ready log [15:42:19.575] [info][status][plugin:table_vis] Status changed from unin itialized to green - Ready log [15:42:19.608] [info][listening] Server running at http://0.0.0.0:5601 log [15:42:22.143] [error][status][plugin:elasticsearch] Status changed from yellow to red - Elasticsearch is still initializing the kibana index... Trying again in 2.5 second. ``` ---
**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:** [April 12, 2016, 5:57am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/2 "2016-04-12T05:57:11Z")
Try moving the file that it mentions in the ES log somewhere else, then start ES. ---
**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\ **Post date:** [April 13, 2016, 6:05am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/3 "2016-04-13T06:05:43Z")
Hi @warkolm, Do you mean **translog-2.tlog** file as per above log? ---
**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:** [April 13, 2016, 6:09am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/4 "2016-04-13T06:09:49Z")
Yes, don't delete it just move it. ---
**Author:** ![krushnat\_khawale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krushnat_khawale/32/6652_2.png) [@krushnat\_khawale](https://discuss.elastic.co/u/krushnat_khawale)\ **Post date:** [April 13, 2016, 6:15am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/5 "2016-04-13T06:15:03Z")
Okay @warkolm, This is a fix or trial an error? I'm asking because I've started another instance for now. So if its gonna fix, I would need to start topbeat, packetbeat on servers which were stopped. ---
**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:** [April 13, 2016, 6:49am UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/6 "2016-04-13T06:49:20Z")
This will stop that error you are seeing. ---
**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:59pm UTC](https://discuss.elastic.co/t/elasticsearch-unable-to-start-after-heavy-20gb-data/46977/7 "2017-07-05T22:59:43Z")