无法连接到我的Elasticsearch实例:NoNodeAvailableException

时间:2018-03-22 22:13:18

标签: java docker elasticsearch docker-compose elasticsearch-5

无法连接到我的Elasticsearch:

docker-compose up

运行命令:

curl -XGET http://localhost:9200/_nodes/http?pretty

输出:

{
  "cluster_name" : "elasticsearch",
  "nodes" : {
    "qD18rHzhQaexExUw5sBgXg" : {
      "name" : "Scanner",
      "transport_address" : "172.19.0.3:9300",
      "host" : "172.19.0.3",
      "ip" : "172.19.0.3",
      "version" : "6.2.3",
      "build" : "fcbb46d",
      "http_address" : "172.19.0.3:9200",
      "http" : {
        "bound_address" : [ "0.0.0.0:9200" ],
        "publish_address" : "172.19.0.3:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

与传输客户端连接:

public Client client() throws Exception {
    Settings settings = Settings.builder()
        .put("spring.data.elasticsearch.cluster-nodes", "localhost:9300")
        .build();

    TransportClient client = TransportClient.builder()
        .settings(settings)
        .build()
        .addTransportAddress(new InetSocketTransportAddress(InetAddress.getByName("localhost"), 9300));
    return client;
}

获取错误:

Caused by: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{localhost}{127.0.0.1:9300}]]
    at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:326)
    at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:223)

搬运工-compose.yml

services:
  elasticsearch:
    image: elasticsearch
    ports:
      - '9200:9200'
      - '9300:9300'
  kibana:
    image: kibana
    ports:
      - '5601:5601'
    environment:
      - ELASTICSEARCH_URL=http://elasticsearch:9200

Dockerfile

FROM elasticsearch, kibana
EXPOSE 9200
EXPOSE 9300

(运行本地安装的Elasticsearch 没有 Docker它可以工作!)

我做错了什么?知道怎么解决吗?

2 个答案:

答案 0 :(得分:0)

传输端点绑定在elasticsearch容器内的localhost上。这就是它只能从容器本身访问的原因。

传输端点应绑定到0.0.0.0容器中的"transport_address" : "0.0.0.0:9300"elasticsearch),并且可以通过localhost:9300在主机上通过localhost访问它。 / p>

因此,您可以使用以下docker-compose.yaml

实现这一目标
version: "3"
services:
  elasticsearch:
    image: elasticsearch
    command: "-Etransport.host=0.0.0.0"
    ports:
      - '9200:9200'
      - '9300:9300'
  kibana:
    image: kibana
    ports:
      - '5601:5601'
    environment:
      - ELASTICSEARCH_URL=http://elasticsearch:9200

<强>更新

如果您只是使用上述docker-compose.yamlelasticsearch容器在启动时失败并显示以下错误:

elasticsearch_1  | [2018-03-26T07:44:13,475][INFO ][o.e.n.Node               ] [rzYPgrJ] starting ...
elasticsearch_1  | [2018-03-26T07:44:13,663][INFO ][o.e.t.TransportService   ] [rzYPgrJ] publish_address {172.17.0.2:9300}, bound_addresses {0.0.0.0:9300}
elasticsearch_1  | [2018-03-26T07:44:13,688][INFO ][o.e.b.BootstrapChecks    ] [rzYPgrJ] bound or publishing to a non-loopback address, enforcing bootstrap checks
elasticsearch_1  | ERROR: [1] bootstrap checks failed
elasticsearch_1  | [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
elasticsearch_1  | [2018-03-26T07:44:13,696][INFO ][o.e.n.Node               ] [rzYPgrJ] stopping ...
elasticsearch_1  | [2018-03-26T07:44:13,747][INFO ][o.e.n.Node               ] [rzYPgrJ] stopped
elasticsearch_1  | [2018-03-26T07:44:13,747][INFO ][o.e.n.Node               ] [rzYPgrJ] closing ...
elasticsearch_1  | [2018-03-26T07:44:13,762][INFO ][o.e.n.Node               ] [rzYPgrJ] closed

那是因为我们在transport endpoint上更改了0.0.0.0

为了解决这个问题,有必要在主机mashine上增加vm.max_map_count sysctl参数,至少为262144

sudo sysctl -w vm.max_map_count=262144

现在,您可以docker-compose up成功启动两个容器。

答案 1 :(得分:0)

当降级到elasticsearch时:2.4.4它有效,我怀疑它与SpringData不兼容最新的Elasticsearch。

   ...
    services:
      elasticsearch:
        image: elasticsearch:2.4.4
        ports:
          - '9200:9200'
          - '9300:9300'
      kibana:
        image: kibana:4.6.1
    ...

图表:

https://github.com/spring-projects/spring-data-elasticsearch

https://www.elastic.co/support/matrix