LATEST VERSION: 9.5.1 - RELEASE NOTES
Pivotal GemFire® v9.5

Custom-Partitioning and Colocating Data

You can customize how Pivotal GemFire groups your partitioned region data with custom partitioning and data colocation.

  • Understanding Custom Partitioning and Data Colocation

    Custom partitioning and data colocation can be used separately or in conjunction with one another.

  • Standard Custom Partitioning

    By default, GemFire partitions each data entry into a bucket using a hashing policy on the key. Additionally, the physical location of the key-value pair is abstracted away from the application. You can change these policies for a partitioned region by providing a standard partition resolver that maps entries to a set of buckets called a partition.

  • Fixed Custom Partitioning

    By default, GemFire partitions each data entry into a bucket using a hashing policy on the key. Additionally, the physical location of the key-value pair is abstracted away from the application. You can change these policies for a partitioned region by providing a fixed partition resolver that not only maps entries to a set of buckets called a partition, but also specifies which members host which data buckets.

  • Colocate Data from Different Partitioned Regions

    By default, GemFire allocates the data locations for a partitioned region independent of the data locations for any other partitioned region. You can change this policy for any group of partitioned regions, so that cross-region, related data is all hosted by the same member. Colocation is required for some operations, and it increases performance for others by reducing the number of data accesses to entries that are hosted on other cluster members.