# Elasticserach stuck

**URL:** <https://discuss.elastic.co/t/elasticserach-stuck/253735>\
**Category:** Elasticsearch\
**Created:** [October 29, 2020, 5:38pm UTC](https://discuss.elastic.co/t/elasticserach-stuck/253735 "2020-10-29T17:38:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafael\_Valverde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafael_valverde/32/47247_2.png) [@Rafael\_Valverde](https://discuss.elastic.co/u/Rafael_Valverde)\
**Post date:** [October 29, 2020, 5:38pm UTC](https://discuss.elastic.co/t/elasticserach-stuck/253735/1 "2020-10-29T17:38:56Z")

</div>

Elasticsearch after restart it.  
I ran curl -u admin\_elasticsearch -X DELETE [https://elasticsearch.bitbucket.com/bitbucket-search](https://elasticsearch.bitbucket.com/bitbucket-search)

then I rebuilt it

curl -u rxv112 -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' [https://bitbucket.com/rest/indexing/latest/sync](https://bitbucket.com/rest/indexing/latest/sync)

But I restarted because it was not working and after that it gets stuck when I start it up, the logs doesn’t show error, only says

[2020-10-29T17:13:15,951][INFO][o.e.t.TransportService] [dbbp1lc9a017] publish\_address {127.0.0.1:8080}, bound\_addresses {127.0.0.1:8080}  
[2020-10-29T17:13:19,032][INFO][o.e.c.s.ClusterService] [dbbp1lc9a017] new\_master {dbbp1lc9a017}{RkfUBapESeOAwplcyI\_e9A}{E2zJ\_xWVT\_mhSGfcdqGdYg}{localhost}{127.0.0.1:8080}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2020-10-29T17:13:19,077][INFO][o.e.h.n.Netty4HttpServerTransport] [dbbp1lc9a017] publish\_address {10.25.27.193:8085}, bound\_addresses {0.0.0.0:8085}  
[2020-10-29T17:13:19,078][INFO][o.e.n.Node] [dbbp1lc9a017] started  
[2020-10-29T17:13:19,136][INFO][o.e.g.GatewayService] [dbbp1lc9a017] recovered [0] indices into cluster\_state

---

<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:** [November 2, 2020, 11:44pm UTC](https://discuss.elastic.co/t/elasticserach-stuck/253735/2 "2020-11-02T23:44:44Z")

</div>

What version are you on?

Usually when it gets to that point it means that Elasticsearch is ready to serve requests.

---

<div class="post-metadata">

**Author:** ![Rafael\_Valverde](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafael_valverde/32/47247_2.png) [@Rafael\_Valverde](https://discuss.elastic.co/u/Rafael_Valverde)\
**Post date:** [November 3, 2020, 1:27am UTC](https://discuss.elastic.co/t/elasticserach-stuck/253735/3 "2020-11-03T01:27:56Z")

</div>

I have found the problem, the issue was caused by its index.

Thanks

---

<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:** [December 3, 2020, 1:27am UTC](https://discuss.elastic.co/t/elasticserach-stuck/253735/4 "2020-12-03T01:27:58Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.