Hi,
Have you tried to reproduce this behaviour with the latest release - 2.8.1?
If I remember correctly, there were some fixes regarding the partition
counters mismatches, for sample:
https://issues.apache.org/jira/browse/IGNITE-10078
-
Alex Shapkin
--
Sent from: http://apache-ignite-users.
Hi, I have created jira for this issue
https://issues.apache.org/jira/browse/IGNITE-13132
Thanks,
Akash
On Sun, Jun 7, 2020 at 9:29 AM Akash Shinde wrote:
> Can someone please help me with this issue.
>
> On Sat, Jun 6, 2020 at 6:45 PM Akash Shinde wrote:
>
>> Hi,
>> Issue: Countdown latched g
Can someone please help me with this issue.
On Sat, Jun 6, 2020 at 6:45 PM Akash Shinde wrote:
> Hi,
> Issue: Countdown latched gets reinitialize to original value(4) when one
> or more (but not all) node goes down. (Partition loss happened)
>
> We are using ignite's distributed countdownlatch t
Hi,
Issue: Countdown latched gets reinitialize to original value(4) when one or
more (but not all) node goes down. (Partition loss happened)
We are using ignite's distributed countdownlatch to make sure that cache
loading is completed on all server nodes. We do this to make sure that our
kafka con
