Hm... I suspect that the load isn't equally distributed. Am I right? I should have mentioned with the same load on the same index with the same query rate.
And if it's low load you can probably get away with it but once the load scales it's not going to be super fun. On Tuesday, October 7, 2014 12:38:11 PM UTC-7, Nikolas Everett wrote: > > We have hundreds of shards on machines with two SSDs each. Some are large > shards (20GB) but most are small (a couple MB). It works fine except for > some trouble how Elasticsearch picks what shards go where (hint: it doesn't > take shard size into account beyond not filling up the disks). > > Nik > > On Tue, Oct 7, 2014 at 3:32 PM, [email protected] <javascript:> < > [email protected] <javascript:>> wrote: > >> The number of shards is in not related to HDD or SSD. >> >> SSD reduces vastly the latency of I/O operations, ES must no longer wait >> for I/O seeks, reads, or writes, so the overall throughput is significantly >> faster, which is noticeable while indexing bulks of data. >> >> Jörg >> >> On Tue, Oct 7, 2014 at 9:07 PM, Kevin Burton <[email protected] >> <javascript:>> wrote: >> >>> I'm curious how many shards would be too many shards per server... and >>> wanted feedback based on community experience. >>> >>> On HDD you probably want to be a big conservative.... but on SSD I think >>> you could probably get away with a higher number. >>> >>> 10 seems to be somewhat reasonable I imagine. Not perfect but not bad >>> either. This way you could grow 10x... >>> >>> PS. Really a shame that ES can't do shard splitting yet. >>> >>> -- >>> 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] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/8c22ef66-5794-4c74-9410-5d83d3a1ee5d%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/elasticsearch/8c22ef66-5794-4c74-9410-5d83d3a1ee5d%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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGx9PW7yGfC6z2J074rzryVDmtLNgSRYPddJ1dS%2BEMmxg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGx9PW7yGfC6z2J074rzryVDmtLNgSRYPddJ1dS%2BEMmxg%40mail.gmail.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/408d8091-272b-4bea-8510-b68541cc578f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
