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
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
: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
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
We are running Apache Ignite version 2.7, It is three node cluster.
After restart of one of the Ignite node, we are getting inconsistent select
result on one of our cache.
Is there any way we can remove this inconsistency ? Below is the couple sql
which clerk_id is intermittently visible.
0
