Re: Apache Ignite 2.5 release

[Andrey Gura]

Hi,

looks like critical issue. Please merge to ignite-2.5 branch.

Thanks!

On Wed, May 23, 2018 at 3:28 PM, Alexey Goncharuk
 wrote:
> Agree, I think we should include this fix in 2.5 as well, otherwise users
> who enable WAL compaction may face data consistency issues after various
> topology restarts.
>
> ср, 23 мая 2018 г. в 12:33, Ivan Rakov :
>
>> Igniters,
>>
>> Unfortunately, previous issue mentioned by Alex G. [1] has broken WAL
>> compaction in 2.5.
>> Follow up fix is already implemented and merged to master [2]. I suggest
>> to include it into 2.5 scope; any user attempt to enable compaction on
>> 2.5 (or use previously compacted WAL segments) will fail with exception
>> otherwise.
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-8464
>> [2] - https://issues.apache.org/jira/browse/IGNITE-8561
>>
>> Best Regards,
>> Ivan Rakov
>>
>> On 17.05.2018 19:28, Denis Magda wrote:
>> > Alexey,
>> >
>> > Makes sense to merge.
>> >
>> > --
>> > Denis
>> >
>> > On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
>> > alexey.goncha...@gmail.com> wrote:
>> >
>> >> Denis,
>> >>
>> >> The issue with page corruption may manifest itself when a node is
>> stopped
>> >> during partition eviction (basically, a random chance on topology change
>> >> scenario).
>> >>
>> >> The issue with WAL iterator can manifest during historical rebalancing
>> >> (this is less likely than the previous issue).
>> >>
>> >> 2018-05-17 18:07 GMT+03:00 Denis Magda :
>> >>
>> >>> We keep facing the issues that postpone the release over and over again
>> >>> which seems like a never-ending story.
>> >>>
>> >>> What are the changes the users come across the 2 latest bugs you've
>> >>> mentioned (any special conditions)?
>> >>>
>> >>> What's the overall state of our testing cycles? When would we send the
>> >>> release for vote if include the abovementioned bugs or move them to the
>> >>> next release?
>> >>>
>> >>> --
>> >>> Denis
>> >>>
>> >>> On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
>> >>> alexey.goncha...@gmail.com> wrote:
>> >>>
>>  Another issue that may lead to incorrect recovery on node startup is
>>  https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
>> >>> PA.
>>  I
>>  suggest we also include it to 2.5 given that fix improves stability of
>> >>> the
>>  persistence layer. Any objections?
>> 
>>  2018-05-17 16:55 GMT+03:00 Ivan Rakov :
>> 
>> > Andrey, Igniters,
>> >
>> > I bumped into this issue while trying to reproduce another:
>> > https://issues.apache.org/jira/browse/IGNITE-8320
>> > I think, this fix worth being cherry-picked into 2.5. Possibility of
>> > AssertionError on persistence level is really undesirable for Ignite
>> >>> as a
>> > product.
>> >
>> > Best Regards,
>> > Ivan Rakov
>> >
>> >
>> > 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 ignite-2.5 branch.
>> >>
>> >> Thanks!
>> >>
>> >>
>> >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
>> >>> wrote:
>> >>> 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 
>> >>> wrote:
>>  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 Regards,
>> > Ivan Rakov
>> >
>> >
>> > On 08.05.2018 15:29, Vladimir Ozerov wrote:
>> >
>> >> 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 <
>>  ptupit...@apache.org
>> >> wrote:
>> >>
>> >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
>> >>> Thank you, Andrey!
>> >>>
>> >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura > >>> wrote:
>> >>>
>> >>> Pavel,
>>  issue is targeted to release 2.5 now. Thanks!
>> 
>>  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
>>  ptupit...@apache.org>
>>  wrote:
>> 
>> > Igniters,
>> >
>> > There is an unpleasant bug in .NET [1

Re: Apache Ignite 2.5 release

[Alexey Goncharuk]

Agree, I think we should include this fix in 2.5 as well, otherwise users
who enable WAL compaction may face data consistency issues after various
topology restarts.

ср, 23 мая 2018 г. в 12:33, Ivan Rakov :

> Igniters,
>
> Unfortunately, previous issue mentioned by Alex G. [1] has broken WAL
> compaction in 2.5.
> Follow up fix is already implemented and merged to master [2]. I suggest
> to include it into 2.5 scope; any user attempt to enable compaction on
> 2.5 (or use previously compacted WAL segments) will fail with exception
> otherwise.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-8464
> [2] - https://issues.apache.org/jira/browse/IGNITE-8561
>
> Best Regards,
> Ivan Rakov
>
> On 17.05.2018 19:28, Denis Magda wrote:
> > Alexey,
> >
> > Makes sense to merge.
> >
> > --
> > Denis
> >
> > On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> >> Denis,
> >>
> >> The issue with page corruption may manifest itself when a node is
> stopped
> >> during partition eviction (basically, a random chance on topology change
> >> scenario).
> >>
> >> The issue with WAL iterator can manifest during historical rebalancing
> >> (this is less likely than the previous issue).
> >>
> >> 2018-05-17 18:07 GMT+03:00 Denis Magda :
> >>
> >>> We keep facing the issues that postpone the release over and over again
> >>> which seems like a never-ending story.
> >>>
> >>> What are the changes the users come across the 2 latest bugs you've
> >>> mentioned (any special conditions)?
> >>>
> >>> What's the overall state of our testing cycles? When would we send the
> >>> release for vote if include the abovementioned bugs or move them to the
> >>> next release?
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
> >>> alexey.goncha...@gmail.com> wrote:
> >>>
>  Another issue that may lead to incorrect recovery on node startup is
>  https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
> >>> PA.
>  I
>  suggest we also include it to 2.5 given that fix improves stability of
> >>> the
>  persistence layer. Any objections?
> 
>  2018-05-17 16:55 GMT+03:00 Ivan Rakov :
> 
> > Andrey, Igniters,
> >
> > I bumped into this issue while trying to reproduce another:
> > https://issues.apache.org/jira/browse/IGNITE-8320
> > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > AssertionError on persistence level is really undesirable for Ignite
> >>> as a
> > product.
> >
> > Best Regards,
> > Ivan Rakov
> >
> >
> > 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 ignite-2.5 branch.
> >>
> >> Thanks!
> >>
> >>
> >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
> >>> wrote:
> >>> 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 
> >>> wrote:
>  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 Regards,
> > Ivan Rakov
> >
> >
> > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> >
> >> 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 <
>  ptupit...@apache.org
> >> wrote:
> >>
> >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> >>> Thank you, Andrey!
> >>>
> >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  >>> wrote:
> >>>
> >>> Pavel,
>  issue is targeted to release 2.5 now. Thanks!
> 
>  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
>  ptupit...@apache.org>
>  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 and I think we should include it
> >>> in
> > 2.5.
> >
>  Users
> 
>

Re: Apache Ignite 2.5 release

[Ivan Rakov]

Igniters,

Unfortunately, previous issue mentioned by Alex G. [1] has broken WAL 
compaction in 2.5.
Follow up fix is already implemented and merged to master [2]. I suggest 
to include it into 2.5 scope; any user attempt to enable compaction on 
2.5 (or use previously compacted WAL segments) will fail with exception 
otherwise.


[1] - https://issues.apache.org/jira/browse/IGNITE-8464
[2] - https://issues.apache.org/jira/browse/IGNITE-8561

Best Regards,
Ivan Rakov

On 17.05.2018 19:28, Denis Magda wrote:

Alexey,

Makes sense to merge.

--
Denis

On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Denis,

The issue with page corruption may manifest itself when a node is stopped
during partition eviction (basically, a random chance on topology change
scenario).

The issue with WAL iterator can manifest during historical rebalancing
(this is less likely than the previous issue).

2018-05-17 18:07 GMT+03:00 Denis Magda :


We keep facing the issues that postpone the release over and over again
which seems like a never-ending story.

What are the changes the users come across the 2 latest bugs you've
mentioned (any special conditions)?

What's the overall state of our testing cycles? When would we send the
release for vote if include the abovementioned bugs or move them to the
next release?

--
Denis

On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Another issue that may lead to incorrect recovery on node startup is
https://issues.apache.org/jira/browse/IGNITE-8464 which is already in

PA.

I
suggest we also include it to 2.5 given that fix improves stability of

the

persistence layer. Any objections?

2018-05-17 16:55 GMT+03:00 Ivan Rakov :


Andrey, Igniters,

I bumped into this issue while trying to reproduce another:
https://issues.apache.org/jira/browse/IGNITE-8320
I think, this fix worth being cherry-picked into 2.5. Possibility of
AssertionError on persistence level is really undesirable for Ignite

as a

product.

Best Regards,
Ivan Rakov


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 ignite-2.5 branch.

Thanks!


On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 

wrote:

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 

wrote:

Thanks for fast update, Ivan.

On Tue, May 8, 2018 at 5:59 PM, Ivan Rakov 
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 several serious
problems,
main - spatial dependency replacement which is a breaking

change.

On Tue, May 8, 2018 at 10:17 AM, Pavel Tupitsyn <

ptupit...@apache.org

wrote:

IGNITE-8434 merged to master, cherry-picked to ignite-2.5.

Thank you, Andrey!

On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
issue is targeted to release 2.5 now. Thanks!

On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
ptupit...@apache.org>
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 and I think we should include it

in

2.5.


Users


are complaining [2].


[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
http://apache-ignite-users.70518.x6.nabble.com/Re-


Service-Grid-and-net-core-2-td21318.html


On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
voze...@gridgain.com>
wrote:

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] https://issues.apache.org/jira/browse/IGNITE-4150

On Mon, May 7, 2018 at 6:07 PM, Andrey Gura <

ag...@apache.org

wrote:

Ivan,

ok, targeted to 2.5. Thanks!

On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <


dpavlov@gmail.com>

wrote:

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:
http://apache-ignite-developers.2346864.n4.nabble.


com/Apache-Ignite-2-5-release-td28927i20.html#a30155


but here Yuriy Babak probably should share his opinion.

Sincerely,
Dmitriy Pavlov

пн, 7 мая 2018 г. в 17:09, Andrey Gura 
:

Sergey, Dmitry,

I've targeted your issues to 2.5 release.

Thanks!

On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <


dpavlov@gmail.com

Re: Apache Ignite 2.5 release

[Denis Magda]

Alexey,

Makes sense to merge.

--
Denis

On Thu, May 17, 2018 at 8:53 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Denis,
>
> The issue with page corruption may manifest itself when a node is stopped
> during partition eviction (basically, a random chance on topology change
> scenario).
>
> The issue with WAL iterator can manifest during historical rebalancing
> (this is less likely than the previous issue).
>
> 2018-05-17 18:07 GMT+03:00 Denis Magda :
>
> > We keep facing the issues that postpone the release over and over again
> > which seems like a never-ending story.
> >
> > What are the changes the users come across the 2 latest bugs you've
> > mentioned (any special conditions)?
> >
> > What's the overall state of our testing cycles? When would we send the
> > release for vote if include the abovementioned bugs or move them to the
> > next release?
> >
> > --
> > Denis
> >
> > On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > Another issue that may lead to incorrect recovery on node startup is
> > > https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
> > PA.
> > > I
> > > suggest we also include it to 2.5 given that fix improves stability of
> > the
> > > persistence layer. Any objections?
> > >
> > > 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
> > >
> > > > Andrey, Igniters,
> > > >
> > > > I bumped into this issue while trying to reproduce another:
> > > > https://issues.apache.org/jira/browse/IGNITE-8320
> > > > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > > > AssertionError on persistence level is really undesirable for Ignite
> > as a
> > > > product.
> > > >
> > > > Best Regards,
> > > > Ivan Rakov
> > > >
> > > >
> > > > 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 ignite-2.5 branch.
> > > >>
> > > >> Thanks!
> > > >>
> > > >>
> > > >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
> > wrote:
> > > >>
> > > >>> 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 
> > wrote:
> > > >>>
> > >  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 Regards,
> > > > Ivan Rakov
> > > >
> > > >
> > > > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> > > >
> > > >> 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 <
> > > ptupit...@apache.org
> > > >> >
> > > >> wrote:
> > > >>
> > > >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> > > >>>
> > > >>> Thank you, Andrey!
> > > >>>
> > > >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  >
> > > >>> wrote:
> > > >>>
> > > >>> Pavel,
> > > 
> > >  issue is targeted to release 2.5 now. Thanks!
> > > 
> > >  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
> > >  ptupit...@apache.org>
> > >  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 and I think we should include it
> > in
> > > > 2.5.
> > > >
> > >  Users
> > > 
> > > > are complaining [2].
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > > > [2]
> > > > http://apache-ignite-users.70518.x6.nabble.com/Re-
> > > >
> > >  Service-Grid-and-net-core-2-td21318.html
> > > 
> > > > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > > > voze...@gridgain.com>
> > > > wrote:
> > > >
> > > > 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 

Re: Apache Ignite 2.5 release

[Alexey Goncharuk]

Denis,

The issue with page corruption may manifest itself when a node is stopped
during partition eviction (basically, a random chance on topology change
scenario).

The issue with WAL iterator can manifest during historical rebalancing
(this is less likely than the previous issue).

2018-05-17 18:07 GMT+03:00 Denis Magda :

> We keep facing the issues that postpone the release over and over again
> which seems like a never-ending story.
>
> What are the changes the users come across the 2 latest bugs you've
> mentioned (any special conditions)?
>
> What's the overall state of our testing cycles? When would we send the
> release for vote if include the abovementioned bugs or move them to the
> next release?
>
> --
> Denis
>
> On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > Another issue that may lead to incorrect recovery on node startup is
> > https://issues.apache.org/jira/browse/IGNITE-8464 which is already in
> PA.
> > I
> > suggest we also include it to 2.5 given that fix improves stability of
> the
> > persistence layer. Any objections?
> >
> > 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
> >
> > > Andrey, Igniters,
> > >
> > > I bumped into this issue while trying to reproduce another:
> > > https://issues.apache.org/jira/browse/IGNITE-8320
> > > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > > AssertionError on persistence level is really undesirable for Ignite
> as a
> > > product.
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > >
> > > 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 ignite-2.5 branch.
> > >>
> > >> Thanks!
> > >>
> > >>
> > >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura 
> wrote:
> > >>
> > >>> 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 
> wrote:
> > >>>
> >  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 Regards,
> > > Ivan Rakov
> > >
> > >
> > > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> > >
> > >> 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 <
> > ptupit...@apache.org
> > >> >
> > >> wrote:
> > >>
> > >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> > >>>
> > >>> Thank you, Andrey!
> > >>>
> > >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
> > >>> wrote:
> > >>>
> > >>> Pavel,
> > 
> >  issue is targeted to release 2.5 now. Thanks!
> > 
> >  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
> >  ptupit...@apache.org>
> >  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 and I think we should include it
> in
> > > 2.5.
> > >
> >  Users
> > 
> > > are complaining [2].
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > > [2]
> > > http://apache-ignite-users.70518.x6.nabble.com/Re-
> > >
> >  Service-Grid-and-net-core-2-td21318.html
> > 
> > > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > > voze...@gridgain.com>
> > > wrote:
> > >
> > > 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] https://issues.apache.org/jira/browse/IGNITE-4150
> > >>
> > >> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  >
> > >> wrote:
> > >>
> > >> Ivan,
> > >>>
> > >>> ok, targe

