You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rmap.addAndGetAsync (and any *Async methonds) - as i understand it shouldn't lock the calling thread, and return value (Future) as soon as possible.
But if for any reason connection is not established yet the calling thread will be blocked.
And if redis server is not available at all it will be blocked for very long period of time.
Maybe i'm wrong but it doesn't look like async nor lock-free.
The text was updated successfully, but these errors were encountered:
You are right. Connection should be established in async too. But as i wrote the underlying Redis client used by Redisson is fully async and lock-free not the Redisson whole
Yes, RBatch allows me to queue updates without blocking.
But as soon as i try to execute them (RBatch#executeAsync) the same situation will happens again: the calling thread will be blocked till connection is established or till it fails to connect.
Rmap.addAndGetAsync (and any *Async methonds) - as i understand it shouldn't lock the calling thread, and return value (Future) as soon as possible.
But if for any reason connection is not established yet the calling thread will be blocked.
And if redis server is not available at all it will be blocked for very long period of time.
Maybe i'm wrong but it doesn't look like async nor lock-free.
The text was updated successfully, but these errors were encountered: