Hi,
If lock will be resides on node that hold the lock, how newly joined node
will discover just locked lock instance by lock name to add itself in
waiting queue?
Who will be responsible for waiting queue handing? Does the queue should be
transferred when owner has changed?
And finally, how this w
Hi,Roman
Thank you for the reply.
I think i should change the value of cacheMode to replicated, it is more
safe.
why not cache the lock on the node who own the lock? If the node leaves
topology, it will has no effect on other nodes.
Thanks
--
Sent from: http://apache-ignite-users.70518.x
Hi,
Yes, you are right. Default backups count is zero by default. This way it is
possible to lose some locks if one of the nodes leaves topology.
You are able to set backups count in AtomicConfiguration:
...
Hi
I want to use reentrantLock of ignite.
In the code, the default backups is zero in AtomicConfiguration.
When a node leaves topology, some locks cached on this node will lost?
Should i modify the configuration of atomicConfiguration?
Thanks
--
Sent from: http://apache-ignite-users.70518
Hi, could you please describe in more details what do you want to achieve?
If you want to aquire a distributed lock on some key you may use pessimistic
transaction with REPEATEABLE_READ isolation level [1] on transactional
cache.
[1]
https://apacheignite.readme.io/v1.7/docs/transactions
Hi
I need to apply distributed lock while storing some KV using my own
JobStore. Now I need to put the lock on the connected instances before
writing some records on a cache. A few line code example will be very
helpful to understand.
--
View this message in context:
http://apache-ignite-users