Re: Apache Ignite 2.5 release

[Denis Magda]

We keep facing the issues that postpone the release over and over again
which seems like a never-ending story.

What are the changes the users come across the 2 latest bugs you've
mentioned (any special conditions)?

What's the overall state of our testing cycles? When would we send the
release for vote if include the abovementioned bugs or move them to the
next release?

--
Denis

On Thu, May 17, 2018 at 7:44 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Another issue that may lead to incorrect recovery on node startup is
> https://issues.apache.org/jira/browse/IGNITE-8464 which is already in PA.
> I
> suggest we also include it to 2.5 given that fix improves stability of the
> persistence layer. Any objections?
>
> 2018-05-17 16:55 GMT+03:00 Ivan Rakov :
>
> > Andrey, Igniters,
> >
> > I bumped into this issue while trying to reproduce another:
> > https://issues.apache.org/jira/browse/IGNITE-8320
> > I think, this fix worth being cherry-picked into 2.5. Possibility of
> > AssertionError on persistence level is really undesirable for Ignite as a
> > product.
> >
> > Best Regards,
> > Ivan Rakov
> >
> >
> > 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 ignite-2.5 branch.
> >>
> >> Thanks!
> >>
> >>
> >> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:
> >>
> >>> 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  wrote:
> >>>
>  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 Regards,
> > Ivan Rakov
> >
> >
> > On 08.05.2018 15:29, Vladimir Ozerov wrote:
> >
> >> 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 <
> ptupit...@apache.org
> >> >
> >> wrote:
> >>
> >> IGNITE-8434 merged to master, cherry-picked to ignite-2.5.
> >>>
> >>> Thank you, Andrey!
> >>>
> >>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
> >>> wrote:
> >>>
> >>> Pavel,
> 
>  issue is targeted to release 2.5 now. Thanks!
> 
>  On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
>  ptupit...@apache.org>
>  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 and I think we should include it in
> > 2.5.
> >
>  Users
> 
> > are complaining [2].
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > [2]
> > http://apache-ignite-users.70518.x6.nabble.com/Re-
> >
>  Service-Grid-and-net-core-2-td21318.html
> 
> > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> > voze...@gridgain.com>
> > wrote:
> >
> > 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] https://issues.apache.org/jira/browse/IGNITE-4150
> >>
> >> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura 
> >> wrote:
> >>
> >> Ivan,
> >>>
> >>> ok, targeted to 2.5. Thanks!
> >>>
> >>> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
> >>>
> >> dpavlov@gmail.com>
> >>>
>  wrote:
> >>>
>  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:
>  http://apache-ignite-developers.2346864.n4.nabble.
> >>>

Re: Apache Ignite 2.5 release

[Alexey Goncharuk]

Another issue that may lead to incorrect recovery on node startup is
https://issues.apache.org/jira/browse/IGNITE-8464 which is already in PA. I
suggest we also include it to 2.5 given that fix improves stability of the
persistence layer. Any objections?

2018-05-17 16:55 GMT+03:00 Ivan Rakov :

> Andrey, Igniters,
>
> I bumped into this issue while trying to reproduce another:
> https://issues.apache.org/jira/browse/IGNITE-8320
> I think, this fix worth being cherry-picked into 2.5. Possibility of
> AssertionError on persistence level is really undesirable for Ignite as a
> product.
>
> Best Regards,
> Ivan Rakov
>
>
> 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 ignite-2.5 branch.
>>
>> Thanks!
>>
>>
>> On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:
>>
>>> 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  wrote:
>>>
 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 Regards,
> Ivan Rakov
>
>
> On 08.05.2018 15:29, Vladimir Ozerov wrote:
>
>> 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, Andrey!
>>>
>>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura 
>>> wrote:
>>>
>>> Pavel,

 issue is targeted to release 2.5 now. Thanks!

 On Mon, May 7, 2018 at 10:40 PM, Pavel Tupitsyn <
 ptupit...@apache.org>
 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 and I think we should include it in
> 2.5.
>
 Users

> are complaining [2].
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8434
> [2]
> http://apache-ignite-users.70518.x6.nabble.com/Re-
>
 Service-Grid-and-net-core-2-td21318.html

> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> wrote:
>
> 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] https://issues.apache.org/jira/browse/IGNITE-4150
>>
>> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura 
>> wrote:
>>
>> Ivan,
>>>
>>> ok, targeted to 2.5. Thanks!
>>>
>>> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
>>>
>> dpavlov@gmail.com>
>>>
 wrote:
>>>
 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:
 http://apache-ignite-developers.2346864.n4.nabble.

>>> com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>>>
 but here Yuriy Babak probably should share his opinion.

 Sincerely,
 Dmitriy Pavlov

 пн, 7 мая 2018 г. в 17:09, Andrey Gura :

> Sergey, Dmitry,
>
> I've targeted your issues to 2.5 release.
>
> Thanks!
>
> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
>
 dpavlov@gmail.com>

> wrote:
>
>> I did not understand process.
>>
>> Is it required to receive someone reply that issue is agreed
>> to
>>
> be

>>>

Re: Apache Ignite 2.5 release

[Ivan Rakov]

Andrey, Igniters,

I bumped into this issue while trying to reproduce another: 
https://issues.apache.org/jira/browse/IGNITE-8320
I think, this fix worth being cherry-picked into 2.5. Possibility of 
AssertionError on persistence level is really undesirable for Ignite as 
a product.


Best Regards,
Ivan Rakov

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 ignite-2.5 branch.

Thanks!


On Thu, May 10, 2018 at 8:02 PM, Andrey Gura  wrote:

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  wrote:

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 Regards,
Ivan Rakov


On 08.05.2018 15:29, Vladimir Ozerov wrote:

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

On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:


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 and I think we should include it in 2.5.

Users

are complaining [2].


[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
http://apache-ignite-users.70518.x6.nabble.com/Re-

Service-Grid-and-net-core-2-td21318.html

On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
wrote:


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] https://issues.apache.org/jira/browse/IGNITE-4150

On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:


Ivan,

ok, targeted to 2.5. Thanks!

On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <

dpavlov@gmail.com>

wrote:

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:
http://apache-ignite-developers.2346864.n4.nabble.

com/Apache-Ignite-2-5-release-td28927i20.html#a30155

but here Yuriy Babak probably should share his opinion.

Sincerely,
Dmitriy Pavlov

пн, 7 мая 2018 г. в 17:09, Andrey Gura :

Sergey, Dmitry,

I've targeted your issues to 2.5 release.

Thanks!

On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <

dpavlov@gmail.com>

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 no response I can cherry-pick anything to

2.5

hoping

it
is lazy consensus; no one objected.

пт, 4 мая 2018 г. в 17:44, Denis Magda :


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 <

dpavlov@gmail.com

wrote:


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

сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov

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] https://issues.apache.org/jira/browse/IGNITE-8421

On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:


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 <

ag...@apache.org>:

Of course I meant bug fixes, not bugs :)

On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura <

ag...@apache.org>

wrote:

Eduard, Pavel,

mentioned bugs are good candidates for includi

Re: Apache Ignite 2.5 release

[Andrey Gura]

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  wrote:
> 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  wrote:
>> 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 Regards,
>>> Ivan Rakov
>>>
>>>
>>> On 08.05.2018 15:29, Vladimir Ozerov wrote:

 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, Andrey!
>
> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:
>
>> 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 and I think we should include it in 2.5.
>>
>> Users
>>>
>>> are complaining [2].
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-8434
>>> [2]
>>> http://apache-ignite-users.70518.x6.nabble.com/Re-
>>
>> Service-Grid-and-net-core-2-td21318.html
>>>
>>> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
>>> wrote:
>>>
 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] https://issues.apache.org/jira/browse/IGNITE-4150

 On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:

