# Changing max\_number\_of\_shards\_per\_node **URL:** \ **Category:** Elasticsearch\ **Created:** [August 19, 2010, 6:46am UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234 "2010-08-19T06:46:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Pablo\_Borges](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pablo_borges/32/3313_2.png) [@Pablo\_Borges](https://discuss.elastic.co/u/Pablo_Borges)\ **Post date:** [August 19, 2010, 6:46am UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/1 "2010-08-19T06:46:10Z")
Hello there! This shows up in cluster state (Cluster Admin from the Rest API) and it doesn't seem to be a configurable option (at least I couldn't find it). Is there a way to increase this value ? Cheers, ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 19, 2010, 1:43pm UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/2 "2010-08-19T13:43:52Z")
I have removed this option for now, there should be an option to restrict what can run on each node, but it should be more properly implemented. -shay.banon On Thu, Aug 19, 2010 at 9:46 AM, Pablo Borges [pablort@gmail.com](mailto:pablort@gmail.com) wrote: > Hello there! > > This shows up in cluster state (Cluster Admin from the Rest API) and it > doesn't seem to be a configurable option (at least I couldn't find it). > > Is there a way to increase this value ? > > Cheers, ---
**Author:** ![Pablo\_Borges](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pablo_borges/32/3313_2.png) [@Pablo\_Borges](https://discuss.elastic.co/u/Pablo_Borges)\ **Post date:** [August 19, 2010, 7:04pm UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/3 "2010-08-19T19:04:34Z")
So we're restricted to a maximum number of 100 shards per node ? That's not good. ☹ On Thu, Aug 19, 2010 at 10:43 AM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > I have removed this option for now, there should be an option to restrict > what can run on each node, but it should be more properly implemented. > > -shay.banon > > On Thu, Aug 19, 2010 at 9:46 AM, Pablo Borges [pablort@gmail.com](mailto:pablort@gmail.com) wrote: > > > Hello there! > > > > This shows up in cluster state (Cluster Admin from the Rest API) and it > > doesn't seem to be a configurable option (at least I couldn't find it). > > > > Is there a way to increase this value ? > > > > Cheers, ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 19, 2010, 9:50pm UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/4 "2010-08-19T21:50:46Z")
No, I mean there is no restriction. By the way, 100 shards on a node is quite a lot, test your system to see that it does not create a load on it. On Thu, Aug 19, 2010 at 10:04 PM, Pablo Borges [pablort@gmail.com](mailto:pablort@gmail.com) wrote: > So we're restricted to a maximum number of 100 shards per node ? That's not > good. ☹ > > On Thu, Aug 19, 2010 at 10:43 AM, Shay Banon \<[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) > > > wrote: > > > I have removed this option for now, there should be an option to restrict > > what can run on each node, but it should be more properly implemented. > > > > -shay.banon > > > > On Thu, Aug 19, 2010 at 9:46 AM, Pablo Borges [pablort@gmail.com](mailto:pablort@gmail.com) wrote: > > > > > Hello there! > > > > > > This shows up in cluster state (Cluster Admin from the Rest API) and it > > > doesn't seem to be a configurable option (at least I couldn't find it). > > > > > > Is there a way to increase this value ? > > > > > > Cheers, ---
**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\ **Post date:** [August 20, 2010, 7:13am UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/5 "2010-08-20T07:13:32Z")
I think I just hit similar. Started new single machine cluster instance, created indexes w/ 141 shards + mappings, loaded a bunch of content. However, the cluster will not start back up until I add an extra node. I must admit that I know I have too many shards for some of my various data buckets, but it'd be nice if this restriction was applied at index creation time. Thanks On Aug 19, 3:50 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > No, I mean there is no restriction. By the way, 100 shards on a node is > quite a lot, test your system to see that it does not create a load on it. > > On Thu, Aug 19, 2010 at 10:04 PM, Pablo Borges [pabl...@gmail.com](mailto:pabl...@gmail.com) wrote: > > > So we're restricted to a maximum number of 100 shards per node ? That's not > > good. ☹ > > > On Thu, Aug 19, 2010 at 10:43 AM, Shay Banon \<[shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > wrote: > > > > I have removed this option for now, there should be an option to restrict > > > what can run on each node, but it should be more properly implemented. > > > > -shay.banon > > > > On Thu, Aug 19, 2010 at 9:46 AM, Pablo Borges [pabl...@gmail.com](mailto:pabl...@gmail.com) wrote: > > > > > Hello there! > > > > > This shows up in cluster state (Cluster Admin from the Rest API) and it > > > > doesn't seem to be a configurable option (at least I couldn't find it). > > > > > Is there a way to increase this value ? > > > > > Cheers, ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [August 20, 2010, 9:22am UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/6 "2010-08-20T09:22:39Z")
This restriction is not there anymore, it has been removed. Those types of restriction, by the way, can't be applied on index creation time, as a cluster is a live thing, and what happens on creation time might not be relevant later on. -shay.banon On Fri, Aug 20, 2010 at 10:13 AM, Paul [ppearcy@gmail.com](mailto:ppearcy@gmail.com) wrote: > I think I just hit similar. Started new single machine cluster > instance, created indexes w/ 141 shards + mappings, loaded a bunch of > content. However, the cluster will not start back up until I add an > extra node. > > I must admit that I know I have too many shards for some of my various > data buckets, but it'd be nice if this restriction was applied at > index creation time. > > Thanks > > On Aug 19, 3:50 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > No, I mean there is no restriction. By the way, 100 shards on a node is > > quite a lot, test your system to see that it does not create a load on > > it. > > > > On Thu, Aug 19, 2010 at 10:04 PM, Pablo Borges [pabl...@gmail.com](mailto:pabl...@gmail.com) > > wrote: > > > > > So we're restricted to a maximum number of 100 shards per node ? That's > > > not > > > good. ☹ > > > > > On Thu, Aug 19, 2010 at 10:43 AM, Shay Banon \< > > > [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) > > > > > > > wrote: > > > > > > I have removed this option for now, there should be an option to > > > > restrict > > > > what can run on each node, but it should be more properly implemented. > > > > > > -shay.banon > > > > > > On Thu, Aug 19, 2010 at 9:46 AM, Pablo Borges [pabl...@gmail.com](mailto:pabl...@gmail.com) > > > > wrote: > > > > > > > Hello there! > > > > > > > This shows up in cluster state (Cluster Admin from the Rest API) and > > > > > it > > > > > doesn't seem to be a configurable option (at least I couldn't find > > > > > it). > > > > > > > Is there a way to increase this value ? > > > > > > > Cheers, ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:20am UTC](https://discuss.elastic.co/t/changing-max-number-of-shards-per-node/3234/7 "2017-07-06T04:20:30Z")