Plan the configuration and ongoing management of your partitioned region for host and accessor members and configure the regions for startup.
Before you begin, understand Basic Configuration and Programming.
Start your region configuration using one of the
PARTITION region shortcut settings. See Region Shortcuts and Custom Named Region Attributes.
If you need high availability for your partitioned region, configure for that. See Configure High Availability for a Partitioned Region.
Estimate the amount of space needed for the region. If you use redundancy, this is the max for all primary and secondary copies stored in the member. For example, with redundancy of one, each region data entry requires twice the space than with no redundancy, because the entry is stored twice. See Memory Requirements for Cached Data.
Configure the total number of buckets for the region. This number must be the same for colocated regions. See Configuring the Number of Buckets for a Partitioned Region.
Configure your members' data storage and data loading for the region:
local-max-memory. This is the only setting in
partition-attributesthat can vary between members. Use these max values and your estimates for region memory requirements to help you figure how many members to start out with for the region.
local-max-memorygreater than 0), define a data loader. See Implement a Data Loader.
local-max-memoryset to 0), review your system startup/shutdown procedures. Make sure there is always at least one member with local data storage running when any members with no storage are running.
If you want to custom partition the data in your region or colocate data between multiple regions, code and configure accordingly. See Understanding Custom Partitioning and Data Colocation.
Plan your partition rebalancing strategy and configure and program for that. See Rebalancing Partitioned Region Data.
Note: To configure a partitioned region using gfsh, see gfsh Command Help.