Pivotal Knowledge Base

Follow

Native Client disable-shuffling-of-endpoints

Applies to

All versions of GemFire Native Client

Purpose

The purpose of this article is to describe how the value of the pool property, 'disable-shuffling-of-endpoints', affects how GemFire Native Client creates connections to servers.

Description

The property disable-shuffling-of-endpoints is a Native Client pool property by which we can specify how clients connect to servers. This parameter is only applicable when using a static server host and port list in the connection pool and is not applicable when the connection pool is configured with a list of locators.

This property interacts with the 'pr-single-hop-enabled' property and the actual connection behavior will fall into one of the following cases:

  • If disable-shuffling-of-endpoints is set to true and pr-single-hop-enabled is false, Native Client will always try to connect the first server in the server list.
    - Setting static server list with <server host=... port=... />
    - Setting pr-single-hop-enabled = "false"
    - Setting disable-shuffling-of-endpoints = "true"
    
  • In the case where disable-shuffling-of-endpoints and pr-single-hop-enabled are both set to true, Native Client tries to connect to a server on which the target bucket exists in order to realize single-hop access. Hence, the Native Client application may not necessarily connect to the first server in the server list.
    - Setting static server list with <server host=... port=... />
    - Setting pr-single-hop-enabled = "true"
    - Setting disable-shuffling-of-endpoints = "true"
    
  • Finally, if 'disable-shuffling-of-endpoints' is set to false (default), Native Client tries to connect to a server in the server list at random regardless of the value of  pr-single-hop-enabled.
    - Setting static server list with <server host=... port=... />
    - Setting pr-single-hop-enabled = "true" or "false"
    - Setting disable-shuffling-of-endpoints = "false"
    

Comments

Powered by Zendesk