# Shard Reallocation While Indexing

**URL:** <https://discuss.elastic.co/t/shard-reallocation-while-indexing/380779>\
**Category:** Elasticsearch\
**Created:** [August 6, 2025, 4:58am UTC](https://discuss.elastic.co/t/shard-reallocation-while-indexing/380779 "2025-08-06T04:58:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [August 6, 2025, 7:50am UTC](https://discuss.elastic.co/t/shard-reallocation-while-indexing/380779/2 "2025-08-06T07:50:34Z")

</div>

There was a somewhat similar recent thread [here](https://discuss.elastic.co/t/is-there-a-way-to-determine-what-triggers-shard-movement/380047) which contains some useful diagnostic tips/info, as well as linking to other threads.

As in that thread, might be useful to share output of

```auto
GET /_cat/nodes?v&h=name,role,disk.used_percent,disk.used,disk.avail&s=role

```

> [@nchalise](#):
>
> How to avoid shard reallocation at the time of data indexing?

If at any instant there was no indexing ongoing how can the cluster know there will be no indexing in the next instant/second/minute/whatever? I guess if your indexing only happens at very specific and predictable times, you could code something, but ... seems wrong. Is the reallocation actually causing you / your clients some actual issue? Or is it that it's just unexpected. And, is your cluster stable, nodes are not semi-frequently leaving/re-joining the cluster?

---

_[View the full topic](https://discuss.elastic.co/t/shard-reallocation-while-indexing/380779)._