> Ivan,
>
> ok, targeted to 2.5. Thanks!
>
> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
>
> dpavlov@gmail.com>
>
> wrote:
>>
>> 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:
>> http://apache-ignite-developers.2346864.n4.nabble.
>
> com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>>
>> but here Yuriy Babak probably should share his opinion.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>>>
>>> Sergey, Dmitry,
>>>
>>> I've targeted your issues to 2.5 release.
>>>
>>> Thanks!
>>>
>>> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
>>
>> dpavlov@gmail.com>
>>>
>>> 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 no response I can cherry-pick anything to
>
> 2.5
>
> hoping

 it
 is lazy consensus; no one objected.

 пт, 4 мая 2018 г. в 17:44, Denis Magda :

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

 dpavlov@gmail.com
>
> wrote:
>
>> Hi Andrey, Igniters,
>>
>> I propose to include
>> https://issues.apache.org/jira/browse/IGNITE-8347
>
> fix
>>
>

Re: Apache Ignite 2.5 release

[Andrey Gura]

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  wrote:
> 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 Regards,
>> Ivan Rakov
>>
>>
>> On 08.05.2018 15:29, Vladimir Ozerov wrote:
>>>
>>> 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, Andrey!

 On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:

> 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 and I think we should include it in 2.5.
>
> Users
>>
>> are complaining [2].
>>
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-8434
>> [2]
>> http://apache-ignite-users.70518.x6.nabble.com/Re-
>
> Service-Grid-and-net-core-2-td21318.html
>>
>> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
>> wrote:
>>
>>> 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] https://issues.apache.org/jira/browse/IGNITE-4150
>>>
>>> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
>>>
 Ivan,

 ok, targeted to 2.5. Thanks!

 On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <

 dpavlov@gmail.com>

 wrote:
>
> 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:
> http://apache-ignite-developers.2346864.n4.nabble.

 com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>
> but here Yuriy Babak probably should share his opinion.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>>
>> Sergey, Dmitry,
>>
>> I've targeted your issues to 2.5 release.
>>
>> Thanks!
>>
>> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
>
> dpavlov@gmail.com>
>>
>> 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 no response I can cherry-pick anything to

 2.5

 hoping
>>>
>>> it
>>> is lazy consensus; no one objected.
>>>
>>> пт, 4 мая 2018 г. в 17:44, Denis Magda :
>>>
 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 <
>>>
>>> dpavlov@gmail.com

 wrote:

> 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
>
> сб, 28

Re: Apache Ignite 2.5 release

[Andrey Gura]

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 Regards,
> Ivan Rakov
>
>
> On 08.05.2018 15:29, Vladimir Ozerov wrote:
>>
>> 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, Andrey!
>>>
>>> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:
>>>
 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 and I think we should include it in 2.5.

 Users
>
> are complaining [2].
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8434
> [2]
> http://apache-ignite-users.70518.x6.nabble.com/Re-

 Service-Grid-and-net-core-2-td21318.html
>
> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
> wrote:
>
>> 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] https://issues.apache.org/jira/browse/IGNITE-4150
>>
>> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
>>
>>> Ivan,
>>>
>>> ok, targeted to 2.5. Thanks!
>>>
>>> On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
>>>
>>> dpavlov@gmail.com>
>>>
>>> wrote:

 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:
 http://apache-ignite-developers.2346864.n4.nabble.
>>>
>>> com/Apache-Ignite-2-5-release-td28927i20.html#a30155

 but here Yuriy Babak probably should share his opinion.

 Sincerely,
 Dmitriy Pavlov

 пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>
> Sergey, Dmitry,
>
> I've targeted your issues to 2.5 release.
>
> Thanks!
>
> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <

 dpavlov@gmail.com>
>
> 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 no response I can cherry-pick anything to
>>>
>>> 2.5
>>>
>>> hoping
>>
>> it
>> is lazy consensus; no one objected.
>>
>> пт, 4 мая 2018 г. в 17:44, Denis Magda :
>>
>>> 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 <
>>
>> dpavlov@gmail.com
>>>
>>> wrote:
>>>
 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

 сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
 >>> :

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

Re: Apache Ignite 2.5 release

[Ivan Rakov]

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

On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:


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 and I think we should include it in 2.5.

Users

are complaining [2].


[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
http://apache-ignite-users.70518.x6.nabble.com/Re-

Service-Grid-and-net-core-2-td21318.html

On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
wrote:


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] https://issues.apache.org/jira/browse/IGNITE-4150

On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:


Ivan,

ok, targeted to 2.5. Thanks!

On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <

dpavlov@gmail.com>

wrote:

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:
http://apache-ignite-developers.2346864.n4.nabble.

com/Apache-Ignite-2-5-release-td28927i20.html#a30155

but here Yuriy Babak probably should share his opinion.

Sincerely,
Dmitriy Pavlov

пн, 7 мая 2018 г. в 17:09, Andrey Gura :

Sergey, Dmitry,

I've targeted your issues to 2.5 release.

Thanks!

On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <

dpavlov@gmail.com>

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 no response I can cherry-pick anything to

2.5

hoping

it
is lazy consensus; no one objected.

пт, 4 мая 2018 г. в 17:44, Denis Magda :


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 <

dpavlov@gmail.com

wrote:


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

сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov

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] https://issues.apache.org/jira/browse/IGNITE-8421

On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:


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 <

ag...@apache.org>:

Of course I meant bug fixes, not bugs :)

On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura <

ag...@apache.org>

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 <

jokse...@gmail.com

wrote:

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 <

eshangar...@gridgain.com

:

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 <

ivan.glu...@gmail.com

wrote:

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

erthehood-WALcompaction
Please take a look - it has all the answers.

Best Regards,
Ivan Rakov


On 27.04.2018 2:28, Dmitriy Setrakyan wrote:


On Fri

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

[Yury Babak]

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: Apache Ignite 2.5 release

[Vladimir Ozerov]

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, Andrey!
>
> On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:
>
> > 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 and I think we should include it in 2.5.
> > Users
> > > are complaining [2].
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > > [2]
> > > http://apache-ignite-users.70518.x6.nabble.com/Re-
> > Service-Grid-and-net-core-2-td21318.html
> > >
> > > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
> > > wrote:
> > >
> > >> 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] https://issues.apache.org/jira/browse/IGNITE-4150
> > >>
> > >> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
> > >>
> > >> > Ivan,
> > >> >
> > >> > ok, targeted to 2.5. Thanks!
> > >> >
> > >> > On Mon, May 7, 2018 at 5:24 PM, Dmitry Pavlov <
> dpavlov@gmail.com>
> > >> > wrote:
> > >> > > 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:
> > >> > > http://apache-ignite-developers.2346864.n4.nabble.
> > >> > com/Apache-Ignite-2-5-release-td28927i20.html#a30155
> > >> > > but here Yuriy Babak probably should share his opinion.
> > >> > >
> > >> > > Sincerely,
> > >> > > Dmitriy Pavlov
> > >> > >
> > >> > > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
> > >> > >>
> > >> > >> Sergey, Dmitry,
> > >> > >>
> > >> > >> I've targeted your issues to 2.5 release.
> > >> > >>
> > >> > >> Thanks!
> > >> > >>
> > >> > >> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
> > dpavlov@gmail.com>
> > >> > >> 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 no response I can cherry-pick anything to
> 2.5
> > >> > hoping
> > >> > >> > it
> > >> > >> > is lazy consensus; no one objected.
> > >> > >> >
> > >> > >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
> > >> > >> >
> > >> > >> >> 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 <
> > >> dpavlov@gmail.com
> > >> > >
> > >> > >> >> wrote:
> > >> > >> >>
> > >> > >> >> > 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
> > >> > >> >> >
> > >> > >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
> > >> > >> >> >  > >> > >> >> >:
> > >> > >> >> >
> > >> > >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> > >> > >> >> > >
> > >> > >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> > >> > >> >> > > alexey.scherbak...@gmail.com> wrote:
> > >> > >> >> > >
> > >> > >>

Re: Apache Ignite 2.5 release

[Pavel Tupitsyn]

IGNITE-8434 merged to master, cherry-picked to ignite-2.5.

Thank you, Andrey!

On Mon, May 7, 2018 at 10:46 PM, Andrey Gura  wrote:

> 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 and I think we should include it in 2.5.
> Users
> > are complaining [2].
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8434
> > [2]
> > http://apache-ignite-users.70518.x6.nabble.com/Re-
> Service-Grid-and-net-core-2-td21318.html
> >
> > On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
> > wrote:
> >
> >> 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] https://issues.apache.org/jira/browse/IGNITE-4150
> >>
> >> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
> >>
> >> > 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
> >> > > 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:
> >> > > http://apache-ignite-developers.2346864.n4.nabble.
> >> > com/Apache-Ignite-2-5-release-td28927i20.html#a30155
> >> > > but here Yuriy Babak probably should share his opinion.
> >> > >
> >> > > Sincerely,
> >> > > Dmitriy Pavlov
> >> > >
> >> > > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
> >> > >>
> >> > >> Sergey, Dmitry,
> >> > >>
> >> > >> I've targeted your issues to 2.5 release.
> >> > >>
> >> > >> Thanks!
> >> > >>
> >> > >> On Fri, May 4, 2018 at 5:51 PM, Dmitry Pavlov <
> dpavlov@gmail.com>
> >> > >> 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 no response I can cherry-pick anything to 2.5
> >> > hoping
> >> > >> > it
> >> > >> > is lazy consensus; no one objected.
> >> > >> >
> >> > >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
> >> > >> >
> >> > >> >> 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 <
> >> dpavlov@gmail.com
> >> > >
> >> > >> >> wrote:
> >> > >> >>
> >> > >> >> > 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
> >> > >> >> >
> >> > >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
> >> > >> >> >  >> > >> >> >:
> >> > >> >> >
> >> > >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> >> > >> >> > >
> >> > >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> >> > >> >> > > alexey.scherbak...@gmail.com> wrote:
> >> > >> >> > >
> >> > >> >> > > > 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 <
> ag...@apache.org>:
> >> > >> >> > > >
> >> > >> >> > > > > Of course I meant bug

Re: Apache Ignite 2.5 release

[Andrey Gura]

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 and I think we should include it in 2.5. Users
> are complaining [2].
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8434
> [2]
> http://apache-ignite-users.70518.x6.nabble.com/Re-Service-Grid-and-net-core-2-td21318.html
>
> On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
> wrote:
>
>> 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] https://issues.apache.org/jira/browse/IGNITE-4150
>>
>> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
>>
>> > 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
>> > > 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:
>> > > http://apache-ignite-developers.2346864.n4.nabble.
>> > com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>> > > but here Yuriy Babak probably should share his opinion.
>> > >
>> > > Sincerely,
>> > > Dmitriy Pavlov
>> > >
>> > > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>> > >>
>> > >> 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 no response I can cherry-pick anything to 2.5
>> > hoping
>> > >> > it
>> > >> > is lazy consensus; no one objected.
>> > >> >
>> > >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
>> > >> >
>> > >> >> 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 <
>> dpavlov@gmail.com
>> > >
>> > >> >> wrote:
>> > >> >>
>> > >> >> > 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
>> > >> >> >
>> > >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
>> > >> >> > > > >> >> >:
>> > >> >> >
>> > >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
>> > >> >> > >
>> > >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
>> > >> >> > > alexey.scherbak...@gmail.com> wrote:
>> > >> >> > >
>> > >> >> > > > 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 fixes, not bugs :)
>> > >> >> > > > >
>> > >> >> > > > > On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura <
>> > ag...@apache.org>
>> > >> >> > 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

