# Data Node Allocation Weight **URL:** \ **Category:** Elasticsearch\ **Created:** [March 20, 2015, 2:30pm UTC](https://discuss.elastic.co/t/data-node-allocation-weight/22779 "2015-03-20T14:30:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![smonasco\_2](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@smonasco\_2](https://discuss.elastic.co/u/smonasco_2)\ **Post date:** [March 20, 2015, 2:30pm UTC](https://discuss.elastic.co/t/data-node-allocation-weight/22779/1 "2015-03-20T14:30:52Z")
Hi, I'm in a bit of a crunch. We have some servers we added to our cluster whose processors were not as good as the older servers. I'd rather not get into how we got swindled into accepting them, but this leaves me in a place with imbalanced hardware between my nodes. The crunch bit comes in that during our peak load we begin to have slow queries which lead to rejected queries once we max out the CPUs on the new machines. I'm trying to find a way to tell ES to put more shards on the more powerful nodes. The simplest idea, would be if I could give a weight to servers or something else rather than try to move shards around by hand, create zones and force some indexes into them, etc. --Shannon Monasco -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [March 20, 2015, 7:57pm UTC](https://discuss.elastic.co/t/data-node-allocation-weight/22779/2 "2015-03-20T19:57:49Z")
If you have hot and cold data, you could allocate the cold data to those nodes (see > **[Cluster-level shard allocation and routing settings | Elasticsearch Guide...](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html)** ). Or you could allocate those nodes to be master only, but that may be a resource waste. On 20 March 2015 at 07:30, smonasco [smonasco@gmail.com](mailto:smonasco@gmail.com) wrote: > Hi, > > I'm in a bit of a crunch. We have some servers we added to our cluster > whose processors were not as good as the older servers. I'd rather not get > into how we got swindled into accepting them, but this leaves me in a place > with imbalanced hardware between my nodes. > > The crunch bit comes in that during our peak load we begin to have slow > queries which lead to rejected queries once we max out the CPUs on the new > machines. > > I'm trying to find a way to tell ES to put more shards on the more > powerful nodes. > > The simplest idea, would be if I could give a weight to servers or > something else rather than try to move shards around by hand, create zones > and force some indexes into them, etc. > > --Shannon Monasco > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/c4d9eb0b-fc46-4f40-a4c0-809632dec5b8%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X97if4Wdyr6RDQBwgeGaBE-7Bxutb\_G5fQSM%3DW%3DVDVdwQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X97if4Wdyr6RDQBwgeGaBE-7Bxutb_G5fQSM%3DW%3DVDVdwQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:25am UTC](https://discuss.elastic.co/t/data-node-allocation-weight/22779/3 "2017-07-06T00:25:18Z")