openfire Hazelcast插件集群配置

2022-04-12 00:00:00 节点 设置 配置 标签 值为

注意虽然hazelcast 官方已经有了3.5.2版本，但是openfire的hazelcast插件新版却不是3.5.2，如果需要在openfire中使用hazelcast的新版，请前往http://www.igniterealtime.org/projects/openfire/plugins.jsp下载 
本人撰写本文的时候openfire的hazelcast插件新版为2.1.2，2015年9月16号更新，已经是新版本了。

Hazelcast Clusters集群配置

主要有以下三种方式

种、Discovering Members by Multicast（通过组播自动发现节点）

With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, they just multicast to all the other members for listening. It depends on your environment if multicast is possible or allowed.

官方给的示例

<network>
    <join>
        <multicast enabled="true">
            <multicast-group>224.2.2.3</multicast-group>
            <multicast-port>54327</multicast-port>
            <multicast-time-to-live>32</multicast-time-to-live>
            <multicast-timeout-seconds>2</multicast-timeout-seconds>
            <trusted-interfaces>
               <interface>192.168.1.102</interface>
            </trusted-interfaces>   
        </multicast>
        <tcp-ip enabled="false">
        </tcp-ip>
        <aws enabled="false">
        </aws>
    </join>
<network>

这个配置并不全面，实际工作配置中，< network>标签中还有其它子标签，而官方给的< join>标签是一个完整的配置，所以如果采用这种配置，请直接拷贝< join>标签。

如果需要使用multicast

首先，设置multicast标签为true

其次，设置multicast-group, multicast-port, multicast-time-to-live,等标签（实际工作中只设置了multicast-group和multicast-port标签，我使用的版本为2.1.2）

后，设置tcp-ip和aws标签为false

我的配置如下（openfire hazelcast 2.1.2）

 <join>
        <multicast enabled="true">
            <multicast-group>224.2.2.3</multicast-group>
            <multicast-port>54327</multicast-port>
        </multicast>
        <tcp-ip enabled="false"/>
        <aws enabled="false"/>
 </join>

官方解释

multicast element 
The multicast element includes parameters to fine tune the multicast join mechanism.

  1. enabled: Specifies whether the multicast discovery is enabled or not, true or false.
  2. multicast-group: The multicast group IP address. Specify it when you want to create clusters within the same network. Values can be between 224.0.0.0 and 239.255.255.255. Default value is 224.2.2.3.
  3. multicast-port: The multicast socket port that the Hazelcast member listens to and sends discovery messages through. Default value is 54327.
  4. multicast-time-to-live: Time-to-live value for multicast packets sent out to control the scope of multicasts. See more information here.
  5. multicast-timeout-seconds: Only when the nodes are starting up, this timeout (in seconds) specifies the period during which a node waits for a multicast response from another node. For example, if you set it as 60 seconds, each node will wait for 60 seconds until a leader node is selected. Its default value is 2 seconds.
  6. trusted-interfaces: Includes IP addresses of trusted members. When a node wants to join to the cluster, its join request will be rejected if it is not a trusted member. You can give an IP addresses range using the wildcard () on the last digit of IP address (e.g. 192.168.1. or 192.168.1.100-110).

下面解释一下< multicast>这个标签

  1. enabled: 设置是否启用multicast自动发现机制取值为true或false.
  2. multicast-group: multicast组播ip地址.设置该属性为在同一个局域网里做集群的时候用。取值范围为224.0.0.0 到 239.255.255.255之间，默认值为224.2.2.3
  3. multicast-port:multicast 套接字端口作为Hazelcast节点监听和发送消息使用，默认端口号54327
  4. multicast-time-to-live: Time-to-live 用来设置multicast包的生存时间（和路由器的差不多）
  5. multicast-timeout-seconds: 只有当节点启动的时候，用来设置节点等待multicast从另一个节点的响应时间。举例来说，如果设置该值为60s，每个节点都回等待60s直到一个主节点被选举出，默认值为2s（该值不宜太大，也不应太小）
  6. trusted-interfaces: 将信任的IP地址包含进来。当一个节点想要加入集群的时候如果它不在被信任节点中，它的加入请求会被拒绝，可以设置一个IP地址段（如192.168.1.* or 192.168.1.100-110）

第二种、Discovering Members by TCP（通过组TCP发现节点）

If multicast is not the preferred way of discovery for your environment, then you can configure Hazelcast to be a full TCP/IP cluster. When you configure Hazelcast to discover members by TCP/IP, you must list all or a subset of the members’ hostnames and/or IP addresses as cluster members. You do not have to list all of these cluster members, but at least one of the listed members has to be active in the cluster when a new member joins.

官方给的示例

<network>
    ...
    <join>
        <multicast enabled="false">
        </multicast>
        <tcp-ip enabled="true">
            <member>machine1</member>
            <member>machine2</member>
            <member>machine3:5799</member>
            <member>192.168.1.0-7</member>
            <member>192.168.1.21</member>
        </tcp-ip>
        ...
    </join>
    ...
</network>

如果需要使用TCP

首先，设置multicast和aws标签为false

其次，设置tcp-ip标签为ture

后，使用member标签将节点添加到tcp-ip中（注意：很早以前的版本使用的是标签式hostname）

官方解释

The tcp-ip element includes parameters to fine tune the TCP/IP join mechanism.

  1. enabled: Specifies whether the TCP/IP discovery is enabled or not. Values can be true or false.
  2. required-member: IP address of the required member. Cluster will only formed if the member with this IP address is found.
  3. member: IP address(es) of one or more well known members. Once members are connected to these well known ones, all member addresses will be communicated with each other. You can also give comma separated IP addresses using the members element.

下面解释一下tcp-ip 
tcp-ip标签使用以下标签来设置使用TCP/IP 做集群的加入机制

  1. enabled: 使TCP/IP生效，取值为true或false
  2. required-members: 节点的IP地址范围
  3. member：IP地址，需要一个一个添加

如果不提供端口，Hazelcast会自动尝试使用5701,5702等等，从5701递增

我的配置如下（openfire hazelcast 2.1.2）

<join>
    <multicast enabled="false">
        <multicast-group>224.2.2.3</multicast-group>
        <multicast-port>54327</multicast-port>
    </multicast>
    <tcp-ip enabled="true">
        <member>172.16.181.73:5701</member>
        <member>172.16.181.74:5701</member>
        <member>172.16.181.75:5701</member>
        <member>172.16.181.76:5701</member>
    </tcp-ip>
    <aws enabled="false"/>
</join>

除了使用上述配置还可以使用地址区间配置如下(注意，members中配置至少两个)

<join>
    <multicast enabled="false">
    </multicast>
    <tcp-ip enabled="true">
        <members>172.16.181.73-75,172.16.181.76</members>
    </tcp-ip>
    <aws enabled="false"/>
</join>

相关文章