RE: Re: Re: Ignite data not in sync

2022-02-16 Thread Sachin1.Garg
Thank you we will explore these options. From: Maksim Timonin Sent: 15 February 2022 13:17 To: user@ignite.apache.org Subject: [External]Re: Re: Ignite data not in sync The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious

Re: Re: Ignite data not in sync

2022-02-14 Thread Maksim Timonin
gt; > > > > > Thanks, > > Sachin. > > > > > > *From:* Maksim Timonin > *Sent:* 12 February 2022 00:35 > *To:* user@ignite.apache.org > *Subject:* [External]Re: Ignite data not in sync > > > > The e-mail below is from an external sour

RE: Re: Ignite data not in sync

2022-02-13 Thread Sachin1.Garg
:35 To: user@ignite.apache.org Subject: [External]Re: Ignite data not in sync The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Hi! Am I correctly understanding your case: 1. There is a 3-node cluster 2. You restart one

Re: Ignite data not in sync

2022-02-11 Thread Maksim Timonin
Hi! Am I correctly understanding your case: 1. There is a 3-node cluster 2. You restart one node 3. After restart you query a cache with the same query, and sometimes it returns a value for the field "CLERK_ID" and sometimes not. Maksim On Fri, Feb 11, 2022 at 11:27 AM wrote: > We are running