Very slow performance with version upgradation in Elasticsearch

Hi All,

we have recently upgraded our production server from version 1.1.0 to
1.4.3. We actually imported the data from old cluster to new cluster with
minor data and mapping removals. But as compared to previous version, the
performance has been decreased. Many requests returning the time out in
response. The application has broken, as we are using it as a source of
data reads.

Our cluster is having 3 nodes of configurations of 8 core, 60GB RAM. Is
there any default settings changes that can cause such side effects. I am
facing issues like,
search requests are very slow
data retrieval after saving is not instant.

Please let me know the area to work on. All help or guidance will be
appreciated.

Thanks

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

That depends on what your settings, your data and your queries are like.

On 24 February 2015 at 22:00, Narinder Kaur narinder.kaur@izap.in wrote:

Hi All,

we have recently upgraded our production server from version 1.1.0 to
1.4.3. We actually imported the data from old cluster to new cluster with
minor data and mapping removals. But as compared to previous version, the
performance has been decreased. Many requests returning the time out in
response. The application has broken, as we are using it as a source of
data reads.

Our cluster is having 3 nodes of configurations of 8 core, 60GB RAM. Is
there any default settings changes that can cause such side effects. I am
facing issues like,
search requests are very slow
data retrieval after saving is not instant.

Please let me know the area to work on. All help or guidance will be
appreciated.

Thanks

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_9W3hO_V1LjbFVs7LaDJfD5QHdkctu3PoCVFRFR1XeKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can you please ask me some specific question on settings,data and queries.
So that I can explain.

On Wednesday, 25 February 2015 11:22:58 UTC+5:30, Mark Walkom wrote:

That depends on what your settings, your data and your queries are like.

On 24 February 2015 at 22:00, Narinder Kaur <narind...@izap.in
<javascript:>> wrote:

Hi All,

we have recently upgraded our production server from version 1.1.0 to
1.4.3. We actually imported the data from old cluster to new cluster with
minor data and mapping removals. But as compared to previous version, the
performance has been decreased. Many requests returning the time out in
response. The application has broken, as we are using it as a source of
data reads.

Our cluster is having 3 nodes of configurations of 8 core, 60GB RAM. Is
there any default settings changes that can cause such side effects. I am
facing issues like,
search requests are very slow
data retrieval after saving is not instant.

Please let me know the area to work on. All help or guidance will be
appreciated.

Thanks

--
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/f5733673-3aa1-4e5d-9831-a4c29eda65c0%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e53e0f5f-c3d7-47e5-9493-a188406b1c99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

If you can gist/pastebin/etc your config and query and document samples,
and provide some details around your cluster size and architecture, as well
as where you are seeing slowness, then it will make the troubleshooting
process a lot easier.

On 25 February 2015 at 18:15, Narinder Kaur narinder.kaur@izap.in wrote:

Can you please ask me some specific question on settings,data and queries.
So that I can explain.

On Wednesday, 25 February 2015 11:22:58 UTC+5:30, Mark Walkom wrote:

That depends on what your settings, your data and your queries are like.

On 24 February 2015 at 22:00, Narinder Kaur narind...@izap.in wrote:

Hi All,

we have recently upgraded our production server from version 1.1.0 to
1.4.3. We actually imported the data from old cluster to new cluster with
minor data and mapping removals. But as compared to previous version, the
performance has been decreased. Many requests returning the time out in
response. The application has broken, as we are using it as a source of
data reads.

Our cluster is having 3 nodes of configurations of 8 core, 60GB RAM. Is
there any default settings changes that can cause such side effects. I am
facing issues like,
search requests are very slow
data retrieval after saving is not instant.

Please let me know the area to work on. All help or guidance will be
appreciated.

Thanks

--
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.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/f5733673-3aa1-4e5d-9831-a4c29eda65c0%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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/e53e0f5f-c3d7-47e5-9493-a188406b1c99%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/e53e0f5f-c3d7-47e5-9493-a188406b1c99%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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8xA1qeh%2ByiZsbFN5dQjfDoMwUew0wqudvi03bETVkXqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.