# \_reindex has suddenly stopped working inexplicably

**URL:** <https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375>\
**Category:** Elasticsearch\
**Created:** [February 2, 2024, 8:47am UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375 "2024-02-02T08:47:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrodent](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mrodent](https://discuss.elastic.co/u/mrodent)\
**Post date:** [February 2, 2024, 8:47am UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375/1 "2024-02-02T08:47:48Z")

</div>

I've been using the `_reindex` endpoint for some time now, about 2 months, without any problems.

I'm running ES 8.6.2 on port 9500. The OS is W10.

For some reason, as of this morning, any attempts to reindex are just not ending. The indices in question are about 20 MB or so: I've let the operation run on for as much as 3 minutes. I've tried running the command from the program (Python) but also from Insomnia.

I've also checked that the index I'm trying to reindex definitely does exist. I've also restarted the ES server. Other ES server commands appear to be working fine.

I've tried rebooting.

I notice that when I cancel the operation after many seconds, and then go `GET _cat/indices` I now see the new index which I was attempting to create with status "red" and apparently no documents (or stated size).

Any suggestions about what might be causing this?

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [February 5, 2024, 6:03pm UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375/2 "2024-02-05T18:03:10Z")

</div>

Thanks for reaching out @mrodent. I have a few follow up questions here:

- I am correct in understanding that you have't received any errors and it just seems to hang?
- Are all your attempts with data of the same size?
- Do you have a code sample you can send over?

This [blog post may also be helpful too](https://www.elastic.co/blog/3-best-practices-for-using-and-troubleshooting-the-reindex-api).

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 5, 2024, 6:27pm UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375/3 "2024-02-05T18:27:37Z")

</div>

> [@mrodent](#):
>
> I now see the new index which I was attempting to create with status "red"

[These docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html) describe how to troubleshoot this situation.

---

<div class="post-metadata">

**Author:** ![mrodent](https://avatars.discourse-cdn.com/v4/letter/m/65b543/32.png) [@mrodent](https://discuss.elastic.co/u/mrodent)\
**Post date:** [February 21, 2024, 7:20pm UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375/4 "2024-02-21T19:20:16Z")

</div>

Thanks both. Turned out the disk was too full and had exceeded the "high watermark". Had never heard of this before!

---

<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:** [March 20, 2024, 7:20pm UTC](https://discuss.elastic.co/t/reindex-has-suddenly-stopped-working-inexplicably/352375/5 "2024-03-20T19:20:25Z")

</div>

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