[Andrey Gura]

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 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] https://issues.apache.org/jira/browse/IGNITE-4150
>
> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
>>
>> 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
>> >
>> > 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:
>> >
>> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-5-release-td28927i20.html#a30155
>> > but here Yuriy Babak probably should share his opinion.
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>> >>
>> >> 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 no response I can cherry-pick anything to 2.5
>> >> > hoping
>> >> > it
>> >> > is lazy consensus; no one objected.
>> >> >
>> >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
>> >> >
>> >> >> 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:
>> >> >>
>> >> >> > 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
>> >> >> >
>> >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
>> >> >> > > >> >> >:
>> >> >> >
>> >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
>> >> >> > >
>> >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
>> >> >> > > alexey.scherbak...@gmail.com> wrote:
>> >> >> > >
>> >> >> > > > 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 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 <
>> >> >> > jokse...@gmail.com
>> >> >> > > >
>> >> >> > > > > wrote:
>> >> >> > > > > >> 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 <
>> >> >> > > > eshangar...@gridgain.com
>> >> >> > > > > >:
>> >> >> > > > > >>
>> >> >> > > > > >>> Guys,
>> >> >> > > > > >>> I have finished
>> >> >> > > > > >>> ttps://issues.apache.org/jira/browse/IGNITE-7628.
>> >> 

Re: Apache Ignite 2.5 release

[Pavel Tupitsyn]

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]
http://apache-ignite-users.70518.x6.nabble.com/Re-Service-Grid-and-net-core-2-td21318.html

On Mon, May 7, 2018 at 6:44 PM, Vladimir Ozerov 
wrote:

> 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] https://issues.apache.org/jira/browse/IGNITE-4150
>
> On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:
>
> > 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
> > > 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:
> > > http://apache-ignite-developers.2346864.n4.nabble.
> > com/Apache-Ignite-2-5-release-td28927i20.html#a30155
> > > but here Yuriy Babak probably should share his opinion.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
> > >>
> > >> 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 no response I can cherry-pick anything to 2.5
> > hoping
> > >> > it
> > >> > is lazy consensus; no one objected.
> > >> >
> > >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
> > >> >
> > >> >> 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 <
> dpavlov@gmail.com
> > >
> > >> >> wrote:
> > >> >>
> > >> >> > 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
> > >> >> >
> > >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
> > >> >> >  > >> >> >:
> > >> >> >
> > >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> > >> >> > >
> > >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> > >> >> > > alexey.scherbak...@gmail.com> wrote:
> > >> >> > >
> > >> >> > > > 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 fixes, not bugs :)
> > >> >> > > > >
> > >> >> > > > > On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura <
> > ag...@apache.org>
> > >> >> > 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 <
> > >> >> > jokse...@gmail.com
> > >> >> > > >
> > >> >> > > > > wrote:
> > >> >> > > > > >> Igniters,
> > >> >> > > > > >>
> > >> >> > > > > >> I would like to add this issue
> > >> >> > > > > >> https://issues.apache.org/jira/browse/IGNITE-8405 to
> 2.5
> > >> >> > > > > >>

Re: Apache Ignite 2.5 release

[Vladimir Ozerov]

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] https://issues.apache.org/jira/browse/IGNITE-4150

On Mon, May 7, 2018 at 6:07 PM, Andrey Gura  wrote:

> 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
> > 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:
> > http://apache-ignite-developers.2346864.n4.nabble.
> com/Apache-Ignite-2-5-release-td28927i20.html#a30155
> > but here Yuriy Babak probably should share his opinion.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 7 мая 2018 г. в 17:09, Andrey Gura :
> >>
> >> 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 no response I can cherry-pick anything to 2.5
> hoping
> >> > it
> >> > is lazy consensus; no one objected.
> >> >
> >> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
> >> >
> >> >> 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:
> >> >>
> >> >> > 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
> >> >> >
> >> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
> >> >> >  >> >> >:
> >> >> >
> >> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> >> >> > >
> >> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> >> >> > > alexey.scherbak...@gmail.com> wrote:
> >> >> > >
> >> >> > > > 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 fixes, not bugs :)
> >> >> > > > >
> >> >> > > > > On Fri, Apr 27, 2018 at 9:28 PM, Andrey Gura <
> ag...@apache.org>
> >> >> > 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 <
> >> >> > jokse...@gmail.com
> >> >> > > >
> >> >> > > > > wrote:
> >> >> > > > > >> 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 <
> >> >> > > > eshangar...@gridgain.com
> >> >> > > > > >:
> >> >> > > > > >>
> >> >> > > > > >>> 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 <
> >> >> > ivan.glu...@gmail.com
> >> >> > > >
> >> >> > > > > wrote:
> >> >> > > > > >>>
> >> >> > > > > >>> > Dmitriy,
> >> >> > > > > >>> >
> >> >> > > > > >>> > There are some notes about WAL compaction in
> "Persistence
> >> >> Under
> >> >> > > th

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

[Andrey Gura]

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 1:39 AM, techbysample  wrote:
> 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 Grid example that
> solves 'Knapsack Problem'
>
>
> Please advise.
>
> Best,
> Turik
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Apache Ignite 2.5 release

[Andrey Gura]

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
> 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:
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-5-release-td28927i20.html#a30155
> but here Yuriy Babak probably should share his opinion.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 7 мая 2018 г. в 17:09, Andrey Gura :
>>
>> 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 no response I can cherry-pick anything to 2.5 hoping
>> > it
>> > is lazy consensus; no one objected.
>> >
>> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
>> >
>> >> 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:
>> >>
>> >> > 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
>> >> >
>> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov
>> >> > > >> >:
>> >> >
>> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
>> >> > >
>> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
>> >> > > alexey.scherbak...@gmail.com> wrote:
>> >> > >
>> >> > > > 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 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 <
>> >> > jokse...@gmail.com
>> >> > > >
>> >> > > > > wrote:
>> >> > > > > >> 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 <
>> >> > > > eshangar...@gridgain.com
>> >> > > > > >:
>> >> > > > > >>
>> >> > > > > >>> 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 <
>> >> > ivan.glu...@gmail.com
>> >> > > >
>> >> > > > > wrote:
>> >> > > > > >>>
>> >> > > > > >>> > 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-und
>> >> > > > > >>> > erthehood-WALcompaction
>> >> > > > > >>> > Please take a look - it has all the answers.
>> >> > > > > >>> >
>> >> > > > > >>> > Best Regards,
>> >> > > > > >>> > Ivan Rakov
>> >> > > > > >>> >
>> >> > > > > >>> >
>> >> > > > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
>> >> > > > > >>> >
>> >> > > > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
>> >> > > > ivan.glu...@gmail.com>
>> >> > > > > >>> >> wrote:
>> >> > > > > >>> >>
>> >> > > > > >>> >> Folks,
>> >> > > > >

Re: Apache Ignite 2.5 release

[Dmitry Pavlov]

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:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-5-release-td28927i20.html#a30155
but here Yuriy Babak probably should share his opinion.

Sincerely,
Dmitriy Pavlov

пн, 7 мая 2018 г. в 17:09, Andrey Gura :

> 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 no response I can cherry-pick anything to 2.5 hoping
> it
> > is lazy consensus; no one objected.
> >
> > пт, 4 мая 2018 г. в 17:44, Denis Magda :
> >
> >> 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:
> >>
> >> > 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
> >> >
> >> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov <
> sergey.chugu...@gmail.com
> >> >:
> >> >
> >> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> >> > >
> >> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> >> > > alexey.scherbak...@gmail.com> wrote:
> >> > >
> >> > > > 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 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 <
> >> > jokse...@gmail.com
> >> > > >
> >> > > > > wrote:
> >> > > > > >> 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 <
> >> > > > eshangar...@gridgain.com
> >> > > > > >:
> >> > > > > >>
> >> > > > > >>> 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 <
> >> > ivan.glu...@gmail.com
> >> > > >
> >> > > > > wrote:
> >> > > > > >>>
> >> > > > > >>> > 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-und
> >> > > > > >>> > erthehood-WALcompaction
> >> > > > > >>> > Please take a look - it has all the answers.
> >> > > > > >>> >
> >> > > > > >>> > Best Regards,
> >> > > > > >>> > Ivan Rakov
> >> > > > > >>> >
> >> > > > > >>> >
> >> > > > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> >> > > > > >>> >
> >> > > > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
> >> > > > ivan.glu...@gmail.com>
> >> > > > > >>> >> 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
> >> > >

Re: Apache Ignite 2.5 release

[Ivan Rakov]

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 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 no response I can cherry-pick anything to 2.5 hoping it
is lazy consensus; no one objected.

пт, 4 мая 2018 г. в 17:44, Denis Magda :


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:


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

сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov 
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] https://issues.apache.org/jira/browse/IGNITE-8421

On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:


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

jokse...@gmail.com

wrote:

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 <

eshangar...@gridgain.com

:

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 <

ivan.glu...@gmail.com

wrote:

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-und
erthehood-WALcompaction
Please take a look - it has all the answers.

Best Regards,
Ivan Rakov


On 27.04.2018 2:28, Dmitriy Setrakyan wrote:


On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <

ivan.glu...@gmail.com>

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 warnings in infinite loop.
I think it's also worth being included in 2.5 release.

Let's include it, especially given that the fix is done.

Ivan, on another note, is WAL compaction described anywhere?

What

do we

do

internally to compact WAL and by what factor are we able to

reduce

the

WAL

file size?

D.




--
Best regards,
Eduard.



--

Best regards,
Alexei Scherbakov

Re: Apache Ignite 2.5 release

[Andrey Gura]

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 no response I can cherry-pick anything to 2.5 hoping it
> is lazy consensus; no one objected.
>
> пт, 4 мая 2018 г. в 17:44, Denis Magda :
>
>> 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:
>>
>> > 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
>> >
>> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov > >:
>> >
>> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
>> > >
>> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
>> > > alexey.scherbak...@gmail.com> wrote:
>> > >
>> > > > 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 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 <
>> > jokse...@gmail.com
>> > > >
>> > > > > wrote:
>> > > > > >> 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 <
>> > > > eshangar...@gridgain.com
>> > > > > >:
>> > > > > >>
>> > > > > >>> 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 <
>> > ivan.glu...@gmail.com
>> > > >
>> > > > > wrote:
>> > > > > >>>
>> > > > > >>> > 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-und
>> > > > > >>> > erthehood-WALcompaction
>> > > > > >>> > Please take a look - it has all the answers.
>> > > > > >>> >
>> > > > > >>> > Best Regards,
>> > > > > >>> > Ivan Rakov
>> > > > > >>> >
>> > > > > >>> >
>> > > > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
>> > > > > >>> >
>> > > > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
>> > > > ivan.glu...@gmail.com>
>> > > > > >>> >> 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 warnings in infinite loop.
>> > > > > >>> >>> I think it's also worth being included in 2.5 release.
>> > > > > >>> >>>
>> > > > > >>> >>> Let's include it, especially given that the fix is done.
>> > > > > >>> >>
>> > > > > >>> >> Ivan, on another note, is WAL compaction described anywhere?
>> > > What
>> > > > > do we
>> > > > > >>> do
>> > > > > >>> >> internally to compact WAL and by what factor are we able to
>> > > reduce
>> > > > > the
>> > > > > >>> WAL
>> > > > > >>> >> file size?
>> > > > > >>> >>
>> > > > > >>> >> D.
>> > > > > >>> >>
>> > > > > >>> >>
>> > > > > >>> >
>> > > > > >>>
>> > > > > >>>
>> > > > > >>> --
>> > > > > >>> Best regards,
>> > > > > >>> Eduard.
>> > > > > >>>
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > >
>> > > > Best regards,

