this "removeNode" call scares me. It seems like it could cause intermittent concurrency issues. Until "prConfig.addNode" is called this node is no longer in the list. Note that other threads in this same jvm would be getting the same prConfig instance from the prRoot region. Other members will not see our changes until we do the put. It might be better to create a copy of the PartitionedRegionConfig (see getPRConfigWithLatestExpirationAttributes for an example) but you will need to copy the nodes.
[ Full content available at: https://github.com/apache/geode/pull/3308 ] This message was relayed via gitbox.apache.org for [email protected]
