blocks|key|2953283|text|bind_host设置控制Elasticsearch侦听的网络接口。因此，在具有多个NIC的计算机上，这将允许您控制将绑定到哪个ES。默认值0.0.0.0基本上表示“绑定到所有”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2953284|publish_host设置控制Elasticsearch向其他成员通告的IP地址。这必须是一个实际的IP地址，并且是其他集群成员将用于与ES节点通信的地址。|2953285|如果需要在多宿主服务器上执行一些特殊操作，可以将bind_host和publish_host设置为不同的值。不过，大多数用例都不需要这样做，因此network.host设置可以同时控制这两种情况。|2953286|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The bind_host setting controls what network interface Elasticsearch listens on. So on a machine that has multiple NICs this will allow you to control which one ES will bind to. The default of 0.0.0.0 basically means "bind to all".

The publish_host setting controls what IP address Elasticsearch announces to other members. This has to be an actual IP address and is what the other cluster members will use to communicate with the ES node.

You can set bind_host and publish_host to different values if you need to do something special on a multi-homed server. Most use cases won't need to though, hence the network.host setting controlling both.

blocks|key|155475|text|可以将它们设置为不同的值，并且在某些情况下非常有用。下面是我的用法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155476|我在数据中心有一个本地网络，在那里我运行由不同节点组成的elasticsearch集群。这意味着每台elasticsearch计算机都有两个ip地址，一个用于从外部计算机访问它，另一个用于本地连接到同一网络中的其他计算机。|155477|内部ip+(eth1)用于让elasticsearch的不同节点相互通信、发现等，而外部ip地址(eth0)是我在另一个网络中的web应用程序发出请求的地址。|155478|因此，简单地说，bind_host+(在我的例子中是两个ip，与连接所有接口的默认值0.0.0.0相同)是elasticsearch侦听的地方，而publish_host+(我的例子是内部ip+)是elasticsearch与其他集群组件通信的地方。|155479|这样，我的web应用程序在另一个网络中，可以从bind_host地址访问ES集群，而elasticsearch通过publish_host与集群通信。|155480|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

It is possible to set them to different values and really useful in some cases. Here is my usage: 

I have a local network in a data center where I run the elasticsearch cluster composed of different nodes. This means that every elasticsearch machine has two ip addresses, one to reach it from an external machine and the other to connect locally to other machines in the same network. 

The internal ip (eth1) is used to let different nodes of elasticsearch communicate, discover, etc. each other and the external ip address (eth0) is the one which my web application, which is in another network, makes the requests to. 

So in simple words, bind_host (both ip in my case, the same as default value 0.0.0.0 that attaches all interfaces) is where elasticsearch listens and publish_host (internal ip in my case) is where elasticsearch communicates with other cluster components.

This way, my web application being in another network, can access the ES cluster from the bind_host address, while elasticsearch communicates with the cluster with the publish_host.

blocks|key|2740467|text|下面的设置应该可以解决这个问题。它接受来自任何IP+(bind)的连接，并将自己的ip配置到第一个可用网络接口中的第一个non_loopback。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2740468|network.bind_host:+"0.0.0.0"
network.publish_host:+_non_loopback:ipv4_|code-block|syntax|javascript|2740469|要查看更多选项，请查看docs。|offset|length|2740470|entityMap|0|LINK|mutability|MUTABLE|url|https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html^0|0|0|B|4|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

The following setting should do the trick. It accepts connections from any IP (bind) and configures its self ip to the first non_loopback in the first available network interface.

<pre><code>network.bind_host: "0.0.0.0"
network.publish_host: _non_loopback:ipv4_
</code></pre>

To see more options, check the <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html" rel="noreferrer">docs</a>.

blocks|key|2953312|text|要检查此值，请通过API：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2953313|curl+http://ES:9200/_cat/master|code-block|syntax|javascript|2953314|请注意，主机名将被解析(因此永远不会公开)。|2953315|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

To check this value, via the API:

<pre><code>curl http://ES:9200/_cat/master
</code></pre>

Pay attention that hostname will be resolved (so never exposed).

blocks|key|2953322|text|根据我的理解，用一个打电话的比喻：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2953323|2953324|publish_host的意思是："Call+me+on+this+number"|unordered-list-item|offset|length|style|CODE|2953325|bind_host“意思是：”I‘’ll+on+this+number"|2953326|2953327|publish_host:+_non_loopback:ipv4_可以理解为：“无论我从哪个号码给你打电话，都可以给我打电话。”|2953328|entityMap^0|0|0|0|C|0|0|9|0|0|0|X|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|P|$]]

From what I understand, and to use a phone-calling analogy:

<ul>
<li><code>publish_host</code> means: "Call me on this number"</li>
<li><code>bind_host</code> means: "I'll answer on this number"</li>
</ul>

And <code>publish_host: _non_loopback:ipv4_</code> may be understood as: "Call me on whatever number I'm calling you from"

From this document <a href="http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-network.html" rel="noreferrer">network settings</a>, I know that publish_host is the host that other nodes in the cluster will communicate to. But I don't understand the functionality of bind_host, which means that:

<blockquote>
 The network.bind_host setting allows to control the host different network components will bind on. By default, the bind host will be anyLocalAddress (typically 0.0.0.0 or ::0). 
</blockquote>

And the network.host will set network.bind_host and network.publish_host to the same value. 

So I want to know why there's a need to set network.bind_host and if it's possible to set network.bind_host and network.publish_host to different values?

What's the difference between bind_host and publish_host in ElasticSearch?

Elasticsearch 

数据中心

服务器

从本文档中，我了解到publish_host是群集中的其他节点将与之通信的主机。但我不理解bind_host的功能，这意味着： network.bind_host设置允许控制将绑定不同网络组件的主机。默认情况下，绑定主机将为anyLocalAddress (通常为0.0.0.0或::0)。并且network.bind_...

问在ElasticSearch中，bind_host和publish_host有什么不同？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ElasticSearch中，bind_host和publish_host有什么不同？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ElasticSearch中，bind_host和publish_host有什么不同？
EN