In invalidation mode we don't wait for the initial state transfer to finish, or even for the joiner to become a member in the "write" CH, before returning to the user from getCache().

Writes to the joiner before it becomes a member of the write CH are not committed to the local cache, because of a check in EntryWrappingInterceptor.shouldWrap(). So it's possible for the joiner to ignore the first write completely.

If StateTransferConfigurationBuilder enabled awaitInitialTransfer by default in invalidation mode, like it does in distributed/replicated mode, this wouldn't happen.

The fact that it will still be possible for the user to disable awaitInitialTransfer manually shouldn't be a problem, because in invalidation mode the user should expect values to be invalidated at any time. This is just about improving the default configuration.