Re: Apache Ignite 2.5 release

[Dmitry Pavlov]

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 :

> 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:
>
> > 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
> >
> > сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov  >:
> >
> > > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> > >
> > > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> > > alexey.scherbak...@gmail.com> wrote:
> > >
> > > > 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 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 <
> > jokse...@gmail.com
> > > >
> > > > > wrote:
> > > > > >> 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 <
> > > > eshangar...@gridgain.com
> > > > > >:
> > > > > >>
> > > > > >>> 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 <
> > ivan.glu...@gmail.com
> > > >
> > > > > wrote:
> > > > > >>>
> > > > > >>> > 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-und
> > > > > >>> > erthehood-WALcompaction
> > > > > >>> > Please take a look - it has all the answers.
> > > > > >>> >
> > > > > >>> > Best Regards,
> > > > > >>> > Ivan Rakov
> > > > > >>> >
> > > > > >>> >
> > > > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> > > > > >>> >
> > > > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
> > > > ivan.glu...@gmail.com>
> > > > > >>> >> 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 warnings in infinite loop.
> > > > > >>> >>> I think it's also worth being included in 2.5 release.
> > > > > >>> >>>
> > > > > >>> >>> Let's include it, especially given that the fix is done.
> > > > > >>> >>
> > > > > >>> >> Ivan, on another note, is WAL compaction described anywhere?
> > > What
> > > > > do we
> > > > > >>> do
> > > > > >>> >> internally to compact WAL and by what factor are we able to
> > > reduce
> > > > > the
> > > > > >>> WAL
> > > > > >>> >> file size?
> > > > > >>> >>
> > > > > >>> >> D.
> > > > > >>> >>
> > > > > >>> >>
> > > > > >>> >
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> Best regards,
> > > > > >>> Eduard.
> > > > > >>>
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Best regards,
> > > > Alexei Scherbakov
> > > >
> > >
> >
>

Re: Apache Ignite 2.5 release

[Denis Magda]

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:

> 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
>
> сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov :
>
> > 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] https://issues.apache.org/jira/browse/IGNITE-8421
> >
> > On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> > alexey.scherbak...@gmail.com> wrote:
> >
> > > 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 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 <
> jokse...@gmail.com
> > >
> > > > wrote:
> > > > >> 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 <
> > > eshangar...@gridgain.com
> > > > >:
> > > > >>
> > > > >>> 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 <
> ivan.glu...@gmail.com
> > >
> > > > wrote:
> > > > >>>
> > > > >>> > 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-und
> > > > >>> > erthehood-WALcompaction
> > > > >>> > Please take a look - it has all the answers.
> > > > >>> >
> > > > >>> > Best Regards,
> > > > >>> > Ivan Rakov
> > > > >>> >
> > > > >>> >
> > > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> > > > >>> >
> > > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
> > > ivan.glu...@gmail.com>
> > > > >>> >> 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 warnings in infinite loop.
> > > > >>> >>> I think it's also worth being included in 2.5 release.
> > > > >>> >>>
> > > > >>> >>> Let's include it, especially given that the fix is done.
> > > > >>> >>
> > > > >>> >> Ivan, on another note, is WAL compaction described anywhere?
> > What
> > > > do we
> > > > >>> do
> > > > >>> >> internally to compact WAL and by what factor are we able to
> > reduce
> > > > the
> > > > >>> WAL
> > > > >>> >> file size?
> > > > >>> >>
> > > > >>> >> D.
> > > > >>> >>
> > > > >>> >>
> > > > >>> >
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> Best regards,
> > > > >>> Eduard.
> > > > >>>
> > > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> > >
> >
>

Re: Apache Ignite 2.5 release

[Dmitry Pavlov]

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

сб, 28 апр. 2018 г. в 19:49, Sergey Chugunov :

> 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] https://issues.apache.org/jira/browse/IGNITE-8421
>
> On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > 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 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  >
> > > wrote:
> > > >> 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 <
> > eshangar...@gridgain.com
> > > >:
> > > >>
> > > >>> 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:
> > https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
> > > >>> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
> > > >>> > erthehood-WALcompaction
> > > >>> > Please take a look - it has all the answers.
> > > >>> >
> > > >>> > Best Regards,
> > > >>> > Ivan Rakov
> > > >>> >
> > > >>> >
> > > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> > > >>> >
> > > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
> > ivan.glu...@gmail.com>
> > > >>> >> 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 warnings in infinite loop.
> > > >>> >>> I think it's also worth being included in 2.5 release.
> > > >>> >>>
> > > >>> >>> Let's include it, especially given that the fix is done.
> > > >>> >>
> > > >>> >> Ivan, on another note, is WAL compaction described anywhere?
> What
> > > do we
> > > >>> do
> > > >>> >> internally to compact WAL and by what factor are we able to
> reduce
> > > the
> > > >>> WAL
> > > >>> >> file size?
> > > >>> >>
> > > >>> >> D.
> > > >>> >>
> > > >>> >>
> > > >>> >
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Best regards,
> > > >>> Eduard.
> > > >>>
> > >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
> >
>

Re: Apache Ignite 2.5 release

[Sergey Chugunov]

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] https://issues.apache.org/jira/browse/IGNITE-8421

On Sat, Apr 28, 2018 at 6:08 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:

> 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 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 
> > wrote:
> > >> 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 <
> eshangar...@gridgain.com
> > >:
> > >>
> > >>> 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:
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
> > >>> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
> > >>> > erthehood-WALcompaction
> > >>> > Please take a look - it has all the answers.
> > >>> >
> > >>> > Best Regards,
> > >>> > Ivan Rakov
> > >>> >
> > >>> >
> > >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> > >>> >
> > >>> >> On Fri, Apr 27, 2018 at 6:38 AM, Ivan Rakov <
> ivan.glu...@gmail.com>
> > >>> >> 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 warnings in infinite loop.
> > >>> >>> I think it's also worth being included in 2.5 release.
> > >>> >>>
> > >>> >>> Let's include it, especially given that the fix is done.
> > >>> >>
> > >>> >> Ivan, on another note, is WAL compaction described anywhere? What
> > do we
> > >>> do
> > >>> >> internally to compact WAL and by what factor are we able to reduce
> > the
> > >>> WAL
> > >>> >> file size?
> > >>> >>
> > >>> >> D.
> > >>> >>
> > >>> >>
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Best regards,
> > >>> Eduard.
> > >>>
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>

Re: Apache Ignite 2.5 release

[Alexei Scherbakov]

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 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 
> wrote:
> >> 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 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: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
> >>> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
> >>> > erthehood-WALcompaction
> >>> > Please take a look - it has all the answers.
> >>> >
> >>> > Best Regards,
> >>> > Ivan Rakov
> >>> >
> >>> >
> >>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> >>> >
> >>> >> 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 warnings in infinite loop.
> >>> >>> I think it's also worth being included in 2.5 release.
> >>> >>>
> >>> >>> Let's include it, especially given that the fix is done.
> >>> >>
> >>> >> Ivan, on another note, is WAL compaction described anywhere? What
> do we
> >>> do
> >>> >> internally to compact WAL and by what factor are we able to reduce
> the
> >>> WAL
> >>> >> file size?
> >>> >>
> >>> >> D.
> >>> >>
> >>> >>
> >>> >
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Eduard.
> >>>
>


-- 

Best regards,
Alexei Scherbakov

Re: Apache Ignite 2.5 release

[Andrey Gura]

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  wrote:
>> 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 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: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
>>> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
>>> > erthehood-WALcompaction
>>> > Please take a look - it has all the answers.
>>> >
>>> > Best Regards,
>>> > Ivan Rakov
>>> >
>>> >
>>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
>>> >
>>> >> 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 warnings in infinite loop.
>>> >>> I think it's also worth being included in 2.5 release.
>>> >>>
>>> >>> Let's include it, especially given that the fix is done.
>>> >>
>>> >> Ivan, on another note, is WAL compaction described anywhere? What do we
>>> do
>>> >> internally to compact WAL and by what factor are we able to reduce the
>>> WAL
>>> >> file size?
>>> >>
>>> >> D.
>>> >>
>>> >>
>>> >
>>>
>>>
>>> --
>>> Best regards,
>>> Eduard.
>>>

Re: Apache Ignite 2.5 release

[Andrey Gura]

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.
>
>
> 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 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: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
>> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
>> > erthehood-WALcompaction
>> > Please take a look - it has all the answers.
>> >
>> > Best Regards,
>> > Ivan Rakov
>> >
>> >
>> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
>> >
>> >> 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 warnings in infinite loop.
>> >>> I think it's also worth being included in 2.5 release.
>> >>>
>> >>> Let's include it, especially given that the fix is done.
>> >>
>> >> Ivan, on another note, is WAL compaction described anywhere? What do we
>> do
>> >> internally to compact WAL and by what factor are we able to reduce the
>> WAL
>> >> file size?
>> >>
>> >> D.
>> >>
>> >>
>> >
>>
>>
>> --
>> Best regards,
>> Eduard.
>>

Re: Apache Ignite 2.5 release

[Pavel Kovalenko]

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 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: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
> > Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
> > erthehood-WALcompaction
> > Please take a look - it has all the answers.
> >
> > Best Regards,
> > Ivan Rakov
> >
> >
> > On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
> >
> >> 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 warnings in infinite loop.
> >>> I think it's also worth being included in 2.5 release.
> >>>
> >>> Let's include it, especially given that the fix is done.
> >>
> >> Ivan, on another note, is WAL compaction described anywhere? What do we
> do
> >> internally to compact WAL and by what factor are we able to reduce the
> WAL
> >> file size?
> >>
> >> D.
> >>
> >>
> >
>
>
> --
> Best regards,
> Eduard.
>

Re: Apache Ignite 2.5 release

[Eduard Shangareev]

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: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+
> Persistent+Store+-+under+the+hood#IgnitePersistentStore-und
> erthehood-WALcompaction
> Please take a look - it has all the answers.
>
> Best Regards,
> Ivan Rakov
>
>
> On 27.04.2018 2:28, Dmitriy Setrakyan wrote:
>
>> 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 warnings in infinite loop.
>>> I think it's also worth being included in 2.5 release.
>>>
>>> Let's include it, especially given that the fix is done.
>>
>> Ivan, on another note, is WAL compaction described anywhere? What do we do
>> internally to compact WAL and by what factor are we able to reduce the WAL
>> file size?
>>
>> D.
>>
>>
>


-- 
Best regards,
Eduard.

Re: Apache Ignite 2.5 release

[Ivan Rakov]

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

On 27.04.2018 2:28, Dmitriy Setrakyan wrote:

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 warnings in infinite loop.
I think it's also worth being included in 2.5 release.


Let's include it, especially given that the fix is done.

Ivan, on another note, is WAL compaction described anywhere? What do we do
internally to compact WAL and by what factor are we able to reduce the WAL
file size?

D.

Re: Apache Ignite 2.5 release

