Hi Adrien,
Thank you so much for your reply. Yes both the clusters were having
the same configurations. And one more point, I missed out. I've configured
the master node and data node in separate docker container. Did the usage
of docker has anything to do with this slowness issue.
Thanks again in advance.
-Anand
On Tuesday, 18 November 2014 16:59:38 UTC+5:30, Adrien Grand wrote:
>
> There are so many moving factors, it is hard to help. Do both clusters
> have exactly the same hardware, network infrastructure, number of nodes,
> ... ? You can potentially try to capture where your nodes are spending time
> during slow queries with the hot_threads API.
>
> On Tue, Nov 18, 2014 at 9:58 AM, Anand kumar <anand...@gmail.com
> <javascript:>> wrote:
>
>> And also addition to this, when I import the indices to another cluster,
>> all the cluster wont be available in the newer cluster. What should be done
>> to make all the indices available over there?
>>
>>
>> On Monday, 17 November 2014 15:00:43 UTC+5:30, Anand kumar wrote:
>>>
>>>
>>>
>>> I'm having a search engine for source code of different repositories. In
>>> which the cluster consist of about 500 indices and about 1.8 million
>>> documents with its full content.
>>>
>>> And am facing slowness issue while searching the content, its taking a
>>> little extra time to display the results.
>>>
>>> Those indices in the cluster were imported from the other cluster, if so
>>> will the metadata of those indices will cause any difference in search
>>> performance? Previously it was working fine, but after importing indices to
>>> another cluster and searching in the new cluster makes the performance
>>> degradation.
>>>
>>> My configurations for the index is as:
>>>
>>> index.number_of_shards: 1
>>> index.number_of_replicas: 0
>>>
>>>
>>> Any suggestions would be helpful.
>>>
>>> Regards,
>>> Anand
>>>
>>> --
>> 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 elasticsearc...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/67c80fa3-71c6-4bf7-81aa-6782ae50df82%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/67c80fa3-71c6-4bf7-81aa-6782ae50df82%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Adrien Grand
>
--
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/c19983f9-0a4a-4c9d-95a6-7371d383521e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
