使用从here, thanks GraphAware guys
获取的略微修改的演示docker-compose运行我使用docker-compose up运行了一个成功的因果群集。然而，我无法使用docker swarm获得同样的东西。
撰写文件是相同的：
version: '3.3'
networks:
neonet:
driver: overlay
attachable: true
ipam:
config:
- subnet: 10.161.0.0/24
services:
neo-1:
image: neo4j:3.3.4-enterprise
networks:
- neonet
volumes:
- /srv/neo4j/neo4j-core1/data:/data
- /srv/neo4j/neo4j-core1/logs:/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_dbms_mode=CORE
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connector_http_listen__address=:7474
- NEO4J_dbms_connector_https_listen__address=:6477
- NEO4J_dbms_connector_bolt_listen__address=:7687
neo-2:
image: neo4j:3.3.4-enterprise
networks:
- neonet
volumes:
- /srv/neo4j/neo4j-core2/data:/data
- /srv/neo4j/neo4j-core2/logs:/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_dbms_mode=CORE
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connector_http_listen__address=:7474
- NEO4J_dbms_connector_https_listen__address=:6477
- NEO4J_dbms_connector_bolt_listen__address=:7687
neo-3:
image: neo4j:3.3.4-enterprise
networks:
- neonet
volumes:
- /srv/neo4j/neo4j-core3/data:/data
- /srv/neo4j/neo4j-core3/logs:/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_dbms_mode=CORE
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connector_http_listen__address=:7474
- NEO4J_dbms_connector_https_listen__address=:6477
- NEO4J_dbms_connector_bolt_listen__address=:7687
..除了docker-compose up我既没有指定覆盖网络细节，也没有部署细节。两个集群都在一台机器上运行。
如果我进入独立docker-compose的容器，ip地址看起来没问题，端口5000是'curlable';为群集部署容器执行相同操作（curl ip：5000）会导致连接被拒绝。
正在运行netstat -ntlp：
/var/lib/neo4j # netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 10.161.0.166:5000 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.11:44137 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:7000 0.0.0.0:* LISTEN -
让端口5000监听一个不属于该机器上任何接口的ip地址（ifconfig）：
eth0 Link encap:Ethernet HWaddr 02:42:0A:A1:00:A7
inet addr:10.161.0.167 Bcast:10.161.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
RX packets:119 errors:0 dropped:0 overruns:0 frame:0
TX packets:119 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7110 (6.9 KiB) TX bytes:7110 (6.9 KiB)
eth1 Link encap:Ethernet HWaddr 02:42:AC:12:00:06
inet addr:172.18.0.6 Bcast:172.18.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:648 (648.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:3604 (3.5 KiB) TX bytes:3604 (3.5 KiB)
..你可以看到有2个接口，我的 neonet 网络，以及（我假设）docker的 ingress 。
此外，neo4j已通过配置指示自己在所有接口上侦听发现：
causal_clustering.transaction_listen_address=0.0.0.0:6000
causal_clustering.transaction_advertised_address=2a9e1683a92e:6000
causal_clustering.raft_listen_address=0.0.0.0:7000
causal_clustering.raft_advertised_address=2a9e1683a92e:7000
causal_clustering.initial_discovery_members=neo1:5000,neo2:5000,neo3:5000
causal_clustering.expected_core_cluster_size=3
causal_clustering.discovery_listen_address=0.0.0.0:5000
causal_clustering.discovery_advertised_address=2a9e1683a92e:5000
EDITION=enterprise
ACCEPT.LICENSE.AGREEMENT=yes
......但是以某种方式做出决定听取某个IP - 它为5000做了但不是7000做了。
我不是网络基金会，但是听一台绑定在这台机器上没有接口的IP是不正确的。
如何指示Neo4J绑定到所有接口？或者至少是一个有效的？
答案 0 :(得分：0)
原来有多个修复程序，核心是设置deploy.endpoint_node: dnsrr以防止创建docker虚拟IP。最后，我的工作swarm文件如下所示。
工作=多个节点工作neo4j因果核心集群（仅）;使用Neo4J OGM v3客户端连接URL bolt+routing://neo-1:7687 100％工作。我还没有足够勇敢尝试对初始连接进行故障转移;所以SPF在neo-1上（最初）。
version: '3.3'
services:
neo-1:
image: neo4j:3.3.4-enterprise
volumes:
- neo-data:/data
- neo-logs:/var/lib/neo4j/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_causalClustering_discoveryAdvertisedAddress=neo-1:5000
- NEO4J_causalClustering_transactionAdvertisedAddress=neo-1:6000
- NEO4J_causalClustering_raftAdvertisedAddress=neo-1:7000
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connectors_default__advertised__address=neo-1
- NEO4J_dbms_connector_bolt_advertised__address=:7687
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_dbms_mode=CORE
deploy:
mode: global
endpoint_mode: dnsrr
placement:
constraints:
- node.labels.neodb == 1
networks:
- neonet
neo-2:
image: neo4j:3.3.4-enterprise
volumes:
- neo-data:/data
- neo-logs:/var/lib/neo4j/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_causalClustering_discoveryAdvertisedAddress=neo-2:5000
- NEO4J_causalClustering_transactionAdvertisedAddress=neo-2:6000
- NEO4J_causalClustering_raftAdvertisedAddress=neo-2:7000
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connectors_default__advertised__address=neo-2
- NEO4J_dbms_connector_bolt_advertised__address=:7687
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_dbms_mode=CORE
deploy:
mode: global
endpoint_mode: dnsrr
placement:
constraints:
- node.labels.neodb == 2
networks:
- neonet
neo-3:
image: neo4j:3.3.4-enterprise
volumes:
- neo-data:/data
- neo-logs:/var/lib/neo4j/logs
environment:
- NEO4J_AUTH=neo4j/blah
- NEO4J_causalClustering_discoveryAdvertisedAddress=neo-3:5000
- NEO4J_causalClustering_transactionAdvertisedAddress=neo-3:6000
- NEO4J_causalClustering_raftAdvertisedAddress=neo-3:7000
- NEO4J_causalClustering_expectedCoreClusterSize=3
- NEO4J_causalClustering_initialDiscoveryMembers=neo-1:5000,neo-2:5000,neo-3:5000
- NEO4J_dbms_connectors_default__advertised__address=neo-3
- NEO4J_dbms_connector_bolt_advertised__address=:7687
- NEO4J_ACCEPT_LICENSE_AGREEMENT=yes
- NEO4J_dbms_mode=CORE
deploy:
mode: global
endpoint_mode: dnsrr
placement:
constraints:
- node.labels.neodb == 3
networks:
- neonet
networks:
neonet:
driver: overlay
volumes:
neo-data:
neo-logs:
我很确定这太冗长了;到目前为止，可能只允许声明一个服务（具有多个副本）的解决方案。