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
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
It is not a error.
You can set 'metricsLogFrequency' to 0.
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setMetricsLogFrequency(0L)
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
Can you show your solution? I am very upset about this.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I am a new user of Ignite.
I have used Hazelcast before, if i set the group name and password, nodes
with the same properties will be build in a cluster.
How can i achieve this in Ignite? i have tried use GridSecurityProcessor,
but the second node is denied with exception and start fail.
Please giv
Thanks.
IgniteClientConfiguration.Host is currently a string property that appears
to accept a single dotted IP address, or single host name.
However, in the event that the single configured host/node goes offline, it
would be useful if the client would attempt to dynamically connect to one
or more additi