Ivan, My suggestion "withFairAsync()". What do you think?
On Fri, May 11, 2018 at 6:23 PM, Ivan Rakov <[email protected]> wrote: > I think, the best option from API side is to add decorating > withExplicitAsync() method. > We already have withKeepBinary, withExpiryPolicy and so on. > > Best Regards, > Ivan Rakov > > > On 11.05.2018 18:18, Dmitriy Govorukhin wrote: > >> Vladimir, >> >> Should we create the new cache adapter or rework GridCacheAdapter? >> >> On Fri, May 11, 2018 at 5:52 PM, Vladimir Ozerov <[email protected]> >> wrote: >> >> +1 >>> >>> This would also be helpful for transactional SQL as it would allow to >>> hide >>> network latency. But there is a problem - deadlocks. We need to inform >>> user >>> that this mode should be used with great care. >>> >>> On Fri, May 11, 2018 at 5:21 PM, Dmitriy Govorukhin < >>> [email protected]> wrote: >>> >>> Hi Igniters, >>>> >>>> I have a question. Why our async operation in not really async? >>>> >>>> GridCacheAdapter.syncOp has awaitLastFut(); this call wait last async >>>> operation completed. >>>> >>>> This means all async operation in one thread will be executed one by one >>>> but not in parallel. Async operation is not async. >>>> >>>> Example for atomic cache >>>> >>>> f1=cache.getAsync(key1); >>>> f2=cache.getAsync(key2); >>>> >>>> f1 always will be complete before f2. >>>> >>>> I want to have the ability run multiple async operations in one thread. >>>> What do you think? >>>> >>>> Maybe we can add new cache adapter with fair async operations? >>>> >>>> >
