I think we'll release the next version in October. GridGain might release
it earlier in its community edition.
-
Denis
-- Forwarded message -
From: ihalilaltun
Date: Thu, Jul 18, 2019 at 11:39 PM
Subject: Re: Sudden node failure on Ignite v2.7.5
To:
Hi Ivan
Thanks
Majid,
Send an email to this address to unsubscribe. We can't do that for you:
user-unsubscr...@ignite.apache.org
-
Denis
On Mon, Jul 15, 2019 at 1:42 AM Majid Salimi wrote:
> unsubscribe me, please! I don't want to receive emails.
>
> On Mon, Jul 15, 2019 at 1:06 PM Pavel Vinokurov
>
Unfortunately I do not know. Currently there is no release activity on 2.8.
пт, 19 июл. 2019 г. в 09:39, ihalilaltun :
>
> Hi Ivan
>
> Thanks for the reply. I've checked the jira issue and it says it will be
> released in v2.8, when do you think v2.8 will be released?
>
>
>
> -
> İbrahim
Hi Ivan
Thanks for the reply. I've checked the jira issue and it says it will be
released in v2.8, when do you think v2.8 will be released?
-
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
It seems that the issue [1] was already fixed.
[1] https://issues.apache.org/jira/browse/IGNITE-11953
вт, 16 июл. 2019 г. в 09:30, ihalilaltun :
>
> Hi Pavel,
>
> Thanks for you reply. Since we use the whole sysyem on production
> environment we cannot apply the second solution.
> Do you
Hi Pavel,
Thanks for you reply. Since we use the whole sysyem on production
environment we cannot apply the second solution.
Do you have any estimated time for the first solution/fix?
Thanks.
-
İbrahim Halil Altun
Senior Software Engineer @ Segmentify
--
Sent from:
unsubscribe me, please! I don't want to receive emails.
On Mon, Jul 15, 2019 at 1:06 PM Pavel Vinokurov
wrote:
> Hi,
>
> It looks like the issue described in
> https://issues.apache.org/jira/browse/IGNITE-11953
> There a two options:
> 1. I believe it will be fixed very soon. Thus you could
Hi,
It looks like the issue described in
https://issues.apache.org/jira/browse/IGNITE-11953
There a two options:
1. I believe it will be fixed very soon. Thus you could create a build
based on 2.7.5 with cherry-picked fix.
2. You could remove the cachegroup property from the cache configuration.
Unsubscribe me
On Sat, Jul 13, 2019 at 7:48 PM ihalilaltun
wrote:
> Hi Igniters,
>
> Recently (11.07.2019), we have upgraded our ignite versin from 2.7.0 to
> 2.7.5. Just like after 11 hours one of our nodes killed itself without any
> notification. I am adding the details that I could get from
