LATEST VERSION: 8.1.0 - CHANGELOG
Pivotal GemFire® v8.1

Data Location for Cache Transactions

Data Location for Cache Transactions

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

Transactions must be run on a data set 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 co-locate all your transactional data in a single member.
  • For transactions run on partitioned and distributed region mixes, you must co-locate 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 run the transactional application, regardless of whether the 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 transactional data host.