Configure Client Single-Hop Access to Server-Partitioned Regions
Configure your client/server system for direct, single-hop access to partitioned region data in the servers.
This requires a client/server installation that uses one or more partitioned regions on the server.
Verify the client’s pool attribute,
pr-single-hop-enabledis not set or is set to true. It is true by default.
If possible, leave the pool’s
max-connectionsat the default unlimited setting (-1).
If possible, use a custom data resolver to partition your server region data according to your clients’ data use patterns. See Custom-Partition Your Region Data. Include the server’s partition resolver implementation in the client’s
CLASSPATH. The server passes the name of the resolver for each custom partitioned region, so the client uses the proper one. If the server does not use a partition resolver, the default partitioning between server and client matches, so single hop works.
Add single-hop considerations to your overall server load balancing plan. Single-hop uses data location rather than least loaded server to pick the servers for single-key operations. Poorly balanced single-hop data access can affect overall client/server load balancing. Some counterbalancing is done automatically because the servers with more single-key operations become more loaded and are less likely to be picked for other operations.