I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts). I
need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts). I
need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
Thanks a lot for the quick response. Does elasticsearch itself has any
restful API for me to enable the option "http.compression"? Thus, one http
request to the ES cluster will do the job for me.
Xiaolin.
On Wednesday, February 18, 2015 at 2:10:32 PM UTC-8, Mark Walkom wrote:
Yes this is an update and restart.
You should really be using things like puppet/chef/ansible to manage
config
On 19 February 2015 at 08:51, Xiaolin Xie <alph...@gmail.com <javascript:>
wrote:
Hi ES guys
I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts). I
need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
Thanks a lot for the quick response. Does elasticsearch itself has any
restful API for me to enable the option "http.compression"? Thus, one http
request to the ES cluster will do the job for me.
Xiaolin.
On Wednesday, February 18, 2015 at 2:10:32 PM UTC-8, Mark Walkom wrote:
Yes this is an update and restart.
You should really be using things like puppet/chef/ansible to manage
config
I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts). I
need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
I am a little bit confused here. The option(http.compression) makes
elasticsearch return a "zipped" http response to client when possible (with
Accept-Encoding). Why does it request the close of indices? what do you
mean "close" here?
In addition, what is the http endpoint for enable this option?
Thanks a lot for your help
Xiaolin.
On Wednesday, February 18, 2015 at 4:18:31 PM UTC-8, Mark Walkom wrote:
Turns out you can enable this dynamically, but you have to close all your
indices for it to be accepted.
On 19 February 2015 at 10:08, Xiaolin Xie <alph...@gmail.com <javascript:>
wrote:
Hi Mark
Thanks a lot for the quick response. Does elasticsearch itself has any
restful API for me to enable the option "http.compression"? Thus, one http
request to the ES cluster will do the job for me.
Xiaolin.
On Wednesday, February 18, 2015 at 2:10:32 PM UTC-8, Mark Walkom wrote:
Yes this is an update and restart.
You should really be using things like puppet/chef/ansible to manage
config
I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts).
I need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
There are some settings you can update dynamically so I tried to see if I
could update this one dynamically.
It initially looked like my tests worked, hence my comment, but further
testing shows I was going down the wrong path. So apologies about that
You will need to update your config and restart the process for it to be
read.
I am a little bit confused here. The option(http.compression) makes
elasticsearch return a "zipped" http response to client when possible (with
Accept-Encoding). Why does it request the close of indices? what do you
mean "close" here?
In addition, what is the http endpoint for enable this option?
Thanks a lot for your help
Xiaolin.
On Wednesday, February 18, 2015 at 4:18:31 PM UTC-8, Mark Walkom wrote:
Turns out you can enable this dynamically, but you have to close all your
indices for it to be accepted.
Thanks a lot for the quick response. Does elasticsearch itself has any
restful API for me to enable the option "http.compression"? Thus, one http
request to the ES cluster will do the job for me.
Xiaolin.
On Wednesday, February 18, 2015 at 2:10:32 PM UTC-8, Mark Walkom wrote:
Yes this is an update and restart.
You should really be using things like puppet/chef/ansible to manage
config
I am a n00b to elasticsearch. We have a cluster of ES nodes(24 hosts).
I need to enable the "http.compression" to for this cluster. Do I have to
manually edit the elasticsearch.yml file in each host and then restart
elasticserach service in each host to take the configuration change? Is
there an easier way for me to do that, such as a http endpoint to enable
the "http.compression"?
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.
