LATEST VERSION: 9.2.0 - CHANGELOG
Pivotal GemFire® v9.2

Configuring Peer Communication

By default Pivotal GemFire uses TCP for communication between members of a single distributed system. You can modify this at the member and region levels.

Before you begin, you should have already determined the address and port settings for multicast, including any bind addresses. See Topology and Communication General Concepts.

See the Reference.

  1. Configure general messaging to use TCP or UDP unicast.

    TCP is the default protocol for communication. To use it, just make sure you do not have it disabled in gemfire.properties. Either have no entry for disable-tcp, or have this entry:

    disable-tcp=false
    

    To use UDP unicast for general messaging, add this entry to gemfire.properties:

    disable-tcp=true
    

    The disable-tcp setting has no effect on the use of TCP locators or the TCP connections used to detect failed members.

  2. Configure any regions you want to distribute using UDP multicast.

    1. Configure UDP multicast for region messaging, set non-default multicast address and port selections in gemfire.properties:

      mcast-address=<address>
      mcast-port=<port>
      
    2. In cache.xml, enable multicast for each region that needs multicast messaging:

      <region-attributes multicast-enabled="true"/> 
      

      Note: Improperly configured multicast can affect production systems. If you intend to use multicast on a shared network, work with your network administrator and system administrator from the planning stage of the project. In addition, you may need to address interrelated setup and tuning issues at the GemFire, operating system, and network level.

Once your members establish their connections to each other, they will send distributed data and messages according to your configuration.