[GitHub] ignite pull request #4041: Apache ignite 2.5 release notes

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/4041 ---

Re: Apache Ignite 2.5 release

>>>> >> >>>>> Andrey, Igniters, >> >>>>> >> >>>>> I bumped into this issue while trying to reproduce another: >> >>>>> https://issues.apache.org/jira/browse/IGNITE-8320 >> >&

Re: Apache Ignite 2.5 release

Almost all issues for Apache Ignite 2.5 release are fixed. Issues that are still in Open state will be moved to 2.6 release. Code freeze for ignite-2.5 branch is planed for tomorrow. Thanks! On Tue, May 8, 2018 at 7:09 PM, Andrey Gura <ag...@apache.org> wrote: Thanks for fast update, I

Re: Apache Ignite 2.5 release

> > Best Regards, > > > > Ivan Rakov > > > > > > > > > > > > On 14.05.2018 15:59, Andrey Gura wrote: > > > > > > > >> Igniters, > > > >> > > > >> we are ready to start process of releasi

Re: Apache Ignite 2.5 release

> > > > > > > On 14.05.2018 15:59, Andrey Gura wrote: > > > > > >> Igniters, > > >> > > >> we are ready to start process of releasing Apache Ignite 2.5. > > >> > > >> So code freeze. No more commits to

Re: Apache Ignite 2.5 release

ze. No more commits to ignite-2.5 branch. > >> > >> Thanks! > >> > >> > >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura <ag...@apache.org> wrote: > >> > >>> Igniters, > >>> > >>> Almost all issues for Apache Ignite 2.5

Re: Apache Ignite 2.5 release

ite-2.5 branch. >> >> Thanks! >> >> >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura <ag...@apache.org> wrote: >> >>> Igniters, >>> >>> Almost all issues for Apache Ignite 2.5 release are fixed. Issues that >>> are still in

Re: Apache Ignite 2.5 release

issues for Apache Ignite 2.5 release are fixed. Issues that are still in Open state will be moved to 2.6 release. Code freeze for ignite-2.5 branch is planed for tomorrow. Thanks! On Tue, May 8, 2018 at 7:09 PM, Andrey Gura <ag...@apache.org> wrote: Thanks for fast update, Ivan. On Tue, May

Re: Apache Ignite 2.5 release

Igniters, we are ready to start process of releasing Apache Ignite 2.5. So code freeze. No more commits to ignite-2.5 branch. Thanks! On Thu, May 10, 2018 at 8:02 PM, Andrey Gura <ag...@apache.org> wrote: > Igniters, > > Almost all issues for Apache Ignite 2.5 release ar

Re: Apache Ignite 2.5 release

Igniters, Almost all issues for Apache Ignite 2.5 release are fixed. Issues that are still in Open state will be moved to 2.6 release. Code freeze for ignite-2.5 branch is planed for tomorrow. Thanks! On Tue, May 8, 2018 at 7:09 PM, Andrey Gura <ag...@apache.org> wrote: > Thanks

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Dmitry, additional BLT related logging is already added. I hope it will help users to understand BLT better. On Tue, May 8, 2018 at 3:36 PM, Dmitriy Setrakyan wrote: > Completely support the decision to move any BLT behavior changes to 2.6. > However, in 2.5 we need to

Re: Apache Ignite 2.5 release

Thanks for fast update, Ivan. On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov wrote: > Andrey, > > Sorry to disturb you again. I have a follow up fix for IGNITE-8429 - > https://issues.apache.org/jira/browse/IGNITE-8453. > Please merge it to master and ignite-2.5. > > Best

Re: Apache Ignite 2.5 release

Andrey, Sorry to disturb you again. I have a follow up fix for IGNITE-8429 - https://issues.apache.org/jira/browse/IGNITE-8453. Please merge it to master and ignite-2.5. Best Regards, Ivan Rakov On 08.05.2018 15:29, Vladimir Ozerov wrote: H2 version updated is moved to AI 2.6. There are

