I just read this, about hudi, and I can't see a use case for putting hudi
behind an Ignite write-through cache.
https://www.xenonstack.com/insights/what-is-hudi
Hudi seems to be a write accelerator for Spark on HDFS, primarily.
What would the expected outcome be if we assume the magic
Perfect, thanks a lot. I get it now!
On 15.09.22 12:33, Stephen Darlington wrote:
Ignite locks /rows/ not /caches/, so no, that would not cause a deadlock.
This could cause a deadlock:
First:
#1 tx.start();
#2 cacheA.put(1, 1);
#3 cacheB.put(2, 2);
#4 tx.commit();
Second:
#5 tx.start();
Ignite locks rows not caches, so no, that would not cause a deadlock.
This could cause a deadlock:
First:
#1 tx.start();
#2 cacheA.put(1, 1);
#3 cacheB.put(2, 2);
#4 tx.commit();
Second:
#5 tx.start();
#6 cacheB.put(2, 2);
#7 cacheA.put(1, 1);
#8 tx.commit();
Both these operations can be
Modifying previous example. Would this still potentially result in
deadlock?
First:
#1 tx.start();
#2 cacheA.put(1, 1);
#3 cacheB.put(2, 2);
#4 tx.commit();
Second:
#5 tx.start();
#6 cacheB.put(1, 1);
#7 cacheA.put(2, 2);
#8 tx.commit();
Ignite locks cacheA on line #2 in first thread. In
The important part is that they’re both waiting for each other to complete.
Whether it’s one cache or ten is not significant.
> On 14 Sep 2022, at 12:44, Thomas Kramer wrote:
>
> OK, that makes sense. However, in my logs below the deadlock says it's in two
> different caches. How does this
