On Monday 17 of November 2014 23:12:26 Christopher Ambler wrote: > I don't see how that's an issue. > > Data needs to be stored somewhere. If I'm hitting disk often, I'm going to > do so no matter what, no matter where. > > So why not have the data on all nodes?
Because your nodes usually only have enough memory to store a limited subset of your index. If nodes store all shards, they have to keep parts of all shards in memory for these to be queried efficiently. If you have enough memory, that will usually work fine. If there is a way to keep shards stored, but prevent elasticsearch from querying them (or otherwise trying to read them from disk), I'd sure like to know about it, because it would make a great way to do backups or recovery from a "passive" node without disrupting the file system cache on active nodes under load. -- Jure Koren -- 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/1799499.UjryPpiTIh%40coin. For more options, visit https://groups.google.com/d/optout.
