# Ignore lost shards and make cluster health from RED to GREEN **URL:** \ **Category:** Elasticsearch\ **Created:** [October 1, 2015, 12:46am UTC](https://discuss.elastic.co/t/ignore-lost-shards-and-make-cluster-health-from-red-to-green/31433 "2015-10-01T00:46:55Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![no\_jihun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/no_jihun/32/64028_2.png) [@no\_jihun](https://discuss.elastic.co/u/no_jihun)\ **Post date:** [October 1, 2015, 9:29am UTC](https://discuss.elastic.co/t/ignore-lost-shards-and-make-cluster-health-from-red-to-green/31433/5 "2015-10-01T09:29:14Z")
Thanks @magnusbaeck. btw. could you please let me know more about > That depends on the performance of your nodes, the mappings, and the query patterns I saw many articles which generally says - a little overallocation good to scalability - shard consume resources, so too many shard make performance/resource issue. In my situation - there is no one document get. - you can see my mapping at this thread [How to add not analyzed field with dynamic tempate? - #3 by no\_jihun](https://discuss.elastic.co/t/how-to-add-not-analyzed-field-with-dynamic-tempate/31391/3) - cluster is under pressure both cpu and ram. - there are about 10 times full gc which takes 10~20secs per a day per a node. - almost of the query is aggretations which made by kibana dashboard in date range 1day ~ 30days. all node's hardward is - 22GB RAM(to es), 24v cores. It would be great if you let me know or give some url something like [Trifork Blog - Keep updated on the technical solutions Trifork is working on!](http://blog.trifork.com/2014/01/07/elasticsearch-how-many-shards/) but this post only reveal the upside of less shards\_count, and tested with facets not aggs. thanks! --- _[View the full topic](https://discuss.elastic.co/t/ignore-lost-shards-and-make-cluster-health-from-red-to-green/31433)._