In addition to basic region management, partitioned regions include options for high availability, data location control, and data balancing across the distributed system.
To use partitioned regions, you should understand how they work and your options for managing them.
Plan the configuration and ongoing management of your partitioned region for host and accessor members and configure the regions for startup.
Decide how many buckets to assign to your partitioned region and set the configuration accordingly.
You can customize how Pivotal GemFire groups your partitioned region data with custom partitioning and data colocation.
By default, Pivotal GemFire stores only a single copy of your partitioned region data among the region’s data stores. You can configure GemFire to maintain redundant copies of your partitioned region data for high availability.
Single-hop data access enables the client pool to track where a partitioned region’s data is hosted in the servers. To access a single entry, the client directly contacts the server that hosts the key, in a single hop.
In a distributed system with minimal contention to the concurrent threads reading or updating from the members, you can use rebalancing to dynamically increase or decrease your data and processing capacity.
Under some circumstances, it can be important to verify that your partitioned region data is redundant and that upon member restart, redundancy has been recovered properly across partitioned region members.
You can use the
moveDatamethods to explicitly move partitioned region data from one member to another.