Re: Cache was inconsistent state

2020-05-11 Thread Evgenii Zhuravlev
John, Yes, client nodes should have this parameter too. Evgenii пн, 11 мая 2020 г. в 07:54, John Smith : > I mean both the prefer IPV4 and the Zookeeper discovery should be on the > "central" cluster as well as all nodes specifically marked as client = true? > > On Mon, 11 May 2020 at 09:59,

Re: Cache was inconsistent state

2020-05-11 Thread John Smith
I mean both the prefer IPV4 and the Zookeeper discovery should be on the "central" cluster as well as all nodes specifically marked as client = true? On Mon, 11 May 2020 at 09:59, John Smith wrote: > Should be on client nodes as well that are specifically setClient = true? > > On Fri, 8 May

Re: Cache was inconsistent state

2020-05-11 Thread John Smith
Should be on client nodes as well that are specifically setClient = true? On Fri, 8 May 2020 at 22:26, Evgenii Zhuravlev wrote: > John, > > It looks like a split-brain. They were in one cluster at first. I'm not > sure what was the reason for this, it could be a network problem or > something

Re: Cache was inconsistent state

2020-05-08 Thread Evgenii Zhuravlev
John, It looks like a split-brain. They were in one cluster at first. I'm not sure what was the reason for this, it could be a network problem or something else. I saw in logs that you use both ipv4 and ipv6, I would recommend using only one of them to avoid problems - just add

Re: Cache was inconsistent state

2020-05-08 Thread John Smith
How though? It's the same cluster! We haven't changed anything this happened on it's own... All I did was reboot the node and the cluster fixed itself. On Fri, 8 May 2020 at 15:32, Evgenii Zhuravlev wrote: > Hi John, > > *Yes, it looks like they are in a different clusters:* > *Metrics from

Re: Cache was inconsistent state

2020-05-08 Thread Evgenii Zhuravlev
Hi John, *Yes, it looks like they are in a different clusters:* *Metrics from the node with a problem:* [15:17:28,668][INFO][grid-timeout-worker-#23%xx%][IgniteKernal%xx] Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=5bbf262e, name=xx, uptime=93

Re: Cache was inconsistent state

2020-05-08 Thread John Smith
Hi Evgenii, here the logs. https://www.dropbox.com/s/ke71qsoqg588kc8/ignite-logs.zip?dl=0 On Fri, 8 May 2020 at 09:21, John Smith wrote: > Ok let me try get them... > > On Thu., May 7, 2020, 1:14 p.m. Evgenii Zhuravlev, < > e.zhuravlev...@gmail.com> wrote: > >> Hi, >> >> It looks like the

Re: Cache was inconsistent state

2020-05-08 Thread John Smith
Ok let me try get them... On Thu., May 7, 2020, 1:14 p.m. Evgenii Zhuravlev, wrote: > Hi, > > It looks like the third server node was not a part of this cluster before > restart. Can you share full logs from all server nodes? > > Evgenii > > чт, 7 мая 2020 г. в 09:11, John Smith : > >> Hi,

Re: Cache was inconsistent state

2020-05-07 Thread Evgenii Zhuravlev
Hi, It looks like the third server node was not a part of this cluster before restart. Can you share full logs from all server nodes? Evgenii чт, 7 мая 2020 г. в 09:11, John Smith : > Hi, running 2.7.0 on 3 deployed on VMs running Ubuntu. > > I checked the state of the cluster by going to:

Cache was inconsistent state

2020-05-07 Thread John Smith
Hi, running 2.7.0 on 3 deployed on VMs running Ubuntu. I checked the state of the cluster by going to: /ignite?cmd=currentState And the response was: {"successStatus":0,"error":null,"sessionToken":null,"response":true} I also checked: /ignite?cmd=size= 2 nodes where reporting 3 million