Re: Apache Ignite 2.5 release: Can IGNITE-8041 be included?

Turik, This pull request looks good to me. So I reviewed and merged this example into master and 2.5 branches. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Completely support the decision to move any BLT behavior changes to 2.6. However, in 2.5 we need to add usability log messages, which I believe we already have. D. On Tue, May 8, 2018 at 2:15 PM, Andrey Gura wrote: > Igniters, > > I believe BLT is serious usability problem

Re: Apache Ignite 2.5 release

H2 version updated is moved to AI 2.6. There are several serious problems, main - spatial dependency replacement which is a breaking change. On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn wrote: > IGNITE-8434 merged to master, cherry-picked to ignite-2.5. > > Thank you,

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Igniters, I believe BLT is serious usability problem but rush isn't good idea because can lead to new bugs. As release manager I think that we should move BLT fix to Apache Ignite 2.6 release and focus on issues included to the AI 2.5 release scope. I also want inform you that code freeze is

Re: Apache Ignite 2.5 release

Pavel, issue is targeted to release 2.5 now. Thanks! On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn wrote: > Igniters, > > There is an unpleasant bug in .NET [1]: > Services do not work at all on .NET Core and sometimes on classic .NET. > > I'm almost done with the fix

Re: Apache Ignite 2.5 release

Vladimir, I am afraid that H2 version upgrade can affect system dramatically. Could you please check TC first and then we'll back to the issue? On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov wrote: > Andrey, > > I realized that we missed one very important thing - H2

Re: Apache Ignite 2.5 release

Igniters, There is an unpleasant bug in .NET [1]: Services do not work at all on .NET Core and sometimes on classic .NET. I'm almost done with the fix and I think we should include it in 2.5. Users are complaining [2]. [1] https://issues.apache.org/jira/browse/IGNITE-8434 [2]

Re: Apache Ignite 2.5 release

Andrey, I realized that we missed one very important thing - H2 version upgrade [1]. This is very important thing because new version contain optimization to IN clause processing. All we need is to upgrade H2 vesion from 1.4.196 to 1.4.197 and re-run tests. Can we target it to 2.5 release? [1]

Re: Apache Ignite 2.5 release: Can IGNITE-8041 be included?

Turik, Apache Ignite 2.5 is in scope freeze at this moment. Only critical and early targeted to 2.5 issue can be included to the release. But in this case only examples are affected by your changes. So if Yury doesn't have any objections we can include this change also. On Mon, May 7, 2018 at

Re: Apache Ignite 2.5 release

Ivan, ok, targeted to 2.5. Thanks! On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov wrote: > Thank you, Andrey, > > I saw 1 more proposal in separate topic >

Re: Apache Ignite 2.5 release

Thank you, Andrey, I saw 1 more proposal in separate topic http://apache-ignite-developers.2346864.n4.nabble.com/RE-Hi-can-we-squeeze-this-into-2-5-https-issues-apache-org-jira-browse-IGNITE-8439-td30161.html and 1 proposal here related to ML:

Re: Apache Ignite 2.5 release

Andrey, I'm afraid this ticket should be included into 2.5 as well: https://issues.apache.org/jira/browse/IGNITE-8429 It's similar to previous WAL compaction issue, but now it affects decompression. Best Regards, Ivan Rakov On 07.05.2018 17:09, Andrey Gura wrote: Sergey, Dmitry, I've

Re: Apache Ignite 2.5 release

Sergey, Dmitry, I've targeted your issues to 2.5 release. Thanks! On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov wrote: > I did not understand process. > > Is it required to receive someone reply that issue is agreed to be included > into release? > > Or because there is

Apache Ignite 2.5 release: Can IGNITE-8041 be included?

