Folks,

Do we currently have any way to set a timeout for an atomic operation? I
don't see neither a way to do this nor any related documentation.

In the code there are CacheAtomicUpdateTimeoutException
and CacheAtomicUpdateTimeoutCheckedException, but I can't find a single
place where it's created and/or thrown. Looks like we used to have this
functionality, but it's not there anymore. Is this really the case or I
missed something?

I think having a way to timeout atomic operation is very important. For
example, two concurrent putAll operations with keys in different order can
completely hang the whole cluster forever, which is unacceptable. Is it
possible to timeout one of the operations (or both of them) in this case?

-Val

Reply via email to