How is this safe if another member is modifying the same PartitionRegionConfig concurrently? prRoot is a distributed region and two or more members could try to modify the PartitionRegionConfig for the same region identifier. Do we have some locking somewhere to prevent concurrent mutators? In our case we could have sent multiple servers the CreateMappingFunction and they might both be concurrently mutating the region. Seems like we need the prRoot.get and prRoot.put to be done atomically to be safe. Also consider using updatePRConfig instead of just calling put. Dan Smith might know more about this code and how to update the node information safely.
[ Full content available at: https://github.com/apache/geode/pull/3308 ] This message was relayed via gitbox.apache.org for [email protected]
