将Spring与Docker中的Elasticsearch连接

Question

我必须将我的Spring客户端与Elasticsearch连接，Elasticsearch的图像已由Elastic在Docker Hub中的官方ES 2.4.6图像拍摄，但当我尝试运行容器时，Docker控制台向我报告以下错误：

[Glitch]无法连接到节点[{{transport}-1}{localhost}{127.0.0.1:9300}]，已从节点列表中删除

应用程序。我的Spring项目的属性是：

spring.data.elasticsearch.cluster-nodes=localhost:9300
index.v = default
server.port = 8443

还有码头工人。yml是：

version: "2.2"

services:
    elk:
        image: cvazquezlos/elk:2.4.6
        ports:
            - 5000:5000
            - 5601:5601
            - 9200:9200
            - 9300:9300
        volumes:
            - elk-data:/var/lib/elasticsearch

    testloganalyzer:
        image: cvazquezlos/testloganalyzer
        ports:
            - 8443:8443

volumes: 
    elk-data:

如果我在没有Docker的情况下运行后端，它会按预期工作，但是当我在没有Docker的情况下运行后端时，会报告我上述错误。完全错误是：

failed to connect to node [{#transport#-1}{localhost}{127.0.0.1:9300}], removed from nodes list

org.elasticsearch.transport.ConnectTransportException: [][127.0.0.1:9300] connect_timeout[30s]
        at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:967) ~[elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:933) ~[elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:906) ~[elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:267) ~[elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.doSample(TransportClientNodesService.java:390) ~[elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.client.transport.TransportClientNodesService$NodeSampler.sample(TransportClientNodesService.java:336) [elasticsearch-2.4.6.jar!/:2.4.6]
        at org.elasticsearch.client.transport.TransportClientNodesService$ScheduledNodeSampler.run(TransportClientNodesService.java:369) [elasticsearch-2.4.6.jar!/:2.4.6]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_151]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_151]
        at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
Caused by: java.net.ConnectException: Connection refused: localhost/127.0.0.1:9300
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.8.0_151]
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[na:1.8.0_151]
        at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) ~[netty-3.10.6.Final.jar!/:na]
        at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ~[netty-3.10.6.Final.jar!/:na]
        ... 3 common frames omitted

Answer 1

我认为您缺少docker compose配置中的网络部分，请尝试以下操作：

version: "2.2"

services:
    elk:
        image: cvazquezlos/elk:2.4.6
        ports:
            - 5000:5000
            - 5601:5601
            - 9200:9200
            - 9300:9300
        networks:
            - elk-network
        volumes:
            - elk-data:/var/lib/elasticsearch

    testloganalyzer:
        image: cvazquezlos/testloganalyzer
        ports:
            - 8443:8443
        networks:
            - elk-network

volumes: 
    elk-data:

networks:
    elk-network:
        driver: bridge

Answer 2

当SpringBoot服务在docker中工作时，它无法将localhost解析为ES主机。在这种情况下，您还可以使用链接属性，如下所示：

在testloganalyzer部分添加链接选项：

testloganalyzer:
    image: cvazquezlos/testloganalyzer
    ports:
        - 8443:8443
    links:
        - elk:elk

首先是服务，其次是别名。

接下来在application.properties中更改it引用：

spring.data.elasticsearch.cluster-nodes=elk:9300