[Andrey Gura]

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 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 warnings in infinite loop.
> > I think it's also worth being included in 2.5 release.
> >
>
> Let's include it, especially given that the fix is done.
>
> Ivan, on another note, is WAL compaction described anywhere? What do we do
> internally to compact WAL and by what factor are we able to reduce the WAL
> file size?
>
> D.
>

Re: Apache Ignite 2.5 release

[Dmitriy Setrakyan]

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 warnings in infinite loop.
> I think it's also worth being included in 2.5 release.
>

Let's include it, especially given that the fix is done.

Ivan, on another note, is WAL compaction described anywhere? What do we do
internally to compact WAL and by what factor are we able to reduce the WAL
file size?

D.

Re: Apache Ignite 2.5 release

[Ivan Rakov]

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 warnings in infinite loop.

I think it's also worth being included in 2.5 release.

Best Regards,
Ivan Rakov

On 26.04.2018 19:54, Igor Sapego wrote:

Cool, I've cherry-picked it to ignite-2.5 from master.

Best Regards,
Igor

On Thu, Apr 26, 2018 at 7:48 PM, Andrey Gura  wrote:


Igor,

Feel free to target ticket to 2.5 release.

Thanks!

On Thu, Apr 26, 2018 at 7:45 PM, Igor Sapego  wrote:

Hi guys,
I also have fix for a critical bug [1] which I'd like to include
in this release. It is OK?

[1] - https://issues.apache.org/jira/browse/IGNITE-8394

Best Regards,
Igor

On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura  wrote:


Pavel,

looks like painful problem. I've targeted it to 2.5 release.

Thanks!

On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov 
wrote:

Hi Pavel,

+1 from me, assertion in GridCachePartitionExchangeManager is to be

fixed

before release.

Sincerely,
Dmitriy Pavlov

ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :


Igniters,

I've found blocker issue https://issues.apache.org/

jira/browse/IGNITE-8390

Cause of the problem is incorrect assertion that could be fixed very
quickly.
I would like to add this issue to 2.5 release.

2018-04-25 17:38 GMT+03:00 Andrey Gura :


Igniters,

We have about 30 JIRA issues that still aren't resolved. So it's
possible that release date will be changed.

But I think that it's time for scope freeze. Please, don't target

any

issues to 2.5 version without community approve.

Thanks.

On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 

wrote:

Andrey, thanks for control :)

So, You'll fix broken versions eventually?

BTW, I don't think it's a good idea to merge issues with fix

version

2.5

to

ignite-2.5. Good way is to fix version to 2.6 instead.

2018-04-12 21:34 GMT+03:00 Andrey Gura :


Anton,

all is under control.

Branches will be compared and changes that should be included

to AI

2.5 will be identified.

On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov <

mr.wei...@gmail.com>

wrote:

Possibly it is Andrey Gura — he initiated this thread and

created

corresponding branch.



On 12 Apr 2018, at 17:39, Anton Vinogradov 

wrote:

Release manager is responsible for this change.
Do we have release manager for 2.5?

2018-04-12 17:35 GMT+03:00 Dmitry Pavlov <

dpavlov@gmail.com

:

I've changed my ticket version assignment, and a lot of

Igniters

changed.

Filter for double-check tickets related to you
*https://issues.apache.org/jira/issues/?jql=project%
3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
20reporter%3DcurrentUser())
*


чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov <

a...@apache.org>:

Folks,
I see a lot of issues 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?

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.




On 5 Apr 2018, at 21:55, Denis Magda 

wrote:

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 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, 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 check JIRA issues assigned to you and move

it

to

the

next

version if this issues shouldn't be included to 2.5

release.

Release page on wiki [1] contains all issues targeted

to

2.5

(fix

version field).

[1] https://cwiki.apache.org/

confluence/display/IGNITE/

Apache+Ignite+2.5

Re: Apache Ignite 2.5 release

[Igor Sapego]

Cool, I've cherry-picked it to ignite-2.5 from master.

Best Regards,
Igor

On Thu, Apr 26, 2018 at 7:48 PM, Andrey Gura  wrote:

> Igor,
>
> Feel free to target ticket to 2.5 release.
>
> Thanks!
>
> On Thu, Apr 26, 2018 at 7:45 PM, Igor Sapego  wrote:
> > Hi guys,
> > I also have fix for a critical bug [1] which I'd like to include
> > in this release. It is OK?
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-8394
> >
> > Best Regards,
> > Igor
> >
> > On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura  wrote:
> >
> >> Pavel,
> >>
> >> looks like painful problem. I've targeted it to 2.5 release.
> >>
> >> Thanks!
> >>
> >> On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov 
> >> wrote:
> >> > Hi Pavel,
> >> >
> >> > +1 from me, assertion in GridCachePartitionExchangeManager is to be
> >> fixed
> >> > before release.
> >> >
> >> > Sincerely,
> >> > Dmitriy Pavlov
> >> >
> >> > ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :
> >> >
> >> >> Igniters,
> >> >>
> >> >> I've found blocker issue https://issues.apache.org/
> >> jira/browse/IGNITE-8390
> >> >> Cause of the problem is incorrect assertion that could be fixed very
> >> >> quickly.
> >> >> I would like to add this issue to 2.5 release.
> >> >>
> >> >> 2018-04-25 17:38 GMT+03:00 Andrey Gura :
> >> >>
> >> >> > Igniters,
> >> >> >
> >> >> > We have about 30 JIRA issues that still aren't resolved. So it's
> >> >> > possible that release date will be changed.
> >> >> >
> >> >> > But I think that it's time for scope freeze. Please, don't target
> any
> >> >> > issues to 2.5 version without community approve.
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 
> >> >> wrote:
> >> >> > > Andrey, thanks for control :)
> >> >> > >
> >> >> > > So, You'll fix broken versions eventually?
> >> >> > >
> >> >> > > BTW, I don't think it's a good idea to merge issues with fix
> version
> >> >> 2.5
> >> >> > to
> >> >> > > ignite-2.5. Good way is to fix version to 2.6 instead.
> >> >> > >
> >> >> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
> >> >> > >
> >> >> > >> Anton,
> >> >> > >>
> >> >> > >> all is under control.
> >> >> > >>
> >> >> > >> Branches will be compared and changes that should be included
> to AI
> >> >> > >> 2.5 will be identified.
> >> >> > >>
> >> >> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov <
> mr.wei...@gmail.com>
> >> >> > wrote:
> >> >> > >> > Possibly it is Andrey Gura — he initiated this thread and
> created
> >> >> > >> corresponding branch.
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov 
> >> wrote:
> >> >> > >> >>
> >> >> > >> >> Release manager is responsible for this change.
> >> >> > >> >> Do we have release manager for 2.5?
> >> >> > >> >>
> >> >> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov <
> dpavlov@gmail.com
> >> >:
> >> >> > >> >>
> >> >> > >> >>> I've changed my ticket version assignment, and a lot of
> >> Igniters
> >> >> > >> changed.
> >> >> > >> >>>
> >> >> > >> >>> Filter for double-check tickets related to you
> >> >> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
> >> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> >> > >> >>> 20reporter%3DcurrentUser())
> >> >> > >> >>>  >> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> >> > >> >>> 20reporter%3DcurrentUser())>*
> >> >> > >> >>>
> >> >> > >> >>>
> >> >> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov <
> a...@apache.org>:
> >> >> > >> >>>
> >> >> > >>  Folks,
> >> >> > >>  I see a lot of issues 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?
> >> >> > >> 
> >> >> > >>  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.
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >> On 5 Apr 2018, at 21:55, Denis Magda 
> >> >> wrote:
> >> >> > >> >>
> >> >> > >> >> 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 I

Re: Apache Ignite 2.5 release

[Andrey Gura]

Igor,

Feel free to target ticket to 2.5 release.

Thanks!

On Thu, Apr 26, 2018 at 7:45 PM, Igor Sapego  wrote:
> Hi guys,
> I also have fix for a critical bug [1] which I'd like to include
> in this release. It is OK?
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-8394
>
> Best Regards,
> Igor
>
> On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura  wrote:
>
>> Pavel,
>>
>> looks like painful problem. I've targeted it to 2.5 release.
>>
>> Thanks!
>>
>> On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov 
>> wrote:
>> > Hi Pavel,
>> >
>> > +1 from me, assertion in GridCachePartitionExchangeManager is to be
>> fixed
>> > before release.
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :
>> >
>> >> Igniters,
>> >>
>> >> I've found blocker issue https://issues.apache.org/
>> jira/browse/IGNITE-8390
>> >> Cause of the problem is incorrect assertion that could be fixed very
>> >> quickly.
>> >> I would like to add this issue to 2.5 release.
>> >>
>> >> 2018-04-25 17:38 GMT+03:00 Andrey Gura :
>> >>
>> >> > Igniters,
>> >> >
>> >> > We have about 30 JIRA issues that still aren't resolved. So it's
>> >> > possible that release date will be changed.
>> >> >
>> >> > But I think that it's time for scope freeze. Please, don't target any
>> >> > issues to 2.5 version without community approve.
>> >> >
>> >> > Thanks.
>> >> >
>> >> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 
>> >> wrote:
>> >> > > Andrey, thanks for control :)
>> >> > >
>> >> > > So, You'll fix broken versions eventually?
>> >> > >
>> >> > > BTW, I don't think it's a good idea to merge issues with fix version
>> >> 2.5
>> >> > to
>> >> > > ignite-2.5. Good way is to fix version to 2.6 instead.
>> >> > >
>> >> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
>> >> > >
>> >> > >> Anton,
>> >> > >>
>> >> > >> all is under control.
>> >> > >>
>> >> > >> Branches will be compared and changes that should be included to AI
>> >> > >> 2.5 will be identified.
>> >> > >>
>> >> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov 
>> >> > wrote:
>> >> > >> > Possibly it is Andrey Gura — he initiated this thread and created
>> >> > >> corresponding branch.
>> >> > >> >
>> >> > >> >
>> >> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov 
>> wrote:
>> >> > >> >>
>> >> > >> >> Release manager is responsible for this change.
>> >> > >> >> Do we have release manager for 2.5?
>> >> > >> >>
>> >> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov > >:
>> >> > >> >>
>> >> > >> >>> I've changed my ticket version assignment, and a lot of
>> Igniters
>> >> > >> changed.
>> >> > >> >>>
>> >> > >> >>> Filter for double-check tickets related to you
>> >> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
>> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> >> > >> >>> 20reporter%3DcurrentUser())
>> >> > >> >>> > >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> >> > >> >>> 20reporter%3DcurrentUser())>*
>> >> > >> >>>
>> >> > >> >>>
>> >> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>> >> > >> >>>
>> >> > >>  Folks,
>> >> > >>  I see a lot of issues 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?
>> >> > >> 
>> >> > >>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
>> >> > >> 
>> >> > >> > Added corresponding triggers for ignite-2.5 in Ignite Tests
>> 2.4+
>> >> > >> >>> project
>> >> > >> > in TC.
>> >> > >> >
>> >> > >> >
>> >> > >> >
>> >> > >> >> On 5 Apr 2018, at 21:55, Denis Magda 
>> >> wrote:
>> >> > >> >>
>> >> > >> >> 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 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, 2018 at 9:11 PM, Andrey Gura <
>> ag...@apache.org

Re: Apache Ignite 2.5 release

[Igor Sapego]

Hi guys,
I also have fix for a critical bug [1] which I'd like to include
in this release. It is OK?

[1] - https://issues.apache.org/jira/browse/IGNITE-8394

Best Regards,
Igor

On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura  wrote:

