The reason the make Reservation needs to be in the sync block is to prevent 
this bug:
if makeReservation thread passed the sync check, and before the lock is being 
hold in makeReservation, there is a possibility that the memberDeparted event 
occurs and release all existing dlockbatch from the departed member. Otherwise 
the lock will be held and no threads to clean it up.

[ Full content available at: https://github.com/apache/geode/pull/3176 ]
This message was relayed via gitbox.apache.org for 
[email protected]

Reply via email to