Any reason not to enable http.compression?


(David Severski) #1

I recently learned that ES's default for http.compression is false (no
compression). A quick search through the archives find several instances of
folks turning this on. Are there counter indications to enabling
compression? My main goal is to enable some remote scan queries executed
via the elasticsearch-py helper to be more kind to my network links. The
only other things hitting my ES 1.2.1 cluster via HTTP are Kibana and
Logstash.

Thanks for the advice and warnings!

David

--
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/0ec89d21-73ae-4adc-b98a-e280525d1e1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2