# Cluster.max\_shards\_per\_node

**URL:** <https://discuss.elastic.co/t/cluster-max-shards-per-node/157263>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [November 19, 2018, 3:43am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263 "2018-11-19T03:43:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [November 19, 2018, 3:43am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/1 "2018-11-19T03:43:26Z")

</div>

I see following message through `Dev Tools` in `Kibana`:

> #! Deprecation: In a future major version, this request will fail because this action would add [10] total shards, but this cluster currently has [9556]/[5000] maximum shards open. Before upgrading, reduce the number of shards in your cluster or adjust the cluster setting [cluster.max\_shards\_per\_node].

yet via `Monitoring` data node has about 2000.

Please advise.

---

<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 19, 2018, 4:07am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/2 "2018-11-19T04:07:08Z")

</div>

What is the output from the `_cat/health?v` API?

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [November 19, 2018, 4:11am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/3 "2018-11-19T04:11:31Z")

</div>

```
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1542600474 04:07:54 x green x 5 9612 4805 0 0 0 0 - 100.0%
```

---

<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 19, 2018, 4:13am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/4 "2018-11-19T04:13:07Z")

</div>

Ok, then as it's suggesting you need to reduce your shard count.

What is the output from `_cat/indices?v`.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 19, 2018, 6:12am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/5 "2018-11-19T06:12:11Z")

</div>

That is indeed a new warning that you have far too many shards for a cluster that size. Please read [this blog post on shards and siding practices](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) and work to reduce that significantly.

---

<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 17, 2018, 6:12am UTC](https://discuss.elastic.co/t/cluster-max-shards-per-node/157263/6 "2018-12-17T06:12:19Z")

</div>

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