Docker部署Cassandra集群添加第4节点时节点崩溃求助

我尝试用Docker部署Apache Cassandra集群，通过命令docker run --network cassandra -e CASSANDRA_ENDPOINT_SNITCH=GossipingPropertyFileSnitch -e CASSANDRA_SEEDS=node0 --name "node0" -d cassandra成功搭建了最多3节点的集群。但每次用相同命令（仅修改容器名）添加第4个节点时，集群里会随机有一个现有节点崩溃，新节点进入UJ（上线-加入）和DJ（下线-加入）状态后很快就退出。

操作步骤 #

• 创建Docker网络：docker network create cassandra
• 启动node0节点，等待上线后，执行nodetool status得到输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
UN  172.19.0.2  88.49 KiB  16      100.0%            15573541-fc19-4569-9a43-cb04e49e134f  rack1

• 添加node1和node2节点，等待它们加入集群后，nodetool status输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
UN  172.19.0.2  74.11 KiB  16      64.7%             15573541-fc19-4569-9a43-cb04e49e134f  rack1
UN  172.19.0.4  98.4 KiB   16      76.0%             30afdc85-e863-452c-9031-59803e4b1f11  rack1
UN  172.19.0.3  74.04 KiB  16      59.3%             6d92cf62-65b4-4365-ab28-2d53872605e3  rack1

添加第4节点后的异常情况 #

执行命令添加node3：docker run --network cassandra -e CASSANDRA_ENDPOINT_SNITCH=GossipingPropertyFileSnitch -e CASSANDRA_SEEDS=node0 --name "node3" -d cassandra

此时node1立即崩溃，node3短暂处于UJ状态后转为DJ，随后从节点列表中移除。

nodetool status的顺序输出： #

第一步输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
UN  172.19.0.2  74.11 KiB  16      64.7%             15573541-fc19-4569-9a43-cb04e49e134f  rack1
UN  172.19.0.4  74.03 KiB  16      76.0%             30afdc85-e863-452c-9031-59803e4b1f11  rack1
DN  172.19.0.3  74.04 KiB  16      59.3%             6d92cf62-65b4-4365-ab28-2d53872605e3  rack1

第二步输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
UJ  172.19.0.5  20.75 KiB  16      ?                 2e4a25e4-3c81-4383-9c9f-6326e4043910  rack1
UN  172.19.0.2  74.11 KiB  16      64.7%             15573541-fc19-4569-9a43-cb04e49e134f  rack1
UN  172.19.0.4  74.03 KiB  16      76.0%             30afdc85-e863-452c-9031-59803e4b1f11  rack1
DN  172.19.0.3  74.04 KiB  16      59.3%             6d92cf62-65b4-4365-ab28-2d53872605e3  rack1

第三步输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
DJ  172.19.0.5  20.75 KiB  16      ?                 2e4a25e4-3c81-4383-9c9f-6326e4043910  rack1
UN  172.19.0.2  74.11 KiB  16      64.7%             15573541-fc19-4569-9a43-cb04e49e134f  rack1
UN  172.19.0.4  74.03 KiB  16      76.0%             30afdc85-e863-452c-9031-59803e4b1f11  rack1
DN  172.19.0.3  74.04 KiB  16      59.3%             6d92cf62-65b4-4365-ab28-2d53872605e3  rack1

第四步输出：

Datacenter: dc1
===============
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address     Load       Tokens  Owns (effective)  Host ID                               Rack 
UN  172.19.0.2  74.11 KiB  16      64.7%             15573541-fc19-4569-9a43-cb04e49e134f  rack1
UN  172.19.0.4  74.03 KiB  16      76.0%             30afdc85-e863-452c-9031-59803e4b1f11  rack1
DN  172.19.0.3  74.04 KiB  16      59.3%             6d92cf62-65b4-4365-ab28-2d53872605e3  rack1

相关日志 #

• node1崩溃日志
• node3退出日志

内容的提问来源于stack exchange，提问作者janic0