Re: Countdown latch issue with 2.6.0

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, >>

[jira] [Created] (IGNITE-13132) Countdown latched gets reinitialize to original value(4) when one or more (but not all) node goes down.

Akash Shinde created IGNITE-13132: - Summary: Countdown latched gets reinitialize to original value(4) when one or more (but not all) node goes down. Key: IGNITE-13132 URL: https://issues.apache.org/jira/browse

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

hy do you think it is not included? I see fix version 2.8 in ticket [1]. > > [1] https://issues.apache.org/jira/browse/IGNITE-10884 > > ср, 30 окт. 2019 г. в 17:29, Akash Shinde : > > > > Hi, > > Could you please include IGNITE-10884 > > <https://issues.apa

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Hi, Could you please include IGNITE-10884 in 2.8 release. This issue is blocker for me. Thanks, Akash On Wed, Oct 30, 2019 at 7:38 PM Maxim Muzafarov wrote: > Folks, > > > It seems a week ago I've replied with the release info only to

Re: After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Added dev@ignite.apache.org. Should I log Jira for this issue? Thanks, Akash On Tue, Jan 8, 2019 at 6:16 PM Akash Shinde wrote: > Hi, > > No both nodes, client and server are running on Ignite 2.7 version. I am > starting both server and client from Intellij IDE. > &g