> Pavel,
>
> looks like painful problem. I've targeted it to 2.5 release.
>
> Thanks!
>
> On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov 
> wrote:
> > Hi Pavel,
> >
> > +1 from me, assertion in GridCachePartitionExchangeManager is to be
> fixed
> > before release.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :
> >
> >> Igniters,
> >>
> >> I've found blocker issue https://issues.apache.org/
> jira/browse/IGNITE-8390
> >> Cause of the problem is incorrect assertion that could be fixed very
> >> quickly.
> >> I would like to add this issue to 2.5 release.
> >>
> >> 2018-04-25 17:38 GMT+03:00 Andrey Gura :
> >>
> >> > Igniters,
> >> >
> >> > We have about 30 JIRA issues that still aren't resolved. So it's
> >> > possible that release date will be changed.
> >> >
> >> > But I think that it's time for scope freeze. Please, don't target any
> >> > issues to 2.5 version without community approve.
> >> >
> >> > Thanks.
> >> >
> >> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 
> >> wrote:
> >> > > Andrey, thanks for control :)
> >> > >
> >> > > So, You'll fix broken versions eventually?
> >> > >
> >> > > BTW, I don't think it's a good idea to merge issues with fix version
> >> 2.5
> >> > to
> >> > > ignite-2.5. Good way is to fix version to 2.6 instead.
> >> > >
> >> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
> >> > >
> >> > >> Anton,
> >> > >>
> >> > >> all is under control.
> >> > >>
> >> > >> Branches will be compared and changes that should be included to AI
> >> > >> 2.5 will be identified.
> >> > >>
> >> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov 
> >> > wrote:
> >> > >> > Possibly it is Andrey Gura — he initiated this thread and created
> >> > >> corresponding branch.
> >> > >> >
> >> > >> >
> >> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov 
> wrote:
> >> > >> >>
> >> > >> >> Release manager is responsible for this change.
> >> > >> >> Do we have release manager for 2.5?
> >> > >> >>
> >> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov  >:
> >> > >> >>
> >> > >> >>> I've changed my ticket version assignment, and a lot of
> Igniters
> >> > >> changed.
> >> > >> >>>
> >> > >> >>> Filter for double-check tickets related to you
> >> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
> >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> > >> >>> 20reporter%3DcurrentUser())
> >> > >> >>>  >> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> > >> >>> 20reporter%3DcurrentUser())>*
> >> > >> >>>
> >> > >> >>>
> >> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
> >> > >> >>>
> >> > >>  Folks,
> >> > >>  I see a lot of issues 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?
> >> > >> 
> >> > >>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
> >> > >> 
> >> > >> > Added corresponding triggers for ignite-2.5 in Ignite Tests
> 2.4+
> >> > >> >>> project
> >> > >> > in TC.
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >> On 5 Apr 2018, at 21:55, Denis Magda 
> >> wrote:
> >> > >> >>
> >> > >> >> 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 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, 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.
> >> > >> 
> >> > >> 

Re: Apache Ignite 2.5 release

[Andrey Gura]

Pavel,

looks like painful problem. I've targeted it to 2.5 release.

Thanks!

On Wed, Apr 25, 2018 at 8:15 PM, Dmitry Pavlov  wrote:
> Hi Pavel,
>
> +1 from me, assertion in GridCachePartitionExchangeManager is to be fixed
> before release.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :
>
>> Igniters,
>>
>> I've found blocker issue https://issues.apache.org/jira/browse/IGNITE-8390
>> Cause of the problem is incorrect assertion that could be fixed very
>> quickly.
>> I would like to add this issue to 2.5 release.
>>
>> 2018-04-25 17:38 GMT+03:00 Andrey Gura :
>>
>> > Igniters,
>> >
>> > We have about 30 JIRA issues that still aren't resolved. So it's
>> > possible that release date will be changed.
>> >
>> > But I think that it's time for scope freeze. Please, don't target any
>> > issues to 2.5 version without community approve.
>> >
>> > Thanks.
>> >
>> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 
>> wrote:
>> > > Andrey, thanks for control :)
>> > >
>> > > So, You'll fix broken versions eventually?
>> > >
>> > > BTW, I don't think it's a good idea to merge issues with fix version
>> 2.5
>> > to
>> > > ignite-2.5. Good way is to fix version to 2.6 instead.
>> > >
>> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
>> > >
>> > >> Anton,
>> > >>
>> > >> all is under control.
>> > >>
>> > >> Branches will be compared and changes that should be included to AI
>> > >> 2.5 will be identified.
>> > >>
>> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov 
>> > wrote:
>> > >> > Possibly it is Andrey Gura — he initiated this thread and created
>> > >> corresponding branch.
>> > >> >
>> > >> >
>> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
>> > >> >>
>> > >> >> Release manager is responsible for this change.
>> > >> >> Do we have release manager for 2.5?
>> > >> >>
>> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
>> > >> >>
>> > >> >>> I've changed my ticket version assignment, and a lot of Igniters
>> > >> changed.
>> > >> >>>
>> > >> >>> Filter for double-check tickets related to you
>> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
>> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> > >> >>> 20reporter%3DcurrentUser())
>> > >> >>> > > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> > >> >>> 20reporter%3DcurrentUser())>*
>> > >> >>>
>> > >> >>>
>> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>> > >> >>>
>> > >>  Folks,
>> > >>  I see a lot of issues 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?
>> > >> 
>> > >>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
>> > >> 
>> > >> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
>> > >> >>> project
>> > >> > in TC.
>> > >> >
>> > >> >
>> > >> >
>> > >> >> On 5 Apr 2018, at 21:55, Denis Magda 
>> wrote:
>> > >> >>
>> > >> >> 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 > >
>> > >> >>> 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
>> > >> > 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, 2018 at 9:11 PM, Andrey Gura > >
>> > >> >>> 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 check JIRA issues assigned to you and move it to
>> > the
>> > >> >>> next
>> > >>  version if this issues shouldn't be included to 2.5 release.
>> > >> 
>> > >>  Release page on wiki [1] contains all issues targeted to 2.5
>> > (fix
>> > >>  version field).
>> > >> 
>> > >>  [1] https://cwiki.apache.org/confluence/display/IGNITE/
>> > >> > Apache+Ignite+2.5
>> > >> >>>
>> > >> >
>> > >> >

Re: Apache Ignite 2.5 release

[Dmitry Pavlov]

Hi Pavel,

+1 from me, assertion in GridCachePartitionExchangeManager is to be fixed
before release.

Sincerely,
Dmitriy Pavlov

ср, 25 апр. 2018 г. в 20:13, Pavel Kovalenko :

> Igniters,
>
> I've found blocker issue https://issues.apache.org/jira/browse/IGNITE-8390
> Cause of the problem is incorrect assertion that could be fixed very
> quickly.
> I would like to add this issue to 2.5 release.
>
> 2018-04-25 17:38 GMT+03:00 Andrey Gura :
>
> > Igniters,
> >
> > We have about 30 JIRA issues that still aren't resolved. So it's
> > possible that release date will be changed.
> >
> > But I think that it's time for scope freeze. Please, don't target any
> > issues to 2.5 version without community approve.
> >
> > Thanks.
> >
> > On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov 
> wrote:
> > > Andrey, thanks for control :)
> > >
> > > So, You'll fix broken versions eventually?
> > >
> > > BTW, I don't think it's a good idea to merge issues with fix version
> 2.5
> > to
> > > ignite-2.5. Good way is to fix version to 2.6 instead.
> > >
> > > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
> > >
> > >> Anton,
> > >>
> > >> all is under control.
> > >>
> > >> Branches will be compared and changes that should be included to AI
> > >> 2.5 will be identified.
> > >>
> > >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov 
> > wrote:
> > >> > Possibly it is Andrey Gura — he initiated this thread and created
> > >> corresponding branch.
> > >> >
> > >> >
> > >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
> > >> >>
> > >> >> Release manager is responsible for this change.
> > >> >> Do we have release manager for 2.5?
> > >> >>
> > >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
> > >> >>
> > >> >>> I've changed my ticket version assignment, and a lot of Igniters
> > >> changed.
> > >> >>>
> > >> >>> Filter for double-check tickets related to you
> > >> >>> *https://issues.apache.org/jira/issues/?jql=project%
> > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> > >> >>> 20reporter%3DcurrentUser())
> > >> >>>  > >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> > >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> > >> >>> 20reporter%3DcurrentUser())>*
> > >> >>>
> > >> >>>
> > >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
> > >> >>>
> > >>  Folks,
> > >>  I see a lot of issues 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?
> > >> 
> > >>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
> > >> 
> > >> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
> > >> >>> project
> > >> > in TC.
> > >> >
> > >> >
> > >> >
> > >> >> On 5 Apr 2018, at 21:55, Denis Magda 
> wrote:
> > >> >>
> > >> >> 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  >
> > >> >>> 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
> > >> > 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, 2018 at 9:11 PM, Andrey Gura  >
> > >> >>> 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 check JIRA issues assigned to you and move it to
> > the
> > >> >>> next
> > >>  version if this issues shouldn't be included to 2.5 release.
> > >> 
> > >>  Release page on wiki [1] contains all issues targeted to 2.5
> > (fix
> > >>  version field).
> > >> 
> > >>  [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > >> > Apache+Ignite+2.5
> > >> >>>
> > >> >
> > >> >
> > >> 
> > >> >>>
> > >> >
> > >>
> >
>

Re: Apache Ignite 2.5 release

[Pavel Kovalenko]

Igniters,

I've found blocker issue https://issues.apache.org/jira/browse/IGNITE-8390
Cause of the problem is incorrect assertion that could be fixed very
quickly.
I would like to add this issue to 2.5 release.

2018-04-25 17:38 GMT+03:00 Andrey Gura :

> Igniters,
>
> We have about 30 JIRA issues that still aren't resolved. So it's
> possible that release date will be changed.
>
> But I think that it's time for scope freeze. Please, don't target any
> issues to 2.5 version without community approve.
>
> Thanks.
>
> On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov  wrote:
> > Andrey, thanks for control :)
> >
> > So, You'll fix broken versions eventually?
> >
> > BTW, I don't think it's a good idea to merge issues with fix version 2.5
> to
> > ignite-2.5. Good way is to fix version to 2.6 instead.
> >
> > 2018-04-12 21:34 GMT+03:00 Andrey Gura :
> >
> >> Anton,
> >>
> >> all is under control.
> >>
> >> Branches will be compared and changes that should be included to AI
> >> 2.5 will be identified.
> >>
> >> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov 
> wrote:
> >> > Possibly it is Andrey Gura — he initiated this thread and created
> >> corresponding branch.
> >> >
> >> >
> >> >> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
> >> >>
> >> >> Release manager is responsible for this change.
> >> >> Do we have release manager for 2.5?
> >> >>
> >> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
> >> >>
> >> >>> I've changed my ticket version assignment, and a lot of Igniters
> >> changed.
> >> >>>
> >> >>> Filter for double-check tickets related to you
> >> >>> *https://issues.apache.org/jira/issues/?jql=project%
> >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> >>> 20reporter%3DcurrentUser())
> >> >>>  >> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >> >>> 20reporter%3DcurrentUser())>*
> >> >>>
> >> >>>
> >> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
> >> >>>
> >>  Folks,
> >>  I see a lot of issues 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?
> >> 
> >>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
> >> 
> >> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
> >> >>> project
> >> > in TC.
> >> >
> >> >
> >> >
> >> >> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> >> >>
> >> >> 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 
> >> >>> 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
> >> > 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, 2018 at 9:11 PM, Andrey Gura 
> >> >>> 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 check JIRA issues assigned to you and move it to
> the
> >> >>> next
> >>  version if this issues shouldn't be included to 2.5 release.
> >> 
> >>  Release page on wiki [1] contains all issues targeted to 2.5
> (fix
> >>  version field).
> >> 
> >>  [1] https://cwiki.apache.org/confluence/display/IGNITE/
> >> > Apache+Ignite+2.5
> >> >>>
> >> >
> >> >
> >> 
> >> >>>
> >> >
> >>
>

