| --- |
| title: Partitioned Regions |
| --- |
| |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| |
| In addition to basic region management, partitioned regions include options for high availability, data location control, and data balancing across the cluster. |
| |
| - **[Understanding Partitioning](how_partitioning_works.html)** |
| |
| To use partitioned regions, you should understand how they work and your options for managing them. |
| |
| - **[Configuring Partitioned Regions](managing_partitioned_regions.html)** |
| |
| Plan the configuration and ongoing management of your partitioned region for host and accessor members and configure the regions for startup. |
| |
| - **[Configuring the Number of Buckets for a Partitioned Region](configuring_bucket_for_pr.html)** |
| |
| Decide how many buckets to assign to your partitioned region and set the configuration accordingly. |
| |
| - **[Custom-Partitioning and Colocating Data](overview_custom_partitioning_and_data_colocation.html)** |
| |
| You can customize how <%=vars.product_name_long%> groups your partitioned region data with custom partitioning and data colocation. |
| |
| - **[Configuring High Availability for Partitioned Regions](overview_how_pr_ha_works.html)** |
| |
| By default, <%=vars.product_name_long%> stores only a single copy of your partitioned region data among the region's data stores. You can configure <%=vars.product_name%> to maintain redundant copies of your partitioned region data for high availability. |
| |
| - **[Configuring Single-Hop Client Access to Server-Partitioned Regions](overview_how_pr_single_hop_works.html)** |
| |
| 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. |
| |
| - **[Rebalancing Partitioned Region Data](rebalancing_pr_data.html)** |
| |
| In a cluster 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. |
| |
| - **[Checking Redundancy in Partitioned Regions](checking_region_redundancy.html)** |
| |
| 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. |
| |
| - **[Moving Partitioned Region Data to Another Member](moving_partitioned_data.html)** |
| |
| You can use the `PartitionRegionHelper` `moveBucketByKey` and `moveData` methods to explicitly move partitioned region data from one member to another. |
| |
| |