Isolating JBoss EAP 6 clusters running on the same network


 SOLUTION VERIFIED - Updated October 27 2016 at 12:47 PM - 

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Issue

  • What config changes are required to isolate clusters on the same network?
  • I need to start JBoss so it doesn't join an existing cluster.
  • Is there a way that the clusters can be segregated in JBoss from seeing the incorrect nodes?
  • Is there configuration in Jboss that will specify the nodes that are in the cluster?
  • How do we start X separate clusters within the same environment?
  • How can one avoid cluster crosstalk in EAP 6?
  • In order to isolate the cluster, Is it required to use different multicast addresses for the JBoss nodes?
  • How to prevent a cluster node on laptop A connects to a clusternode on laptop B?

Resolution

When using the default multicast/UDP clustering configuration, specify a unique multicast address for each cluster.

  • If using TCP and TCPPING for all cluster channels, then setting the multicast address is not necessary because the TCPPING.initial_hosts configuration controls the cluster membership.

  • Multicast addresses are in the range 224.0.0.0 to 239.255.255.255.

    • 224.0.0.* are reserved for specific purposes and shouldn't be used. Other ranges are reserved for particular scopes (how far on the network the messages can travel).
    • If you're not sure what addresses to use, check with your network administrators if they have any particular IPs or ranges they'd like you to use.
  • The multicast IPs and ports are configured by the following socket bindings (note that messaging is only enabled by default in some profiles). These are usually configured by setting the listed system properties.

    Raw
    <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
    
    <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
    

Standalone Mode

  • Specify a unique multicast address for each cluster with "-u". This is shorthand syntax for setting the jboss.default.multicast.address system property.

    Raw
    ./standalone.sh -u 230.1.1.1 ...
    
  • If using HornetQ set the following property to the same value as -u:

    Raw
    -Djboss.messaging.group.address=...
    

    for nodes belonging to the same hornetQ cluster

Domain Mode

Set the system properties for the server-group or individual servers.
For the most common use case where a server-group corresponds to a single cluster:

Raw
<server-group ...
    <system-properties>
        <property name="jboss.default.multicast.address" value="230.0.0.4"/>
        <property name="jboss.messaging.group.address" value="231.7.7.7"/>
        ...
    </system-properties>
翻译 There are several reasons a network designed on layer-2 protocols is selected over a network designed on layer-3 protocols. In spite of the difficulties of using a bridge to perform the network role of a router, many vendors, customers, and service providers choose to use Ethernet in as many parts of their networks as possible. The benefits of selecting a layer-2 design are: Ethernet frames contain all the essentials for networking. These include, but are not limited to, globally unique source addresses, globally unique destination addresses, and error control. Ethernet frames can carry any kind of packet. Networking at layer-2 is independent of the layer-3 protocol. Adding more layers to the Ethernet frame only slows the networking process down. This is known as nodal processing delay. You can add adjunct networking features, for example class of service (CoS) or multicasting, to Ethernet as readily as IP networks. VLANs are an easy mechanism for isolating networks. Most information starts and ends inside Ethernet frames. Today this applies to data, voice, and video. The concept is that the network will benefit more from the advantages of Ethernet if the transfer of information from a source to a destination is in the form of Ethernet frames. Although it is not a substitute for IP networking, networking at layer-2 can be a powerful adjunct to IP networking. Layer-2 Ethernet usage has additional benefits over layer-3 IP network usage: Speed Reduced overhead of the IP hierarchy. No need to keep track of address configuration as systems move around. Whereas the simplicity of layer-2 protocols might work well in a data center with hundreds of physical machines, cloud data centers have the additional burden of needing to keep track of all virtual machine addresses and networks. In these data centers, it is not uncommon for one physical node to support 30-40 instances.
07-23
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值