I think you are seeing the proper behavior. Does FULL_ASYNC mode provide a put future that you can wait on?
On Wed, Apr 20, 2016 at 12:31 PM, Alexei Scherbakov < [email protected]> wrote: > Hello, > > I tried the following: > Started two server nodes. > Created a cache in ATOMIC, REPLICATED, FULL_ASYNC modes > From the client deployed a service on backup node for that cache. > In the service I executed the code: > put(key, val); // val is not null > V v = get(key); > and got v equal to null (not suprising) > But javadoc for FULL_ASYNC mode states: > "remote nodes may get their state updated a bit after any of the cache > write methods complete" > From the user point of view this update is local, so it might be confusing. > Should we do anything about it? > > > -- > > Best regards, > Alexei Scherbakov >
