Query response times in the order of 5-10 seconds can not be made much
faster just because of different-sized nodes, there must be other reasons.
Right now, according to shard management, ES assumes all nodes to be equal
regarding JVM capacity, and it is not a good thing to set up indexes in
production spanning over machines with different capacity. The relation of
a shard size and the JVM power under it will got skewed.
At query time, ES selects the responses from shards that return fastest, so
if all of your large JVM hold a replica, you won't get much faster response
with an index distributed over equal nodes I'm afraid of.
On Monday, September 17, 2012 6:58:56 PM UTC+2, T Vinod Gupta wrote:
i have a cluster of 2 nodes on aws - 1 m1.large and 1 m1.xlarge. i
allocated 4GB on the former and 8GB on the latter for ES. i also have a
m1.large non-data non-master node in addition to act as a load balancer. we
are seeing high latency on search queries. indexing is happening at a very
high rate in parallel.
i was wondering if the asymmetry in the topology is causing any slowness.
the cpu usage is high in both nodes due to ES process.
searches are taking over 5-10 seconds. trying hard to figure out how to
speed up the queries.