我有一个包含 2 个节点的集群。
我试图了解连接节点的最佳实践,并在一个节点出现停机时检查故障转移。
from 文档 http://elasticsearch-py.readthedocs.io/en/master/api.html#nodes:
es = Elasticsearch(
['esnode1', 'esnode2'],
# sniff before doing anything
sniff_on_start=True,
# refresh nodes after a node fails to respond
sniff_on_connection_fail=True,
# and also every 60 seconds
sniffer_timeout=60
)
所以我尝试像这样连接到我的节点:
client = Elasticsearch([ip1, ip2],sniff_on_start=True, sniffer_timeout=10,sniff_on_connection_fail=True)
其中 ip1/ip2 是机器 IP(例如 10.0.0.1、10.0.0.2)
为了测试它,我终止了 ip2 (或者放置不存在的 if )
现在,当我尝试连接时,我总是得到:
TransportError: TransportError(N/A, 'Unable to sniff hosts - no viable hosts found.')
即使 ip1 已存在并已启动。
如果我尝试像这样连接:
es = Elasticsearch([ip1, ip2])
然后我可以在日志中看到,如果客户端没有从 ip2 收到任何响应,它将移动到 ip1,并返回有效响应。
那么我在这里错过了什么吗?我认为通过嗅探,如果其中一个节点已关闭,客户端不会抛出任何异常,并继续使用活动节点(直到下一次嗅探)
update:
当我将 sniff 设置为“True”时,我会得到这种行为:
----> 1 client = Elasticsearch([ip1, ip2],sniff_on_start=True)
/usr/local/lib/python2.7/dist-packages/elasticsearch/client/__init__.pyc in __init__(self, hosts, transport_class, **kwargs)
148 :class:`~elasticsearch.Connection` instances.
149 """
--> 150 self.transport = transport_class(_normalize_hosts(hosts), **kwargs)
151
152 # namespaced clients for compatibility with API names
/usr/local/lib/python2.7/dist-packages/elasticsearch/transport.pyc in __init__(self, hosts, connection_class, connection_pool_class, host_info_callback, sniff_on_start, sniffer_timeout, sniff_timeout, sniff_on_connection_fail, serializer, serializers, default_mimetype, max_retries, retry_on_status, retry_on_timeout, send_get_body_as, **kwargs)
128
129 if sniff_on_start:
--> 130 self.sniff_hosts(True)
131
132 def add_connection(self, host):
/usr/local/lib/python2.7/dist-packages/elasticsearch/transport.pyc in sniff_hosts(self, initial)
235 # transport_schema or host_info_callback blocked all - raise error.
236 if not hosts:
--> 237 raise TransportError("N/A", "Unable to sniff hosts - no viable hosts found.")
238
239 self.set_connections(hosts)