Hi Wenxing, Global scope type has been deprecated. Can you please describe your scenario? From what I have seen, creating a region as REPLICATE and then performing a transaction should give better performance. There is also a DistributedLockService <http://geode.apache.org/releases/latest/javadoc/org/apache/geode/distributed/DistributedLockService.html> in Geode that may be of help.
For transactions on partitioned regions, you have to ensure data colocation <http://geode.apache.org/docs/guide/16/developing/transactions/data_location_cache_transactions.html> . On Fri, Jun 8, 2018 at 6:56 AM wenxing zheng <[email protected]> wrote: > Sorry to append another question: > How to embed an update on the partitioned region in a transaction? > > As I met with the exception with TransactionDataRebalancedException. > > Thanks again, Wenxing > > On Fri, Jun 8, 2018 at 5:55 PM, wenxing zheng <[email protected]> > wrote: > >> Dear experts, >> >> I have met with a question related with transaction on GEODE version: >> 1.8.0-SNAPSHOT. How to get the distributed lock with >> Region.getDistributedLock as it seemed only support on GLOBAL scope type. >> But from the gfsh or the API, we have no chance to create the region with >> GLOBAL type since "as of 6.5 use >> Cache.createRegionFactory(RegionShortcut) >> <http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/Cache.html#createRegionFactory-org.apache.geode.cache.RegionShortcut-> >> ". >> >> From the RegionShortcut definition, I can't find any descriptions related >> with the GLOBAL scope type. >> >> Please help to shed some lights. >> Thanks, Wenxing >> > >
