Configure High Availability for a Partitioned Region
Configure in-memory high availability for your partitioned region. Set other high-availability options, like redundancy zones and redundancy recovery strategies.
Here are the main steps for configuring high availability for a partitioned region. See later sections for details.
- Set the number of redundant copies the system should maintain of the region data. See Set the Number of Redundant Copies.
- (Optional) If you want to group your data store members into redundancy zones, configure them accordingly. See Configure Redundancy Zones for Members.
- (Optional) If you want Tanzu GemFire to only place redundant copies on different physical machines, configure for that. See Set Enforce Unique Host.
Decide how to manage redundancy recovery and change Tanzu GemFire’s default behavior as needed.
- After a member crashes. If you want automatic redundancy recovery, change the configuration for that. See Configure Member Crash Redundancy Recovery for a Partitioned Region.
- After a member joins. If you do not want immediate, automatic redundancy recovery, change the configuration for that. See Configure Member Join Redundancy Recovery for a Partitioned Region.
Decide how many buckets Tanzu GemFire should attempt to recover in parallel when performing redundancy recovery. By default, the system recovers up to 8 buckets in parallel. Use the
gemfire.MAX_PARALLEL_BUCKET_RECOVERIESsystem property to increase or decrease the maximum number of buckets to recover in parallel any time redundancy recovery is performed.
For all but fixed partitioned regions, review the points at which you kick off rebalancing. Redundancy recovery is done automatically at the start of any rebalancing. This is most important if you run with no automated recovery after member crashes or joins. See Rebalancing Partitioned Region Data.
For all partitioned regions, redundancy can be restored without moving buckets between members using a restore redundancy operation. See Restoring Redundancy in Partitioned Regions.
During runtime, you can add capacity by adding new members for the region. For regions that do not use fixed partitioning, you can also kick off a rebalancing operation to spread the region buckets among all members.
Configure in-memory high availability for your partitioned region by specifying the number of secondary copies you want to maintain in the region’s data stores.
Group members into redundancy zones so Tanzu GemFire will separate redundant data copies into different zones.
Configure Tanzu GemFire to use only unique physical machines for redundant copies of partitioned region data.
Configure whether and how redundancy is recovered in a partition region after a member crashes.
Configure whether and how redundancy is recovered in a partition region after a member joins.