Hello Eliott ,
I suspect if this has something to do with client creation.
Can you see the time taken for the query alone and not the client creation.
Other possible reasons can be refresh flag ON.
Please check that also.
Thanks
Vineeth
On Wed, Aug 20, 2014 at 10:11 PM, Elliott Bradshaw <[email protected]>
wrote:
> Vineeth,
>
> Thanks, but according to the documentation, it looks like sniffing is only
> supported when using the TransportClient. I'm using the standard
> Node/Client configuration.
>
>
> On Wednesday, August 20, 2014 12:24:45 PM UTC-4, vineeth mohan wrote:
>
>> Hello Elliot ,
>>
>> Is the sniffing enabled while creating the client.
>> This means that , it will determine which all machines are enabled and
>> does some load balancing.
>> Which means that it needs additional time while creating the client.
>>
>> Thanks
>> Vineeth
>>
>>
>> On Wed, Aug 20, 2014 at 9:39 PM, Elliott Bradshaw <[email protected]>
>> wrote:
>>
>>> I'm joining an existing cluster as a node via the Java API. I generate
>>> a relatively complicated multi-index "indices" query that combines the
>>> results of two different queries on two modestly sized indexes (150M
>>> records combined). Execution of actionGet() on this query takes
>>> approximately 1-2 seconds. On the other hand, if I dump the same query to
>>> JSON via the XContent jsonBuilder() and execute it with curl, it takes only
>>> 14 ms. Results are identical in both cases.
>>>
>>> Has anyone else had similar problems like this? Any thoughts on what
>>> might be the source of the problem? My next thought was to try connecting
>>> to the cluster via a TransportClient. Not sure if it will help or not...
>>>
>>> Thanks!
>>>
>>> - Elliott
>>>
>>> --
>>> 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/fa4fb57e-3beb-4e80-8672-1981bcb8c35c%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/elasticsearch/fa4fb57e-3beb-4e80-8672-1981bcb8c35c%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/bfae9628-0212-4b03-8f76-4fb85aab23e9%40googlegroups.com
> <https://groups.google.com/d/msgid/elasticsearch/bfae9628-0212-4b03-8f76-4fb85aab23e9%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/CAGdPd5m7B_iaHJwudFcFEbwcVab3hjEo5KWWg_3hLwmaDhuKDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