Denis/Yury, Can this ticket be include in 2.5?: This is very isolated, as I have added another example for GA Grid. Ticket is presently planned for 2.6. Ticket Number Description https://issues.apache.org/jira/browse/IGNITE-8041 Add a GA

Re: Apache Ignite 2.5 release

I did not understand process. Is it required to receive someone reply that issue is agreed to be included into release? Or because there is no response I can cherry-pick anything to 2.5 hoping it is lazy consensus; no one objected. пт, 4 мая 2018 г. в 17:44, Denis Magda : >

Re: Apache Ignite 2.5 release

Igniters, I got lost. Were all the bugs reported in this thread fixed and merged into 2.5 branch? Is there any bug which fix is still in progress? Just want to know when the QA and bugs fixing stage is over. -- Denis On Thu, May 3, 2018 at 9:14 AM, Dmitry Pavlov wrote:

Re: Apache Ignite 2.5 release

Hi Andrey, Igniters, I propose to include https://issues.apache.org/jira/browse/IGNITE-8347 fix to 2.5. It is quite isolated. Memory leak can be reproduced if node in embedded mode is restarted under the same process (thread is alive and cleanup is not performed). Sincerely, Dmitriy Pavlov сб,

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Hi Dmitriy, As far as I understand manual activation will not be required for in-memory mode (same for persistence). Change means we will change node state from 'joined-inactive' to 'joined-active' according to that user defined in policy (cluster grow policy). Default will be allow to rebalance

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Can someone explain what is the before and after effect for this change from the usability standpoint. If we are changing BLT for the in-memory mode, which is the default, then we must think through all the usability consequences ahead of time. Otherwise, the perception will be that the product

Re: Apache Ignite 2.5 release

Igniters, I would like to include into release another critical bug found in ZooKeeper Discovery [1]. Situation reproducing the error is very specific and rare but it leads to full cluster shut down. At the same time fix for it very simple and I don't expect it is too risky. [1]

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

I'm backing up Vladimir's proposal to fix the behavior in 2.5 if it's not time-consuming. To give you a bit more context on the subj, here is why we should have the fix to be delivered in 2.5: http://apache-ignite-users.70518.x6.nabble.com/Problems-

Re: Apache Ignite 2.5 release

Guys, Consider including this [1] to release. It's major usability issue and if not fixed now will lead to compatibility issues in subsequent release. [1] https://issues.apache.org/jira/browse/IGNITE-8418 пт, 27 апр. 2018 г. в 21:34, Andrey Gura : > Of course I meant bug

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

I like AI 2.5 now, but then release AI 2.6 with (BL)AT fix. Probably we will find some more changes to be delivered to users. сб, 28 апр. 2018 г. в 17:56, Vladimir Ozerov : > Yakov, > > Messages would help users understand what is wrong earlier, but will not > protect them

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Yakov, Messages would help users understand what is wrong earlier, but will not protect them from additional maintenance which is required in AI 2.4 and is supposed to be removed in next AI releases. Please note that in IEP-4 topic I proposed alternative solution - release AI 2.5 now, but then

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Guys, how about we release 2.5 in the nearest future after adding proper usability log messages that will explain user what to do and also output link to readme.io with the first BLT related message during node uptime. This should not take much time and we can use the same messages when we have

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Ok, I understand process now. Thank you for clarification. сб, 28 апр. 2018 г. в 17:41, Vladimir Ozerov : > Dmitry, > > I think that developer convenience is of much smaller priority here than > user experience. Moreover, we are not going to unfreeze AI 2.5 scope >

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Dmitry, I think that developer convenience is of much smaller priority here than user experience. Moreover, we are not going to unfreeze AI 2.5 scope completely. Instead, we propose to add BLT fix to AI 2.5, but disallow anything else. This way most contributors will continue working with master

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

-0.9 from me, because I want users get performance fix https://issues.apache.org/jira/browse/IGNITE-7638 and 2 related fixes faster. сб, 28 апр. 2018 г. в 17:35, Dmitry Pavlov : > Hi Vladimir, > > The fact that we will postpone the release will somehow allow users to >

