Setting Transport and HTTP to different networks

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?

Heya,

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):

transport.netty.bind_host
transport.netty.publish_host

http.netty.bind_host
http.netty.publish_host

-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?

View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Setting-Transport-and-HTTP-to-different-networks-tp2546637p2546637.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.

ok, pushed the simplified settings: Add `http` and `transport` simplified host settings · Issue #706 · elastic/elasticsearch · GitHub. You can do this now with the explicit netty settings.
On Monday, February 21, 2011 at 7:46 PM, Shay Banon wrote:

Heya,

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):

transport.netty.bind_host
transport.netty.publish_host

http.netty.bind_host
http.netty.publish_host

-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?

View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Setting-Transport-and-HTTP-to-different-networks-tp2546637p2546637.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.