I'm not quite sure this is relevant to your issue.
I've experienced the hanging issue on ignite 1.8.0 when topology changed.
https://issues.apache.org/jira/browse/IGNITE-4450 might get to fix the
problem.
FYR.
2017-03-16 1:03 GMT+08:00 bintisepaha :
> Andrey, do you think topology changes with c
I have considered using AtomicLong as well. But the main reason to
introduce ignite lock is becuase the increaseAndGet() method should only be
called after all the policies are allowed.
Here is an example, when a message is allowed by Policy A(100 messages per
user per day), but blocked by policy
this is the right way to use Ignite, or there are better
solutions?
Best,
Evans Ye