Re: Postpone Apache Ignite 2.5 release to fix baseline topology

Hi Vladimir, The fact that we will postpone the release will somehow allow users to receive fixes faster? What if we will fix (BL)AT it in 2.6 instead? It will be additional issue for all developers to maintain 2.5 & master branches. Sincerely, Dmitriy Pavlov сб, 28 апр. 2018 г. в 17:28,

Postpone Apache Ignite 2.5 release to fix baseline topology

Igniters, we have a problem. Baseline topology was introduced in AI 2.4. Looks like it have two serious flaws which confuse our users a lot: 1) No automatic rebalance by default 2) Topology misalignment between persistent and in-memory caches These are really *critical* problems which severely

Re: Apache Ignite 2.5 release

Of course I meant bug fixes, not bugs :) On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura wrote: > Eduard, Pavel, > > mentioned bugs are good candidates for including to release. > > Targeted to 2.5. > > Thanks! > > On Fri, Apr 27, 2018 at 5:06 PM, Pavel Kovalenko

Re: Apache Ignite 2.5 release

Eduard, Pavel, mentioned bugs are good candidates for including to release. Targeted to 2.5. Thanks! On Fri, Apr 27, 2018 at 5:06 PM, Pavel Kovalenko wrote: > Igniters, > > I would like to add this issue > https://issues.apache.org/jira/browse/IGNITE-8405 to 2.5 scope. > >

Re: Apache Ignite 2.5 release

Igniters, I would like to add this issue https://issues.apache.org/jira/browse/IGNITE-8405 to 2.5 scope. 2018-04-27 16:59 GMT+03:00 Eduard Shangareev : > Guys, > I have finished > ttps://issues.apache.org/jira/browse/IGNITE-7628. > > It looks like a good candidate to

Re: Apache Ignite 2.5 release

Guys, I have finished ttps://issues.apache.org/jira/browse/IGNITE-7628. It looks like a good candidate to merge to 2.5. On Fri, Apr 27, 2018 at 1:32 PM, Ivan Rakov wrote: > Dmitriy, > > There are some notes about WAL compaction in "Persistence Under the Hood" > article:

Re: Apache Ignite 2.5 release

Dmitriy, There are some notes about WAL compaction in "Persistence Under the Hood" article: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-WALcompaction Please take a look - it has all the answers. Best Regards,

Re: Apache Ignite 2.5 release

Hi there! >From my point of view it is blocker too. Targeted to 2.5 release. Thanks, Ivan! пт, 27 апр. 2018 г., 2:29 Dmitriy Setrakyan : > On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov wrote: > > > Folks, > > > > I have a fix for a critical issue

Re: Apache Ignite 2.5 release

On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov wrote: > Folks, > > I have a fix for a critical issue related to WAL compaction: > https://issues.apache.org/jira/browse/IGNITE-8393 > In short, if part of WAL archive is broken, attempt to compress it may > result in spamming

Re: Apache Ignite 2.5 release

merge to master. On Wed, Apr 4, 2018 at 9:11 PM, Andrey Gura < ag...@apache.org wrote: Igniters, It's time to create branch for upcoming Apache Ignite 2.5 release in order to start stabilization process. If there are no any objections I'll create ignite-2.5 branch tomorrow. Also please ch

Re: Apache Ignite 2.5 release

is% > >> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or% > >> >> > >> >>> 20reporter%3DcurrentUser()) > >> >> > >> >>> <https://issues.apache.org/jira/issues/?jql=project% > >>

Re: Apache Ignite 2.5 release

ntUser()%20or% >> >> > >> >>> 20reporter%3DcurrentUser()) >> >> > >> >>> <https://issues.apache.org/jira/issues/?jql=project% >> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is% >> >> > >> >>

