In general this seems wrong. I think something has gone wrong at a higher level if we have proxies here. We should not even have executed this function on this member. Why would we still create the async queue on a proxy member? We check for cluster config first thing to see if we can create the mapping on the region back in CreateRegionCommand. Seems like we should have checked their if it was a proxy region. If it is then we fail. Otherwise when we ask for all the members using that cluster config (either the cluster wide one or the group) shouldn't they all have the region as configured in the cluster config? Then at this point it could not even be a proxy. If you are using cluster config (which create jdbc-mapping requires) then don't you need to put the proxy definition in a separate group? So how are we even executing this function on servers that have a proxy? I think the fix should be in CreateMappingCommand before we call any function
[ Full content available at: https://github.com/apache/geode/pull/3309 ] This message was relayed via gitbox.apache.org for [email protected]
