How do I "explicitly override" the shared network settings as hinted in the network module docs to put different TCP components on different networks?
Do I just, for example, set different transport.network.bind_host/publish_host and http.network.bind_host/publish_host etc. or transport.bind_host/publish_host and http.network.bind_host/publish_host etc. instead of setting them under the shared network module?
There isn't a simplistic pure "http"/"transport" prefix setting for that (I will add it), but you can explicitly set it for netty (the default networking library elasticsearch uses):
-shay.banon
On Monday, February 21, 2011 at 7:16 PM, Sorostaran wrote:
How do I "explicitly override" the shared network settings as hinted in the
network module docs to put different TCP components on different networks?
Do I just, for example, set different
transport.network.bind_host/publish_host and
http.network.bind_host/publish_host etc. or transport.bind_host/publish_host
and http.network.bind_host/publish_host etc. instead of setting them under
the shared network module?
There isn't a simplistic pure "http"/"transport" prefix setting for that (I will add it), but you can explicitly set it for netty (the default networking library elasticsearch uses):
-shay.banon
On Monday, February 21, 2011 at 7:16 PM, Sorostaran wrote:
How do I "explicitly override" the shared network settings as hinted in the
network module docs to put different TCP components on different networks?
Do I just, for example, set different
transport.network.bind_host/publish_host and
http.network.bind_host/publish_host etc. or transport.bind_host/publish_host
and http.network.bind_host/publish_host etc. instead of setting them under
the shared network module?
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.