Kubernetes的Hazelcast集群中的裂脑发现

问题描述 投票:0回答:1

我有以下设置。

我的Vert.x Verticle与Hazelcast聚类,并部署在Kubernetes集群上,其中包含以下网络信息:

------------------------------------------------
           TCP/IP NETWORK INFORMATION
------------------------------------------------
IP Entered = ..................: 10.60.0.0
CIDR = ........................: /14
Netmask = .....................: 255.252.0.0
Netmask (hex) = ...............: 0xfffc0000
Wildcard Bits = ...............: 0.3.255.255
------------------------------------------------
Network Address = .............: 10.60.0.0
Broadcast Address = ...........: 10.63.255.255
Usable IP Addresses = .........: 262,142
First Usable IP Address = .....: 10.60.0.1
Last Usable IP Address = ......: 10.63.255.254

Hazelcast的cluster.xml有以下部分:

<join>
  <multicast enabled="true">
    <multicast-group>224.2.2.3</multicast-group>
    <multicast-port>54327</multicast-port>
  </multicast>
</join>

一切似乎都很好。当我在pods中启动Verticle时,我得到输出(缩写):

>kubectl get pods --namespace develop -o wide

READY   STATUS    RESTARTS   AGE   IP        
1/1     Running   0          52m   10.60.4.18
1/1     Running   0          4m    10.60.6.19
1/1     Running   0          4m    10.60.1.16
1/1     Running   0          4m    10.60.1.18
1/1     Running   0          4m    10.60.6.18  
1/1     Running   0          4m    10.60.1.17
1/1     Running   0          4m    10.60.4.23
1/1     Running   0          8m    10.60.6.17
1/1     Running   0          4m    10.60.4.22
1/1     Running   0          4m    10.60.4.21
1/1     Running   0          4m    10.60.6.20
1/1     Running   0          5d    10.60.4.9 

问题是,群集不是由指定的组名分组,而是由第3个ip地址组分组。所以,我得到了一个群集:

                      masterAddress=[10.60.1.17]:5701
                      Members[
                              [10.60.1.17]:5701
                              [10.60.1.16]:5701
                              [10.60.1.18]:5701]]

然后5名成员为“集群”10.60.4.*,4名成员为10.60.6.*等等他们没有合并......

我错过了什么?

TIA

kubernetes hazelcast multicast vert.x
1个回答
1
投票

Hazelcast有一个专门用于Kubernetes发现的插件。请检查:hazelcast-kubernetes

Mutlicast可能有效,也可能无效,因为它取决于底层网络。根据我在GKE上的经验,它有时会起作用,有时则不然。这就是Kubernetes从不推荐基于组播的发现的原因。

资源:

© www.soinside.com 2019 - 2024. All rights reserved.