Re: AtomicSequence not working when shutting down one server node from a cluster

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

Re: AtomicSequence not working when shutting down one server node from a cluster

Hi, You example required external connection for running it and does not have atomicConfiguration, which was recommended. Hence I created own sample, please look at attachment. The example does not fail, until last one server would by online. PS You need to start ignite.sh with same

Re: AtomicSequence not working when shutting down one server node from a cluster

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

Re: AtomicSequence not working when shutting down one server node from a cluster

This is the link to the code. 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.bat 2.

Re: AtomicSequence not working when shutting down one server node from a cluster

Hi, For REPLICATED cache the property: is not matter. Could you please provide code sample, where the issue is reproduced? On Tue, Sep 20, 2016 at 10:33 AM, hitansu wrote: > First of all why it is still showing this post is not accepted ? > I tried with the backup

Re: AtomicSequence not working when shutting down one server node from a cluster

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.

Re: AtomicSequence not working when shutting down one server node from a cluster

Even simpler and more correct is to increase a number of backups for AtomicConfiguration that is used for your sequence. This can be done by setting AtomicConfiguration.setBackups to value higher than 0. This will make your partitioned AtomicSequence fault tolerant unless all primaries and

Re: AtomicSequence not working when shutting down one server node from a cluster

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:

Re: AtomicSequence not working when shutting down one server node from a cluster

hitansu wrote > For my poc I created a cluster of 3 nodes by executing the ignite.bat file > 3 times.I run the java program as a client to generate sequence id.In the > middle I shut down one server node.The sequence id generation threw > NullpointerException.I observed that if the first server

Re: AtomicSequence not working when shutting down one server node from a cluster

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. -- View this message in context:

Re: AtomicSequence not working when shutting down one server node from a cluster

-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-working-when-shutting-down-one-server-node-from-a-cluster-tp7770p7780.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.