I have written a program to start ignite in separate jvms to form a
cluster.It is starting the Ignite,but could not form a cluster. It is
printing following log.
Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/10.150.113.61:47500]
Below is my IgniteC
Thanks for the quick reply.
If I will use range, then it wont be anymore a sequence in cluster-wide.If
the range is 1000,then calling AtomicSequence.increamentAndGet() twice may
give 1 & 1001.But I want it should give 1 & 2 respectively in any situation.
Again Is it the same thing using AtomicLong
Hi,
I am using AtomicSequence to generate sequence id.So I have set the reserve
size as 0 as I want strictly sequence id throughout the cluster. I have a
cluster set up of 2 nodes. It is taking around 18min. to generate 1Million
id in one system more than 25min. in other system. I have triggered t
Thanks. The issue got resolved. While starting the client I was not giving
the configuration file.By setting the configuration file to client it solved
the issue.
But one for doubt I have. If I will run 2-3 client at the same time , then
why the id being generated in each client has a diff of 1000
class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:908)
at
org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl.incrementAndGet(GridCacheAtomicSequenceImpl.java:178)
at
ig
This is the link to the code.
https://github.com/hitansu/ScalableUniqueIdGenerator/tree/master/src/main/java
<https://github.com/hitansu/ScalableUniqueIdGenerator/tree/master/src/main/java>
client/IdGeneratorClient.java is the main class.
1. Started server nodes by executing the ignite
First of all why it is still showing this post is not accepted ?
I tried with the backup option & also tried with the REPLICATED mode cache
setting.Still it gives null poiter
when I stop one of the server(basically the first node).This is my cache
setting.
Is it like replication ?But if the AtomicSequnce is cluster wide, then it
should work even one of the node is down.Isn't it?Why is it computing the
AtomicSequnce only in one node ?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-working-when-sh
