So, I'm looking into an issue in which the Geode Server starts up and accepts connections from Clients and starts handling their requests before its Cache has completed initialization.
Regions have a series of initialization latches that local puts and gets are forced to wait on. For example, initializationLatchAfterGetInitialImage is released after GII completes for that Region. Local puts and gets are not allowed to be handled until after GII completes. I would expect the Cache to have an initialization latch as well that Client requests have to wait on before the Geode Server completes Cache initialization. Does anyone know why Cache or AcceptorImpl don't have an initialization latch like this? Does anyone have a good reason to not add such an initialization latch to protect incoming Client requests? Thanks, Kirk
