Ignore lost shards and make cluster health from RED to GREEN

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
  • 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!
but this post only reveal the upside of less shards_count, and tested with facets not aggs.

thanks!