Re: Apache Ignite 2.5 release

rsion%3D2.5%20and%20resolution%20is% > >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or% > >> > >> >>> 20reporter%3DcurrentUser())>* > >> > >> >>> > >> > >

Re: Apache Ignite 2.5 release

;> >>> >> > >> >>>> Folks, >> > >> >>>> I see a lot of issues resolved as 2.5 but not merged to >> ignite-2.5 >> > >> >>> branch. >> > >> >>>> >&

Re: Apache Ignite 2.5 release

to > ignite-2.5 > > >> >>> branch. > > >> >>>> > > >> >>>> Who is in charge of release 2.5, why (first time in history) > nobody > > >> >>> changes > > >> >>>> all 2.5 to 2.6? > > >>

Re: Apache Ignite 2.5 release

resolved as 2.5 but not merged to ignite-2.5 > >> >>> branch. > >> >>>> > >> >>>> Who is in charge of release 2.5, why (first time in history) nobody > >> >>> changes > >> >>>> all 2.5 to 2.6? > >> >

Re: Apache Ignite 2.5 release

>>>> >> >>>> 2018-04-06 10:19 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: >> >>>> >> >>>>> Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ >> >>> project >> >>>>> in TC. >&

Re: Apache Ignite 2.5 release

gt; changes > >>>> all 2.5 to 2.6? > >>>> > >>>> 2018-04-06 10:19 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: > >>>> > >>>>> Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ > >>> project

Re: Apache Ignite 2.5 release

t;> >>>>> Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ >>> project >>>>> in TC. >>>>> >>>>> >>>>> >>>>>> On 5 Apr 2018, at 21:55, Denis Magda <dma...@apache.org> wrote: >>>&g

Re: Apache Ignite 2.5 release

or ignite-2.5 in Ignite Tests 2.4+ >> project >>>> in TC. >>>> >>>> >>>> >>>>> On 5 Apr 2018, at 21:55, Denis Magda <dma...@apache.org> wrote: >>>>> >>>>> Thanks Andrey! >>>>> &

Re: Apache Ignite 2.5 release

> > Folks, if you'd like to add anything to 2.5 please make sure it gets > > > merged > > > > into 2.5 branch. > > > > > > > > -- > > > > Denis > > > > > > > > On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org&g

Re: Apache Ignite 2.5 release

please make sure it gets > > merged > > > into 2.5 branch. > > > > > > -- > > > Denis > > > > > > On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org> wrote: > > > > > >> Hi, > > >> > >

Re: Apache Ignite 2.5 release

t; > > > -- > > Denis > > > > On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org> wrote: > > > >> Hi, > >> > >> I've created branch ignite-2.5 for Apache Ignite 2.5 release. > >> > >> As always please follo

Re: Apache Ignite 2.5 release

; > -- > Denis > > On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org> wrote: > >> Hi, >> >> I've created branch ignite-2.5 for Apache Ignite 2.5 release. >> >> As always please follow the rules below when merging new commits to m

Re: Apache Ignite 2.5 release

Thanks Andrey! Folks, if you'd like to add anything to 2.5 please make sure it gets merged into 2.5 branch. -- Denis On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura <ag...@apache.org> wrote: > Hi, > > I've created branch ignite-2.5 for Apache Ignite 2.5 release. > > As

Re: Apache Ignite 2.5 release

Hi, I've created branch ignite-2.5 for Apache Ignite 2.5 release. As always please follow the rules below when merging new commits to master: 1) If ticket is targeted for 2.5 release, please merge to master, then cherry-pick to ignite-2.5 2) Otherwise just merge to master. On Wed, Apr 4

Apache Ignite 2.5 release

Igniters, It's time to create branch for upcoming Apache Ignite 2.5 release in order to start stabilization process. If there are no any objections I'll create ignite-2.5 branch tomorrow. Also please check JIRA issues assigned to you and move it to the next version if this issues shouldn't