LATEST VERSION: 9.1.1 - CHANGELOG
Pivotal GemFire® v9.1

Data Location for Cache Transactions

The location where you can run your transaction depends on where you are storing your data.

Transactions must operate on a data set that is hosted entirely by one member.

  • For replicated or other distributed regions, the transaction uses only the data set in the member where the transaction is run.
  • For partitioned regions, you must colocate all your transactional data in a single member. See Colocate Data from Different Partitioned Regions.
  • For transactions run on partitioned and distributed region mixes, you must colocate the partitioned region data and make sure the distributed region data is available in any member hosting the partitioned region data.

For transactions involving partitioned regions, any member with the regions defined can orchestrate the transactional operations, regardless of whether that member hosts data for the regions. If the transactional data resides on a remote member, the transaction is carried out by proxy in the member hosting the data. The member hosting the data is referred to as the transaction host.

The first operation determines and sets the transaction host for any transactions involving partitioned regions. Therefore, in a system that colocates data, the first operation must be to the host with the colocated data, such that the transaction host is the one with the colocated data. The first operation must not be to a replicated region, as any member might become the transaction host. If the wrong member becomes the transaction host, accesses of partitioned region data will result in an exception.