Your setup looks quite uncommon but I do not comment on that any further as you seem to know what you do, just the idea of creating single shard clusters and distributing them across data centers is counterintuitive to the advantages of an ES installation.
I recommend revising your settings, they look very odd. Why did you change the defaults? The heap size of 512m, this is definitely preventing more shards. Short answers to your questions - no, clustering / sharding is not the main key to performance, it is crucial for scalability - you can cluster not only in LANs, but over all kinds of hosts as long as they can respond fast "enough". Important for ES nodes is low latency on the network. High latency between nodes induces instabilities into ES which makes life hard as an operator. - if you mean client perspective, you should look at the Tribe node that can span multiple clusters http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-tribe.html Jörg On Mon, Jul 7, 2014 at 3:51 PM, 'Fin Sekun' via elasticsearch < elasticsearch@googlegroups.com> wrote: > > > *QUESTIONS* > > Are our assumptions correct? Especially: > > - Is clustering/sharding (also small indices) the main key to performance, > that means the only possibility to prevent overloaded (virtual) CPUs? > - Is it right that clustering is only useful/possible in LANs? > - Do you have any ES configuration or architecture hints regarding our > preference for using multiple hosting providers? > > > > -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFdT_08OkwAYy10zOizv9%2BJCpcLRbDYHq%2B2S5Tbq1ViYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