Re: Apache Ignite 2.5 release

[Andrey Gura]

Igniters,

We have about 30 JIRA issues that still aren't resolved. So it's
possible that release date will be changed.

But I think that it's time for scope freeze. Please, don't target any
issues to 2.5 version without community approve.

Thanks.

On Fri, Apr 13, 2018 at 11:30 AM, Anton Vinogradov  wrote:
> Andrey, thanks for control :)
>
> So, You'll fix broken versions eventually?
>
> BTW, I don't think it's a good idea to merge issues with fix version 2.5 to
> ignite-2.5. Good way is to fix version to 2.6 instead.
>
> 2018-04-12 21:34 GMT+03:00 Andrey Gura :
>
>> Anton,
>>
>> all is under control.
>>
>> Branches will be compared and changes that should be included to AI
>> 2.5 will be identified.
>>
>> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov  wrote:
>> > Possibly it is Andrey Gura — he initiated this thread and created
>> corresponding branch.
>> >
>> >
>> >> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
>> >>
>> >> Release manager is responsible for this change.
>> >> Do we have release manager for 2.5?
>> >>
>> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
>> >>
>> >>> I've changed my ticket version assignment, and a lot of Igniters
>> changed.
>> >>>
>> >>> Filter for double-check tickets related to you
>> >>> *https://issues.apache.org/jira/issues/?jql=project%
>> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> >>> 20reporter%3DcurrentUser())
>> >>> > >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> >>> 20reporter%3DcurrentUser())>*
>> >>>
>> >>>
>> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>> >>>
>>  Folks,
>>  I see a lot of issues 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?
>> 
>>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
>> 
>> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
>> >>> project
>> > in TC.
>> >
>> >
>> >
>> >> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
>> >>
>> >> 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 
>> >>> 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
>> > 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, 2018 at 9:11 PM, Andrey Gura 
>> >>> 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 check JIRA issues assigned to you and move it to the
>> >>> next
>>  version if this issues shouldn't be included to 2.5 release.
>> 
>>  Release page on wiki [1] contains all issues targeted to 2.5 (fix
>>  version field).
>> 
>>  [1] https://cwiki.apache.org/confluence/display/IGNITE/
>> > Apache+Ignite+2.5
>> >>>
>> >
>> >
>> 
>> >>>
>> >
>>

Re: Apache Ignite 2.5 release

[Anton Vinogradov]

Andrey, thanks for control :)

So, You'll fix broken versions eventually?

BTW, I don't think it's a good idea to merge issues with fix version 2.5 to
ignite-2.5. Good way is to fix version to 2.6 instead.

2018-04-12 21:34 GMT+03:00 Andrey Gura :

> Anton,
>
> all is under control.
>
> Branches will be compared and changes that should be included to AI
> 2.5 will be identified.
>
> On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov  wrote:
> > Possibly it is Andrey Gura — he initiated this thread and created
> corresponding branch.
> >
> >
> >> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
> >>
> >> Release manager is responsible for this change.
> >> Do we have release manager for 2.5?
> >>
> >> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
> >>
> >>> I've changed my ticket version assignment, and a lot of Igniters
> changed.
> >>>
> >>> Filter for double-check tickets related to you
> >>> *https://issues.apache.org/jira/issues/?jql=project%
> >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >>> 20reporter%3DcurrentUser())
> >>>  >>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> >>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> >>> 20reporter%3DcurrentUser())>*
> >>>
> >>>
> >>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
> >>>
>  Folks,
>  I see a lot of issues 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?
> 
>  2018-04-06 10:19 GMT+03:00 Petr Ivanov :
> 
> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
> >>> project
> > in TC.
> >
> >
> >
> >> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> >>
> >> 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 
> >>> 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
> > 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, 2018 at 9:11 PM, Andrey Gura 
> >>> 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 check JIRA issues assigned to you and move it to the
> >>> next
>  version if this issues shouldn't be included to 2.5 release.
> 
>  Release page on wiki [1] contains all issues targeted to 2.5 (fix
>  version field).
> 
>  [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.5
> >>>
> >
> >
> 
> >>>
> >
>

Re: Apache Ignite 2.5 release

[Andrey Gura]

Anton,

all is under control.

Branches will be compared and changes that should be included to AI
2.5 will be identified.

On Thu, Apr 12, 2018 at 6:19 PM, Petr Ivanov  wrote:
> Possibly it is Andrey Gura — he initiated this thread and created 
> corresponding branch.
>
>
>> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
>>
>> Release manager is responsible for this change.
>> Do we have release manager for 2.5?
>>
>> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
>>
>>> I've changed my ticket version assignment, and a lot of Igniters changed.
>>>
>>> Filter for double-check tickets related to you
>>> *https://issues.apache.org/jira/issues/?jql=project%
>>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>>> 20reporter%3DcurrentUser())
>>> >> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>>> 20reporter%3DcurrentUser())>*
>>>
>>>
>>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>>>
 Folks,
 I see a lot of issues 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?

 2018-04-06 10:19 GMT+03:00 Petr Ivanov :

> Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
>>> project
> in TC.
>
>
>
>> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
>>
>> 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 
>>> 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
> 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, 2018 at 9:11 PM, Andrey Gura 
>>> 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 check JIRA issues assigned to you and move it to the
>>> next
 version if this issues shouldn't be included to 2.5 release.

 Release page on wiki [1] contains all issues targeted to 2.5 (fix
 version field).

 [1] https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.5
>>>
>
>

>>>
>

Re: Apache Ignite 2.5 release

[Petr Ivanov]

Possibly it is Andrey Gura — he initiated this thread and created corresponding 
branch.


> On 12 Apr 2018, at 17:39, Anton Vinogradov  wrote:
> 
> Release manager is responsible for this change.
> Do we have release manager for 2.5?
> 
> 2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :
> 
>> I've changed my ticket version assignment, and a lot of Igniters changed.
>> 
>> Filter for double-check tickets related to you
>> *https://issues.apache.org/jira/issues/?jql=project%
>> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> 20reporter%3DcurrentUser())
>> > 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
>> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
>> 20reporter%3DcurrentUser())>*
>> 
>> 
>> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>> 
>>> Folks,
>>> I see a lot of issues 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?
>>> 
>>> 2018-04-06 10:19 GMT+03:00 Petr Ivanov :
>>> 
 Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
>> project
 in TC.
 
 
 
> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> 
> 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 
>> 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
 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, 2018 at 9:11 PM, Andrey Gura 
>> 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 check JIRA issues assigned to you and move it to the
>> next
>>> version if this issues shouldn't be included to 2.5 release.
>>> 
>>> Release page on wiki [1] contains all issues targeted to 2.5 (fix
>>> version field).
>>> 
>>> [1] https://cwiki.apache.org/confluence/display/IGNITE/
 Apache+Ignite+2.5
>> 
 
 
>>> 
>> 

Re: Apache Ignite 2.5 release

[Anton Vinogradov]

Release manager is responsible for this change.
Do we have release manager for 2.5?

2018-04-12 17:35 GMT+03:00 Dmitry Pavlov :

> I've changed my ticket version assignment, and a lot of Igniters changed.
>
> Filter for double-check tickets related to you
> *https://issues.apache.org/jira/issues/?jql=project%
> 3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> 20reporter%3DcurrentUser())
>  3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%
> 20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%
> 20reporter%3DcurrentUser())>*
>
>
> чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :
>
> > Folks,
> > I see a lot of issues 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?
> >
> > 2018-04-06 10:19 GMT+03:00 Petr Ivanov :
> >
> > > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+
> project
> > > in TC.
> > >
> > >
> > >
> > > > On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> > > >
> > > > 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 
> 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
> > > 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, 2018 at 9:11 PM, Andrey Gura 
> 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 check JIRA issues assigned to you and move it to the
> next
> > > >>> version if this issues shouldn't be included to 2.5 release.
> > > >>>
> > > >>> Release page on wiki [1] contains all issues targeted to 2.5 (fix
> > > >>> version field).
> > > >>>
> > > >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > Apache+Ignite+2.5
> > > >>
> > >
> > >
> >
>

Re: Apache Ignite 2.5 release

[Dmitry Pavlov]

I've changed my ticket version assignment, and a lot of Igniters changed.

Filter for double-check tickets related to you
*https://issues.apache.org/jira/issues/?jql=project%3DIGNITE%20AND%20fixVersion%3D2.5%20and%20resolution%20is%20EMPTY%20%20and%20(assignee%3DcurrentUser()%20or%20reporter%3DcurrentUser())
*


чт, 12 апр. 2018 г. в 17:24, Anton Vinogradov :

> Folks,
> I see a lot of issues 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?
>
> 2018-04-06 10:19 GMT+03:00 Petr Ivanov :
>
> > Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ project
> > in TC.
> >
> >
> >
> > > On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> > >
> > > 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  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
> > 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, 2018 at 9:11 PM, Andrey Gura  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 check JIRA issues assigned to you and move it to the next
> > >>> version if this issues shouldn't be included to 2.5 release.
> > >>>
> > >>> Release page on wiki [1] contains all issues targeted to 2.5 (fix
> > >>> version field).
> > >>>
> > >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.5
> > >>
> >
> >
>

Re: Apache Ignite 2.5 release

[Anton Vinogradov]

Folks,
I see a lot of issues 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?

2018-04-06 10:19 GMT+03:00 Petr Ivanov :

> Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ project
> in TC.
>
>
>
> > On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> >
> > 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  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
> 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, 2018 at 9:11 PM, Andrey Gura  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 check JIRA issues assigned to you and move it to the next
> >>> version if this issues shouldn't be included to 2.5 release.
> >>>
> >>> Release page on wiki [1] contains all issues targeted to 2.5 (fix
> >>> version field).
> >>>
> >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.5
> >>
>
>

Re: Apache Ignite 2.5 release

[Petr Ivanov]

Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ project in TC.



> On 5 Apr 2018, at 21:55, Denis Magda  wrote:
> 
> 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  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 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, 2018 at 9:11 PM, Andrey Gura  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 check JIRA issues assigned to you and move it to the next
>>> version if this issues shouldn't be included to 2.5 release.
>>> 
>>> Release page on wiki [1] contains all issues targeted to 2.5 (fix
>>> version field).
>>> 
>>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.5
>> 

Re: Apache Ignite 2.5 release

[Denis Magda]

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  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 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, 2018 at 9:11 PM, Andrey Gura  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 check JIRA issues assigned to you and move it to the next
> > version if this issues shouldn't be included to 2.5 release.
> >
> > Release page on wiki [1] contains all issues targeted to 2.5 (fix
> > version field).
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.5
>

Re: Apache Ignite 2.5 release

[Andrey Gura]

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, 2018 at 9:11 PM, Andrey Gura  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 check JIRA issues assigned to you and move it to the next
> version if this issues shouldn't be included to 2.5 release.
>
> Release page on wiki [1] contains all issues targeted to 2.5 (fix
> version field).
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.5