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.
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.
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.
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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.