Because you have to load data from the shard when you get a query, so the larger the shard the more data you load, and OOM or slower response times happen.
It also helps recovery and reallocation if they are smaller. On 5 January 2015 at 13:13, Jinyuan Zhou <[email protected]> wrote: > I read some where that max recommended shard size is about 50G. > What are biggest bad consequences when shard size is too large. > I have, for some indice, shard size more than 100G on a jvm with 29G > fixed heap size. I suspect this is one factor that caused OutofMemory > problem. > However I don't know if large shard size will results in memory issue. I > can only think of longer seek time. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/ce84aba7-67a5-4484-ac93-e86cc3f7384b%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/ce84aba7-67a5-4484-ac93-e86cc3f7384b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-trGqU0u%3DCVcO8puRcDW-EcgdwLtGHd8EojgbHChVq2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
