This topic explains how to configure high availability for a partitioned regions in VMware Tanzu GemFire.
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.
Decide how to manage redundancy recovery and change Tanzu GemFire’s default behavior as needed.
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_RECOVERIES
system property to increase or decrease the maximum number of buckets to recover in parallel any time redundancy recovery is performed.
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.
Set the Number of Redundant Copies
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.
Configure Redundancy Zones for Members
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 Member Crash Redundancy Recovery for a Partitioned Region
Configure whether and how redundancy is recovered in a partition region after a member crashes.
Configure Member Join Redundancy Recovery for a Partitioned Region
Configure whether and how redundancy is recovered in a partition region after a member joins.