Apache Geode

Socket Communication

Geode processes communicate using TCP/IP and UDP unicast and multicast protocols. In all cases, communication uses sockets that you can tune to optimize performance.

The adjustments you make to tune your Geode communication may run up against operating system limits. If this happens, check with your system administrator about adjusting the operating system settings.

All of the settings discussed here are listed as gemfire.properties and cache.xml settings. They can also be configured through the API and some can be configured at the command line. Before you begin, you should understand Geode Basic Configuration and Programming.

• Setting Socket Buffer Sizes

  When you determine buffer size settings, you try to strike a balance between communication needs and other processing.

• Ephemeral TCP Port Limits

  By default, Windows’ ephemeral ports are within the range 1024-4999, inclusive.You can increase the range.

• Making Sure You Have Enough Sockets

  The number of sockets available to your applications is governed by operating system limits.

• TCP/IP KeepAlive Configuration

  Geode supports TCP KeepAlive to prevent socket connections from being timed out.

• TCP/IP Peer-to-Peer Handshake Timeouts

  You can alleviate connection handshake timeouts for TCP/IP connections by increasing the connection handshake timeout interval with the system property p2p.handshakeTimeoutMs.