LATEST VERSION: 8.2.7 - CHANGELOG
Pivotal GemFire® v8.2

Configuring Peer-to-Peer Discovery

Configuring Peer-to-Peer Discovery

By default, GemFire uses multicast for peer discovery. You can change the configuration to separate distributed systems and provide greater flexibility in member discovery.

Before you begin, you should have a basic understanding of member discovery. You should also have already determined the address and port settings for member discovery. See Topology and Communication General Concepts.

These options are set through GemFire properties. See gemfire.properties and gfsecurity.properties (GemFire Properties).
  • To use multicast for membership, in the gemfire.properties for all system peers, provide the multicast address and port and disable locators for peer discovery:
    locators=
    mcast-address=<mcast address>
    mcast-port=<mcast port>
  • To use locators for membership, in the gemfire.properties of all system peers, including the locators, provide the locator list:
    locators=<locator1-address>[<port1>],<locator2-address>[<port2>]
    By default, locators provide peer discovery in the system in which they run, so no special settings are required to enable it when you start them. See Running GemFire Locator Processes.
  • To run a standalone member, in the gemfire.properties disable multicasting and locators:
    locators=
    mcast-address=                    
    mcast-port=0
Note: Multicast and locator settings must be consistent throughout the distributed system.