Problem in forming cluster with multi-jvm in single machine
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 IgniteConfiguration setting.
TcpDiscoverySpi discoSpi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
String hostAddress = InetAddress.getLocalHost().getHostAddress();
List address= Arrays.asList(hostAddress);
//String portRangeStr= "5701-5800";
String portRangeStr= "47500-47509";
String[] portRange = portRangeStr.replace(" ", "").split("-");
discoSpi.setLocalPortRange(Integer.parseInt(portRange[1]) -
Integer.parseInt(portRange[0]) + 1);
discoSpi.setLocalPort(Integer.parseInt(portRange[0]));
ipFinder.setAddresses(address);
ipFinder.setShared(true);
// ipFinder.setAddresses(Collections.singletonList("0.0.0.0:5701..5800"));
//
ipFinder.setAddresses(Collections.singletonList("192.168.127.1:5701..5800"));
discoSpi.setIpFinder(ipFinder);
I want to start ignite in separate jvm to emulate the real cluster.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Problem-in-forming-cluster-with-multi-jvm-in-single-machine-tp9327.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: AtomicSequence not performing well with 2 nodes cluster set up
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 or AtomicSequence with reservesize as 0 ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-performing-well-with-2-nodes-cluster-set-up-tp9208p9253.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
AtomicSequence not performing well with 2 nodes cluster set up
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 to generate 1Million id in each system. Can you please suggest how can I improve the performance? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-performing-well-with-2-nodes-cluster-set-up-tp9208.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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 1000. Means 1st client produces from 1 & 2nd from 1001 & 3rd from 2001. By this way it is not a sequence id genarator.Is there any configuration for that.So that the id will be a sequence across the 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-tp7770p8008.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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 ignite.IdGenerationServiceCacheLayer.getId(IdGenerationServiceCacheLayer.java:61) at idgen_service.IdGenerationServiceDataLayer.generateId(IdGenerationServiceDataLayer.java:56) at client.IdGenTask.generateSequnceId(IdGenTask.java:43) at client.IdGenTask.run(IdGenTask.java:33) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.IgniteCheckedException: null at org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:921) at org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl.internalUpdate(GridCacheAtomicSequenceImpl.java:255) at org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl.incrementAndGet(GridCacheAtomicSequenceImpl.java:175) ... 5 more Caused by: java.lang.NullPointerException at org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl$2.call(GridCacheAtomicSequenceImpl.java:504) at org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl$2.call(GridCacheAtomicSequenceImpl.java:477) at org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1672) at org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:915) -- 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-tp7770p7905.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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 <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. The IdGeneratorClient.java runs as a client node 3. IdGenTask.java,which is a runnable, generates id Note: I am not using IgniteRunnable,which I think not necessary as the AtomicSequnce should run on all the server nodes by default. -- 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-tp7770p7865.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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. -- 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-tp7770p7839.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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: http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-working-when-shutting-down-one-server-node-from-a-cluster-tp7770p7793.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
