RE: Is ID generator split brain compliant?

It worked. Directory set for IGNITE_HOME was getting cleaned up because it wasn't on a mount point or docker volume. Once I set IGNITE_HOME to a directory that persisted between container stop and start, the ID generator worked as expected. -- Sent from: http://apache-ignite-users.705

RE: Is ID generator split brain compliant?

Server logs -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Is ID generator split brain compliant?

I did not see any locks related logs. I did set consistent ID to make sure Ignite looks for the same folder on a restart. But it did not work. On docker restart i.e. the ID generator starts generating a sequence from the initial value. I am attaching the ignite logs for server restart in this

RE: Is ID generator split brain compliant?

@ignite.apache.org Subject: Re: Is ID generator split brain compliant? I believe it won't work either. I will try it soon and share the result. Could you please share some pointers that I should look at for debugging persistence? I have org.apache.ignite=DEBUG in logs and IGNITE_QUITE set to false. There

Re: Is ID generator split brain compliant?

I believe it won't work either. I will try it soon and share the result. Could you please share some pointers that I should look at for debugging persistence? I have org.apache.ignite=DEBUG in logs and IGNITE_QUITE set to false. There a lot of logs, most of which I can not make sense of w.r.t. pe

Re: Is ID generator split brain compliant?

Hello Ankit, I'm not an expert in docker, but for me it looks like you have a problem with overall cache persistence (not only with AtomicSequence), could you try to put some values into cache and check their availability after the restart? пт, 28 сент. 2018 г. в 23:45, abatra : > To give more

Re: Is ID generator split brain compliant?

To give more information on how I restart the server: I run server and client inside their own respective docker container and I issue 'docker stop' for server node container ID to stop and then restart it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Is ID generator split brain compliant?

I tried debugging it a bit. Now, I am running only 1 server node. I am running other node as client. Even with single server node, the atomic sequence is reset to initial value after the server node restarts. I checked the IGNITE_HOME folder, on every restart, the contents are recreated with a d

Re: Is ID generator split brain compliant?

Ankit, > 1. I run two nodes in the cluster. I checked 2 nodes cluster restart (simultaneously, 2 processes on same machine) with the same result - after restart the "current" value != "initial" value. > 2. I restart the entire node and hence the server gets restarted. I gave this example only f

Re: Is ID generator split brain compliant?

There are only two differences in the way you tried the example: 1. I run two nodes in the cluster. 2. I do not stop and configure the server while the JVM is running. I restart the entire node and hence the server gets restarted. Otherwise, I am not sure how is that working out for you. Also, I

Re: Is ID generator split brain compliant?

Ankit, I tried test your example with the following code: configure(); System.out.println("Initial value: " + getCurrentValue("sequence")); for (int i = 0; i < 10_000; i++) incrementAndGet("sequence"); stop(); configure(); System.out.println("Value after restart: " + getCurrentValue("se

Re: Is ID generator split brain compliant?

*Configuration* private static final String STORAGE_PATH = "/existingDirectory/ignite/data/storage";private static final String WAL_PATH = "/existingDirectory/ignite/data/wal";private static final String WAL_ARCHIVE_PATH = "/existingDirectory/ignite/data/wal/archive"; @Overridepu

Re: Is ID generator split brain compliant?

ectory. We have sequence value = 1000, atomic value = 100 after node restart. Could you tell us in more detail how you use "Ignite ID generator"? чт, 27 сент. 2018 г. в 16:27, abatra : > > Hi Anton, > > With persistence enabled, if I reboot the nodes in the cluster, ID generato

Re: Is ID generator split brain compliant?

Hi Anton, With persistence enabled, if I reboot the nodes in the cluster, ID generator starts generating ID from 1 after the nodes are back up. My expectation is that that the latest generated ID(s) will be persisted across cluster reboot and the ID generator will start from the latest persisted

Re: Is ID generator split brain compliant?

o far, it looks pretty good except that it does not provide persistence >>> out >>> of the box. But I can work around it by backing latest generated ID in a >>> persistent cache and initializing ID generator with the latest value on a >>> cluster restart. >>

Re: Is ID generator split brain compliant?

oks pretty good except that it does not provide persistence >> out >> of the box. But I can work around it by backing latest generated ID in a >> persistent cache and initializing ID generator with the latest value on a >> cluster restart. > > > Sounds like a goo

Re: Is ID generator split brain compliant?

> > So far, it looks pretty good except that it does not provide persistence > out > of the box. But I can work around it by backing latest generated ID in a > persistent cache and initializing ID generator with the latest value on a > cluster restart. Sounds like a good solut

Re: Is ID generator split brain compliant?

> Hi, > > I have a requirement to create a distributed cluster-unique ID generator > microservice. I have done a PoC on it using Apache Ignite ID Generator. > > I created a 2 node cluster with two instances of microservices running on > each node. Nodes are in the same data

Is ID generator split brain compliant?

Hi, I have a requirement to create a distributed cluster-unique ID generator microservice. I have done a PoC on it using Apache Ignite ID Generator. I created a 2 node cluster with two instances of microservices running on each node. Nodes are in the same datacenter (in fact in the same

Re: Id-generator

my cacheconfiguration xml I use to > bring up my server node? > > > > Gary > > > > *From:* Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com] > *Sent:* Thursday, May 10, 2018 9:17 AM > *To:* user@ignite.apache.org > *Subject:* Re: Id-generator > > > > Hello!

RE: Id-generator

So can I specify IgniteAtomicLong in my cacheconfiguration xml I use to bring up my server node? Gary From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com] Sent: Thursday, May 10, 2018 9:17 AM To: user@ignite.apache.org Subject: Re: Id-generator Hello! For example, you could have an

Re: Id-generator

Having an issue with identity column, found it’s not possible, but there’s > a workaround using the ID-generator. > > > > How does this work? > > If I have numerous clients attempting to write db records, won’t the > id-generator fail to provide a unique value? Maybe? >

Id-generator

Hi, Doing proof of concept. Having an issue with identity column, found it's not possible, but there's a workaround using the ID-generator. How does this work? If I have numerous clients attempting to write db records, won't the id-generator fail to provide a unique value? May