Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-10-12 Thread Vladislav Pyatkov 
This patch [1] interesting only a deployment where clients often
reconnecting (stopping/starting) to cluster.
In these cases Coordinator node could fail by OOM, even the cluster did not
use MVCC caches.

On Mon, Oct 12, 2020 at 1:41 PM Zhenya Stanilovsky
 wrote:

>
>
> without [2] and [3] we obtain unexpected fields in index creation and as a
> consequence buggy sql execution and pla of course.
>
>
>
> >Guys,
> >
> >I've found 3 more tickets which were targeted to 2.9 but merged only to
> the
> >master branch ([1], [2], [3]).
> >Do we need these tickets in 2.9? Are they critical?
> >
> >[1]:  https://issues.apache.org/jira/browse/IGNITE-12350
> >[2]:  https://issues.apache.org/jira/browse/IGNITE-13376
> >[3]:  https://issues.apache.org/jira/browse/IGNITE-13280
> >
> >вс, 11 окт. 2020 г. в 16:11, Nikolay Izhikov < nizhi...@apache.org >:
> >
> >> Igniters,
> >>
> >> IGNITE-13553 fixed and cherry-picked to 2.9.
> >> We can continue with the release.
> >>
> >> > 10 окт. 2020 г., в 00:00, Denis Magda < dma...@apache.org >
> написал(а):
> >> >
> >> > Nikolay,
> >> >
> >> > re: the minor improvements. I'm not against of including those if we
> can
> >> > prepare the docs before the vote starts. Presently, the docs are
> "frozen"
> >> > for the 2.9 release, but I can scratch some time and take part in the
> >> docs
> >> > review the next week.
> >> >
> >> > -
> >> > Denis
> >> >
> >> >
> >> > On Fri, Oct 9, 2020 at 12:40 AM Nikolay Izhikov < nizhi...@apache.org
> >
> >> wrote:
> >> >
> >> >> Hello, Igniters.
> >> >>
> >> >> I prepared a patch [1] for blocker ticket [2] - «Server node fail and
> >> >> stops in case wrong datatype put in indexed field»
> >> >> Can someone, please, help me with the review?
> >> >>
> >> >> [1]  https://github.com/apache/ignite/pull/8330
> >> >> [2]  https://issues.apache.org/jira/browse/IGNITE-13553
> >> >>
> >> >> ==
> >> >>
> >> >> I propose to include several minor tickets to the scope of the 2.9
> that
> >> >> increase Ignite User Experience
> >> >>
> >> >> CMD tools improvements:
> >> >>
> >> >> IGNITE-13488 - Command to print metric value
> >> >> IGNITE-13426 - Command to print system view content
> >> >> IGNITE-13422 - Parameter to explicitly enable experimental commands
> >> >>
> >> >> IGNITE-13380 - Output IgniteSystemProperties via ignite.sh
> >> >>
> >> >> New system views:
> >> >>
> >> >> IGNITE-13409 Metastorage and DistributedMetastorage viewы.
> >> >> IGNITE-13408 BinaryMetadata view.
> >> >>
> >> >>> 9 окт. 2020 г., в 04:04, Denis Magda < dma...@apache.org >
> написал(а):
> >> >>>
> >> >>> @Alex Plehanov < plehanov.a...@gmail.com >,
> >> >>>
> >> >>> If it still makes sense and not too late, you can cherry-pick the
> >> commit
> >> >>> with the new docs into the 2.9 branch:
> >> >>>
> >> >>
> >>
> https://github.com/apache/ignite/commit/073488ac97517bbaad9f6b94b781fc404646f191
> >> >>>
> >> >>> Anyway, it's not crucial as long as we agreed to make an exception
> for
> >> >> this
> >> >>> release. The docs were already published to the website and
> assembled
> >> >> from
> >> >>> the master. Once the vote passes, I'll make them visible and
> traceable
> >> >> from
> >> >>> the website menus.
> >> >>>
> >> >>> -
> >> >>> Denis
> >> >>>
> >> >>>
> >> >>> On Tue, Oct 6, 2020 at 7:20 AM Alexey Goncharuk <
> >> >>  alexey.goncha...@gmail.com >
> >> >>> wrote:
> >> >>>
> >>  Saikat,
> >> 
> >>  The plan sounds good to me! Do you have an idea for the timeline of
> >> the
> >>  module releases? Let me know if I can help in any way.
> >> 
> >>  Also, I was looking into the modularization IEP and noticed that
> OSGI
> >>  module is discussed to be moved to the extensions, but there is no
> >>  corresponding ticket. Should I create one? I will be happy to help
> >> with
> >>  moving this module to extensions.
> >> 
> >>  вт, 29 сент. 2020 г. в 03:03, Saikat Maitra <
> saikat.mai...@gmail.com
> >> >:
> >> 
> >> > Hi Alexey,
> >> >
> >> > All the modules as planned in IEP-36
> >> >
> >> 
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36:+Modularization
> >> > are migrated to ignite-extensions repository.
> >> >
> >> > We can definitely plan to release ignite-extensions modules.
> >> >
> >> > I have a pending PR related to the kafka module and the PR is in
> >> review
> >> >  https://github.com/apache/ignite/pull/8222 but its
> corresponding PR
> >> >> has
> >> > been merged in ignite-extensions repository.
> >> >
> >> > My thoughts / action items for the migration efforts and releases
> >> were
> >> > as follows:
> >> >
> >> > 1. Merge the changes for
> https://github.com/apache/ignite/pull/8222
> >> > 2. Fix the upload nightly packages task for ignite-core to help
> fix
> >> the
> >> > travis build failure in ignite-extensions repository.
> >> > 3. Review and update the README.md files for the ignite-extensions
> >>

Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-10-12 Thread Zhenya Stanilovsky 


without [2] and [3] we obtain unexpected fields in index creation and as a 
consequence buggy sql execution and pla of course.


 
>Guys,
>
>I've found 3 more tickets which were targeted to 2.9 but merged only to the
>master branch ([1], [2], [3]).
>Do we need these tickets in 2.9? Are they critical?
>
>[1]:  https://issues.apache.org/jira/browse/IGNITE-12350
>[2]:  https://issues.apache.org/jira/browse/IGNITE-13376
>[3]:  https://issues.apache.org/jira/browse/IGNITE-13280
>
>вс, 11 окт. 2020 г. в 16:11, Nikolay Izhikov < nizhi...@apache.org >:
> 
>> Igniters,
>>
>> IGNITE-13553 fixed and cherry-picked to 2.9.
>> We can continue with the release.
>>
>> > 10 окт. 2020 г., в 00:00, Denis Magda < dma...@apache.org > написал(а):
>> >
>> > Nikolay,
>> >
>> > re: the minor improvements. I'm not against of including those if we can
>> > prepare the docs before the vote starts. Presently, the docs are "frozen"
>> > for the 2.9 release, but I can scratch some time and take part in the
>> docs
>> > review the next week.
>> >
>> > -
>> > Denis
>> >
>> >
>> > On Fri, Oct 9, 2020 at 12:40 AM Nikolay Izhikov < nizhi...@apache.org >
>> wrote:
>> >
>> >> Hello, Igniters.
>> >>
>> >> I prepared a patch [1] for blocker ticket [2] - «Server node fail and
>> >> stops in case wrong datatype put in indexed field»
>> >> Can someone, please, help me with the review?
>> >>
>> >> [1]  https://github.com/apache/ignite/pull/8330
>> >> [2]  https://issues.apache.org/jira/browse/IGNITE-13553
>> >>
>> >> ==
>> >>
>> >> I propose to include several minor tickets to the scope of the 2.9 that
>> >> increase Ignite User Experience
>> >>
>> >> CMD tools improvements:
>> >>
>> >> IGNITE-13488 - Command to print metric value
>> >> IGNITE-13426 - Command to print system view content
>> >> IGNITE-13422 - Parameter to explicitly enable experimental commands
>> >>
>> >> IGNITE-13380 - Output IgniteSystemProperties via ignite.sh
>> >>
>> >> New system views:
>> >>
>> >> IGNITE-13409 Metastorage and DistributedMetastorage viewы.
>> >> IGNITE-13408 BinaryMetadata view.
>> >>
>> >>> 9 окт. 2020 г., в 04:04, Denis Magda < dma...@apache.org > написал(а):
>> >>>
>> >>> @Alex Plehanov < plehanov.a...@gmail.com >,
>> >>>
>> >>> If it still makes sense and not too late, you can cherry-pick the
>> commit
>> >>> with the new docs into the 2.9 branch:
>> >>>
>> >>
>>  
>> https://github.com/apache/ignite/commit/073488ac97517bbaad9f6b94b781fc404646f191
>> >>>
>> >>> Anyway, it's not crucial as long as we agreed to make an exception for
>> >> this
>> >>> release. The docs were already published to the website and assembled
>> >> from
>> >>> the master. Once the vote passes, I'll make them visible and traceable
>> >> from
>> >>> the website menus.
>> >>>
>> >>> -
>> >>> Denis
>> >>>
>> >>>
>> >>> On Tue, Oct 6, 2020 at 7:20 AM Alexey Goncharuk <
>> >>  alexey.goncha...@gmail.com >
>> >>> wrote:
>> >>>
>>  Saikat,
>> 
>>  The plan sounds good to me! Do you have an idea for the timeline of
>> the
>>  module releases? Let me know if I can help in any way.
>> 
>>  Also, I was looking into the modularization IEP and noticed that OSGI
>>  module is discussed to be moved to the extensions, but there is no
>>  corresponding ticket. Should I create one? I will be happy to help
>> with
>>  moving this module to extensions.
>> 
>>  вт, 29 сент. 2020 г. в 03:03, Saikat Maitra < saikat.mai...@gmail.com
>> >:
>> 
>> > Hi Alexey,
>> >
>> > All the modules as planned in IEP-36
>> >
>> 
>> >>
>>  https://cwiki.apache.org/confluence/display/IGNITE/IEP-36:+Modularization
>> > are migrated to ignite-extensions repository.
>> >
>> > We can definitely plan to release ignite-extensions modules.
>> >
>> > I have a pending PR related to the kafka module and the PR is in
>> review
>> >  https://github.com/apache/ignite/pull/8222 but its corresponding PR
>> >> has
>> > been merged in ignite-extensions repository.
>> >
>> > My thoughts / action items for the migration efforts and releases
>> were
>> > as follows:
>> >
>> > 1. Merge the changes for  https://github.com/apache/ignite/pull/8222
>> > 2. Fix the upload nightly packages task for ignite-core to help fix
>> the
>> > travis build failure in ignite-extensions repository.
>> > 3. Review and update the README.md files for the ignite-extensions
>>  modules
>> > as required.
>> > 4. Update the docs for ignite-extensions modules in ignite-website.
>> > 5. Release each module separately and share updates.
>> >
>> > Please let me know if you have feedback.
>> >
>> > Regards,
>> > Saikat
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Sep 28, 2020 at 7:36 AM Petr Ivanov < mr.wei...@gmail.com >
>> >> wrote:
>> >
>> >> It seems that gitbox.apache.org is not available on CI/CD.
>> >>
>> >> I will try to update

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-08-06 Thread Alex Plehanov 
Ivan,

Thank you. We've got performance drop on our benchmarks too.
We are trying to bisect changes and find problematic commit now.

чт, 6 авг. 2020 г. в 14:51, Ivan Artiukhov :

> Hello,
>
> I've compared performances of 2.9 and 2.8.1 using Yardstick and some
> atomic/transactional/SQL operations. Ignite 2.9 is up to 7% slower in my
> configuration. Please see
> https://issues.apache.org/jira/browse/IGNITE-13337 for
> details. Is this performance drop a blocker for 2.9 release?
>
> --
> Regards,
> Ivan Artiukhov
>
> чт, 6 авг. 2020 г. в 11:10, Ivan Daschinsky :
>
> > I recently found, that control.sh is broken since 2.8.0 a little bit.
> > Script returns always 0 code, despite the fact, that CommandHandler
> returns
> > code correctly.
> >
> > Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328,
> > patch
> > is available.
> >
> > пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :
> >
> > > Ivan,
> > >
> > > IGNITE-13306 cherry-picked to 2.9
> > >
> > > пт, 31 июл. 2020 г. в 13:43, Ivan Rakov :
> > >
> > > > Hi Alex,
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-13306 is merged to
> > master.
> > > > Can you please cherry-pick to 2.9?
> > > >
> > > > On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hello!
> > > >>
> > > >> I don't think that IGNITE-13006
> > > >>  is a blocker
> in
> > > any
> > > >> way. It is a good candidate for 3.0.
> > > >>
> > > >> ignite-spring will work with 4.x Spring as well as 5.x and the user
> is
> > > >> free
> > > >> to bump Spring version. I think bumping this dependency explicitly
> is
> > > >> infeasible since it may break existing code.
> > > >>
> > > >> Regards,
> > > >> --
> > > >> Ilya Kasnacheev
> > > >>
> > > >>
> > > >> ср, 22 июл. 2020 г. в 10:22, Alex Plehanov  >:
> > > >>
> > > >> > Guys,
> > > >> >
> > > >> > We are in code-freeze phase now. I've moved almost all non-blocker
> > > >> > unresolved tickets from 2.9 to the next release. If you think that
> > > >> > some ticket is a blocker and should be included into 2.9 release,
> > > please
> > > >> > write a note in this thread.
> > > >> >
> > > >> > There are some tickets with "blocker" priority targeted to 2.9,
> some
> > > of
> > > >> > them in "open" state and still unassigned, and I'm not sure we
> need
> > > all
> > > >> of
> > > >> > these tickets in 2.9:
> > > >> >
> > > >> > IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version
> 4x
> > to
> > > >> > spring 5.2 version or later) - Is it really a blocker for 2.9
> > release?
> > > >> If
> > > >> > yes, can somebody help with resolving this ticket?
> > > >> >
> > > >> > IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) -
> > > ticket
> > > >> in
> > > >> > "Patch available" state. There is a thread on dev-list related to
> > this
> > > >> > ticket ([6]), but as far as I understand we still don't have
> > consensus
> > > >> > about version for this patch (2.9, 2.10, 3.0).
> > > >> >
> > > >> > IGNITE-12489 [3] (Error during purges by expiration: Unknown page
> > > type)
> > > >> -
> > > >> > perhaps issue is already resolved by some related tickets, there
> is
> > > >> still
> > > >> > no reproducer, no additional details and no work in progress. I
> > > propose
> > > >> to
> > > >> > move this ticket to the next release.
> > > >> >
> > > >> > IGNITE-12911 [4] (B+Tree Corrupted exception when using a key
> > > extracted
> > > >> > from a BinaryObject value object --- and SQL enabled) - ticket in
> > > "Patch
> > > >> > available" state, but there is no activity since May 2020. Anton
> > > >> > Kalashnikov, Ilya Kasnacheev, do we have any updates on this
> ticket?
> > > Is
> > > >> it
> > > >> > still in progress?
> > > >> >
> > > >> > IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
> > > >> metrics
> > > >> > framework is already released in 2.8 and it's still marked with
> > > >> > @IgniteExperemental annotation, I think this ticket is not a
> > blocker.
> > > I
> > > >> > propose to change the ticket priority and move it to the next
> > release.
> > > >> >
> > > >> >
> > > >> > [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> > > >> > [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> > > >> > [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> > > >> > [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> > > >> > [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> > > >> > [6]:
> > > >> >
> > > >>
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
> > > >> >
> > > >> > пт, 17 июл. 2020 г. в 11:50, Alex Plehanov <
> plehanov.a...@gmail.com
> > >:
> > > >> >
> > > >> >> Ivan,
> > > >> >>
> > > >> >> Merged to 2.9.
> > > >> >>
> > > >> >> Thanks
> > > >> >>
> > > >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> > > >> >>
> > > >> >>> Alex,
> >

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-08-06 Thread Ivan Artiukhov 
Hello,

I've compared performances of 2.9 and 2.8.1 using Yardstick and some
atomic/transactional/SQL operations. Ignite 2.9 is up to 7% slower in my
configuration. Please see
https://issues.apache.org/jira/browse/IGNITE-13337 for
details. Is this performance drop a blocker for 2.9 release?

-- 
Regards,
Ivan Artiukhov

чт, 6 авг. 2020 г. в 11:10, Ivan Daschinsky :

> I recently found, that control.sh is broken since 2.8.0 a little bit.
> Script returns always 0 code, despite the fact, that CommandHandler returns
> code correctly.
>
> Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328,
> patch
> is available.
>
> пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :
>
> > Ivan,
> >
> > IGNITE-13306 cherry-picked to 2.9
> >
> > пт, 31 июл. 2020 г. в 13:43, Ivan Rakov :
> >
> > > Hi Alex,
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-13306 is merged to
> master.
> > > Can you please cherry-pick to 2.9?
> > >
> > > On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > > wrote:
> > >
> > >> Hello!
> > >>
> > >> I don't think that IGNITE-13006
> > >>  is a blocker in
> > any
> > >> way. It is a good candidate for 3.0.
> > >>
> > >> ignite-spring will work with 4.x Spring as well as 5.x and the user is
> > >> free
> > >> to bump Spring version. I think bumping this dependency explicitly is
> > >> infeasible since it may break existing code.
> > >>
> > >> Regards,
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >>
> > >> ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :
> > >>
> > >> > Guys,
> > >> >
> > >> > We are in code-freeze phase now. I've moved almost all non-blocker
> > >> > unresolved tickets from 2.9 to the next release. If you think that
> > >> > some ticket is a blocker and should be included into 2.9 release,
> > please
> > >> > write a note in this thread.
> > >> >
> > >> > There are some tickets with "blocker" priority targeted to 2.9, some
> > of
> > >> > them in "open" state and still unassigned, and I'm not sure we need
> > all
> > >> of
> > >> > these tickets in 2.9:
> > >> >
> > >> > IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x
> to
> > >> > spring 5.2 version or later) - Is it really a blocker for 2.9
> release?
> > >> If
> > >> > yes, can somebody help with resolving this ticket?
> > >> >
> > >> > IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) -
> > ticket
> > >> in
> > >> > "Patch available" state. There is a thread on dev-list related to
> this
> > >> > ticket ([6]), but as far as I understand we still don't have
> consensus
> > >> > about version for this patch (2.9, 2.10, 3.0).
> > >> >
> > >> > IGNITE-12489 [3] (Error during purges by expiration: Unknown page
> > type)
> > >> -
> > >> > perhaps issue is already resolved by some related tickets, there is
> > >> still
> > >> > no reproducer, no additional details and no work in progress. I
> > propose
> > >> to
> > >> > move this ticket to the next release.
> > >> >
> > >> > IGNITE-12911 [4] (B+Tree Corrupted exception when using a key
> > extracted
> > >> > from a BinaryObject value object --- and SQL enabled) - ticket in
> > "Patch
> > >> > available" state, but there is no activity since May 2020. Anton
> > >> > Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket?
> > Is
> > >> it
> > >> > still in progress?
> > >> >
> > >> > IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
> > >> metrics
> > >> > framework is already released in 2.8 and it's still marked with
> > >> > @IgniteExperemental annotation, I think this ticket is not a
> blocker.
> > I
> > >> > propose to change the ticket priority and move it to the next
> release.
> > >> >
> > >> >
> > >> > [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> > >> > [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> > >> > [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> > >> > [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> > >> > [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> > >> > [6]:
> > >> >
> > >>
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
> > >> >
> > >> > пт, 17 июл. 2020 г. в 11:50, Alex Plehanov  >:
> > >> >
> > >> >> Ivan,
> > >> >>
> > >> >> Merged to 2.9.
> > >> >>
> > >> >> Thanks
> > >> >>
> > >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> > >> >>
> > >> >>> Alex,
> > >> >>>
> > >> >>> Tracing is merged to master:
> > >> >>> https://issues.apache.org/jira/browse/IGNITE-13060
> > >> >>>
> > >> >>> Can you please port it to 2.9?
> > >> >>> For you convenience, there's PR versus 2.9 with conflicts
> resolved:
> > >> >>> https://github.com/apache/ignite/pull/8046/files
> > >> >>>
> > >> >>> --
> > >> >>> Best Regards,
> > >> >>> Ivan Rakov
> > >> >>>
> > >> >>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov <
> > >> plehanov.a...@gmail.com>
> > >> >>> wrote:
> > >> >>>
> > >

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-08-06 Thread Ivan Daschinsky 
I recently found, that control.sh is broken since 2.8.0 a little bit.
Script returns always 0 code, despite the fact, that CommandHandler returns
code correctly.

Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328, patch
is available.

пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :

> Ivan,
>
> IGNITE-13306 cherry-picked to 2.9
>
> пт, 31 июл. 2020 г. в 13:43, Ivan Rakov :
>
> > Hi Alex,
> >
> > https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master.
> > Can you please cherry-pick to 2.9?
> >
> > On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>
> > wrote:
> >
> >> Hello!
> >>
> >> I don't think that IGNITE-13006
> >>  is a blocker in
> any
> >> way. It is a good candidate for 3.0.
> >>
> >> ignite-spring will work with 4.x Spring as well as 5.x and the user is
> >> free
> >> to bump Spring version. I think bumping this dependency explicitly is
> >> infeasible since it may break existing code.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :
> >>
> >> > Guys,
> >> >
> >> > We are in code-freeze phase now. I've moved almost all non-blocker
> >> > unresolved tickets from 2.9 to the next release. If you think that
> >> > some ticket is a blocker and should be included into 2.9 release,
> please
> >> > write a note in this thread.
> >> >
> >> > There are some tickets with "blocker" priority targeted to 2.9, some
> of
> >> > them in "open" state and still unassigned, and I'm not sure we need
> all
> >> of
> >> > these tickets in 2.9:
> >> >
> >> > IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> >> > spring 5.2 version or later) - Is it really a blocker for 2.9 release?
> >> If
> >> > yes, can somebody help with resolving this ticket?
> >> >
> >> > IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) -
> ticket
> >> in
> >> > "Patch available" state. There is a thread on dev-list related to this
> >> > ticket ([6]), but as far as I understand we still don't have consensus
> >> > about version for this patch (2.9, 2.10, 3.0).
> >> >
> >> > IGNITE-12489 [3] (Error during purges by expiration: Unknown page
> type)
> >> -
> >> > perhaps issue is already resolved by some related tickets, there is
> >> still
> >> > no reproducer, no additional details and no work in progress. I
> propose
> >> to
> >> > move this ticket to the next release.
> >> >
> >> > IGNITE-12911 [4] (B+Tree Corrupted exception when using a key
> extracted
> >> > from a BinaryObject value object --- and SQL enabled) - ticket in
> "Patch
> >> > available" state, but there is no activity since May 2020. Anton
> >> > Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket?
> Is
> >> it
> >> > still in progress?
> >> >
> >> > IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
> >> metrics
> >> > framework is already released in 2.8 and it's still marked with
> >> > @IgniteExperemental annotation, I think this ticket is not a blocker.
> I
> >> > propose to change the ticket priority and move it to the next release.
> >> >
> >> >
> >> > [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> >> > [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> >> > [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> >> > [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> >> > [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> >> > [6]:
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
> >> >
> >> > пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
> >> >
> >> >> Ivan,
> >> >>
> >> >> Merged to 2.9.
> >> >>
> >> >> Thanks
> >> >>
> >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> >> >>
> >> >>> Alex,
> >> >>>
> >> >>> Tracing is merged to master:
> >> >>> https://issues.apache.org/jira/browse/IGNITE-13060
> >> >>>
> >> >>> Can you please port it to 2.9?
> >> >>> For you convenience, there's PR versus 2.9 with conflicts resolved:
> >> >>> https://github.com/apache/ignite/pull/8046/files
> >> >>>
> >> >>> --
> >> >>> Best Regards,
> >> >>> Ivan Rakov
> >> >>>
> >> >>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov <
> >> plehanov.a...@gmail.com>
> >> >>> wrote:
> >> >>>
> >>  Ivan,
> >> 
> >>  Looks like master is broken after IGNITE-13246 (but everything is
> ok
> >> in
> >>  2.9
> >>  branch)
> >> 
> >>  ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <
> plehanov.a...@gmail.com
> >> >:
> >> 
> >>  > Zhenya, Ivan,
> >>  >
> >>  > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> >> branch.
> >>  > Thank you.
> >>  >
> >>  > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <
> bessonov...@gmail.com
> >> >:
> >>  >
> >>  >> Guys,
> >>  >>
> >>  >> can you please backport
> >>  >> https://issues.apache.org/jira/browse/IGNITE-13246
> >>  >>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-31 Thread Alex Plehanov 
Ivan,

IGNITE-13306 cherry-picked to 2.9

пт, 31 июл. 2020 г. в 13:43, Ivan Rakov :

> Hi Alex,
>
> https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master.
> Can you please cherry-pick to 2.9?
>
> On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> I don't think that IGNITE-13006
>>  is a blocker in any
>> way. It is a good candidate for 3.0.
>>
>> ignite-spring will work with 4.x Spring as well as 5.x and the user is
>> free
>> to bump Spring version. I think bumping this dependency explicitly is
>> infeasible since it may break existing code.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :
>>
>> > Guys,
>> >
>> > We are in code-freeze phase now. I've moved almost all non-blocker
>> > unresolved tickets from 2.9 to the next release. If you think that
>> > some ticket is a blocker and should be included into 2.9 release, please
>> > write a note in this thread.
>> >
>> > There are some tickets with "blocker" priority targeted to 2.9, some of
>> > them in "open" state and still unassigned, and I'm not sure we need all
>> of
>> > these tickets in 2.9:
>> >
>> > IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
>> > spring 5.2 version or later) - Is it really a blocker for 2.9 release?
>> If
>> > yes, can somebody help with resolving this ticket?
>> >
>> > IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket
>> in
>> > "Patch available" state. There is a thread on dev-list related to this
>> > ticket ([6]), but as far as I understand we still don't have consensus
>> > about version for this patch (2.9, 2.10, 3.0).
>> >
>> > IGNITE-12489 [3] (Error during purges by expiration: Unknown page type)
>> -
>> > perhaps issue is already resolved by some related tickets, there is
>> still
>> > no reproducer, no additional details and no work in progress. I propose
>> to
>> > move this ticket to the next release.
>> >
>> > IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
>> > from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
>> > available" state, but there is no activity since May 2020. Anton
>> > Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is
>> it
>> > still in progress?
>> >
>> > IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
>> metrics
>> > framework is already released in 2.8 and it's still marked with
>> > @IgniteExperemental annotation, I think this ticket is not a blocker. I
>> > propose to change the ticket priority and move it to the next release.
>> >
>> >
>> > [1]: https://issues.apache.org/jira/browse/IGNITE-13006
>> > [2]: https://issues.apache.org/jira/browse/IGNITE-11942
>> > [3]: https://issues.apache.org/jira/browse/IGNITE-12489
>> > [4]: https://issues.apache.org/jira/browse/IGNITE-12911
>> > [5]: https://issues.apache.org/jira/browse/IGNITE-12553
>> > [6]:
>> >
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>> >
>> > пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
>> >
>> >> Ivan,
>> >>
>> >> Merged to 2.9.
>> >>
>> >> Thanks
>> >>
>> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
>> >>
>> >>> Alex,
>> >>>
>> >>> Tracing is merged to master:
>> >>> https://issues.apache.org/jira/browse/IGNITE-13060
>> >>>
>> >>> Can you please port it to 2.9?
>> >>> For you convenience, there's PR versus 2.9 with conflicts resolved:
>> >>> https://github.com/apache/ignite/pull/8046/files
>> >>>
>> >>> --
>> >>> Best Regards,
>> >>> Ivan Rakov
>> >>>
>> >>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov <
>> plehanov.a...@gmail.com>
>> >>> wrote:
>> >>>
>>  Ivan,
>> 
>>  Looks like master is broken after IGNITE-13246 (but everything is ok
>> in
>>  2.9
>>  branch)
>> 
>>  ср, 15 июл. 2020 г. в 18:54, Alex Plehanov > >:
>> 
>>  > Zhenya, Ivan,
>>  >
>>  > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
>> branch.
>>  > Thank you.
>>  >
>>  > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov > >:
>>  >
>>  >> Guys,
>>  >>
>>  >> can you please backport
>>  >> https://issues.apache.org/jira/browse/IGNITE-13246
>>  >> to ignite-2.9? Me and Alexey Kuznetsov really want these new
>> events
>>  in
>>  >> release.
>>  >>
>>  >> This time I prepared PR with resolved conflicts:
>>  >> https://github.com/apache/ignite/pull/8042
>>  >>
>>  >> Thank you!
>>  >>
>>  >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>>  >> >  >> >:
>>  >>
>>  >> >
>>  >> >
>>  >> >
>>  >> > Alex, i also suggest to merge this
>>  >> > https://issues.apache.org/jira/browse/IGNITE-13229 too,
>> GridClient
>>  >> > leakage and further TC OOM preventing.
>>  >> >
>>  >> > >Ivan,
>>  >> > >
>>  >> > >It was already in release scope a

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-31 Thread Ivan Rakov 
Hi Alex,

https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master.
Can you please cherry-pick to 2.9?

On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> I don't think that IGNITE-13006
>  is a blocker in any
> way. It is a good candidate for 3.0.
>
> ignite-spring will work with 4.x Spring as well as 5.x and the user is free
> to bump Spring version. I think bumping this dependency explicitly is
> infeasible since it may break existing code.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :
>
> > Guys,
> >
> > We are in code-freeze phase now. I've moved almost all non-blocker
> > unresolved tickets from 2.9 to the next release. If you think that
> > some ticket is a blocker and should be included into 2.9 release, please
> > write a note in this thread.
> >
> > There are some tickets with "blocker" priority targeted to 2.9, some of
> > them in "open" state and still unassigned, and I'm not sure we need all
> of
> > these tickets in 2.9:
> >
> > IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> > spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
> > yes, can somebody help with resolving this ticket?
> >
> > IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket
> in
> > "Patch available" state. There is a thread on dev-list related to this
> > ticket ([6]), but as far as I understand we still don't have consensus
> > about version for this patch (2.9, 2.10, 3.0).
> >
> > IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
> > perhaps issue is already resolved by some related tickets, there is still
> > no reproducer, no additional details and no work in progress. I propose
> to
> > move this ticket to the next release.
> >
> > IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
> > from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
> > available" state, but there is no activity since May 2020. Anton
> > Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is
> it
> > still in progress?
> >
> > IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
> metrics
> > framework is already released in 2.8 and it's still marked with
> > @IgniteExperemental annotation, I think this ticket is not a blocker. I
> > propose to change the ticket priority and move it to the next release.
> >
> >
> > [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> > [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> > [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> > [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> > [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> > [6]:
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
> >
> > пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
> >
> >> Ivan,
> >>
> >> Merged to 2.9.
> >>
> >> Thanks
> >>
> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> >>
> >>> Alex,
> >>>
> >>> Tracing is merged to master:
> >>> https://issues.apache.org/jira/browse/IGNITE-13060
> >>>
> >>> Can you please port it to 2.9?
> >>> For you convenience, there's PR versus 2.9 with conflicts resolved:
> >>> https://github.com/apache/ignite/pull/8046/files
> >>>
> >>> --
> >>> Best Regards,
> >>> Ivan Rakov
> >>>
> >>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov  >
> >>> wrote:
> >>>
>  Ivan,
> 
>  Looks like master is broken after IGNITE-13246 (but everything is ok
> in
>  2.9
>  branch)
> 
>  ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
> 
>  > Zhenya, Ivan,
>  >
>  > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> branch.
>  > Thank you.
>  >
>  > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
>  >
>  >> Guys,
>  >>
>  >> can you please backport
>  >> https://issues.apache.org/jira/browse/IGNITE-13246
>  >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events
>  in
>  >> release.
>  >>
>  >> This time I prepared PR with resolved conflicts:
>  >> https://github.com/apache/ignite/pull/8042
>  >>
>  >> Thank you!
>  >>
>  >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>  >>   >> >:
>  >>
>  >> >
>  >> >
>  >> >
>  >> > Alex, i also suggest to merge this
>  >> > https://issues.apache.org/jira/browse/IGNITE-13229 too,
> GridClient
>  >> > leakage and further TC OOM preventing.
>  >> >
>  >> > >Ivan,
>  >> > >
>  >> > >It was already in release scope as discussed in this thread.
>  >> > >
>  >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com
>  >:
>  >> > >
>  >> > >> Hi,
>  >> > >>
>  >> > >> We are still waiting for a final review of Tracing
>  functionality [1]
>  >> > until

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-30 Thread Ilya Kasnacheev 
Hello!

I don't think that IGNITE-13006
 is a blocker in any
way. It is a good candidate for 3.0.

ignite-spring will work with 4.x Spring as well as 5.x and the user is free
to bump Spring version. I think bumping this dependency explicitly is
infeasible since it may break existing code.

Regards,
-- 
Ilya Kasnacheev


ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :

> Guys,
>
> We are in code-freeze phase now. I've moved almost all non-blocker
> unresolved tickets from 2.9 to the next release. If you think that
> some ticket is a blocker and should be included into 2.9 release, please
> write a note in this thread.
>
> There are some tickets with "blocker" priority targeted to 2.9, some of
> them in "open" state and still unassigned, and I'm not sure we need all of
> these tickets in 2.9:
>
> IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
> yes, can somebody help with resolving this ticket?
>
> IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in
> "Patch available" state. There is a thread on dev-list related to this
> ticket ([6]), but as far as I understand we still don't have consensus
> about version for this patch (2.9, 2.10, 3.0).
>
> IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
> perhaps issue is already resolved by some related tickets, there is still
> no reproducer, no additional details and no work in progress. I propose to
> move this ticket to the next release.
>
> IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
> from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
> available" state, but there is no activity since May 2020. Anton
> Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it
> still in progress?
>
> IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics
> framework is already released in 2.8 and it's still marked with
> @IgniteExperemental annotation, I think this ticket is not a blocker. I
> propose to change the ticket priority and move it to the next release.
>
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> [6]:
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>
> пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
>
>> Ivan,
>>
>> Merged to 2.9.
>>
>> Thanks
>>
>> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
>>
>>> Alex,
>>>
>>> Tracing is merged to master:
>>> https://issues.apache.org/jira/browse/IGNITE-13060
>>>
>>> Can you please port it to 2.9?
>>> For you convenience, there's PR versus 2.9 with conflicts resolved:
>>> https://github.com/apache/ignite/pull/8046/files
>>>
>>> --
>>> Best Regards,
>>> Ivan Rakov
>>>
>>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
>>> wrote:
>>>
 Ivan,

 Looks like master is broken after IGNITE-13246 (but everything is ok in
 2.9
 branch)

 ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :

 > Zhenya, Ivan,
 >
 > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
 > Thank you.
 >
 > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
 >
 >> Guys,
 >>
 >> can you please backport
 >> https://issues.apache.org/jira/browse/IGNITE-13246
 >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events
 in
 >> release.
 >>
 >> This time I prepared PR with resolved conflicts:
 >> https://github.com/apache/ignite/pull/8042
 >>
 >> Thank you!
 >>
 >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
 >> >>> >> >:
 >>
 >> >
 >> >
 >> >
 >> > Alex, i also suggest to merge this
 >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
 >> > leakage and further TC OOM preventing.
 >> >
 >> > >Ivan,
 >> > >
 >> > >It was already in release scope as discussed in this thread.
 >> > >
 >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com
 >:
 >> > >
 >> > >> Hi,
 >> > >>
 >> > >> We are still waiting for a final review of Tracing
 functionality [1]
 >> > until
 >> > >> the end of tomorrow (July 15).
 >> > >> We anticipate that it will be merged to Ignite master no later
 than
 >> July
 >> > >> 16.
 >> > >>
 >> > >> Sorry for being a bit late here. Alex P., can you include [1]
 to the
 >> > >> release scope?
 >> > >>
 >> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
 >> > >>
 >> > >> --
 >> > >> Best Regards,
 >> > >> Ivan Rakov
 >> > >>
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-29 Thread Denis Mekhanikov 
Guys,

Is there a chance to squeeze the fix for the following issue in:
https://issues.apache.org/jira/browse/IGNITE-13306
?
The issue makes the CPU load metric show -1 on Java 11. This is a quite
important metric, and this bug makes it harder to configure its monitoring.
Mirza, who's currently working on this issue says that he'll be able to
finish working on it today or tomorrow.

What do you think?

Denis

пт, 24 июл. 2020 г. в 11:04, Alex Plehanov :

> Guys,
>
> I've cherry-picked IGNITE-12438 (One-way client-server connections) and
> IGNITE-13038 (Web console removing) to 2.9.
>
> Since there are no objections I will move IGNITE-13006 (Spring libs upgrade
> to 5.2 version), IGNITE-12489 (Error during purges by expiration) and
> IGNITE-12553 (public Java metrics API) to the next release.
>
> I will cherry-pick ticket IGNITE-11942 (IGFS and Hadoop removing) after it
> will be reviewed and merged to master.
>
> What about IGNITE-12911 [1] (B+Tree Corrupted exception when using a key
> extracted from a BinaryObject value object --- and SQL enabled)? Anton
> Kalashnikov, Ilya Kasnacheev, can you please clarify the ticket status?
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-12911
>
> чт, 23 июл. 2020 г. в 12:08, Alexey Kuznetsov :
>
> > Alex, Denis
> >
> > Issue with moving of Web Console to separate repository is merged to
> > master.
> > See:  https://issues.apache.org/jira/browse/IGNITE-13038
> >
> > Please, consider to cherry-pick to ignite-2.9
> >
> > ---
> > Alexey Kuznetsov
> >
> >
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-24 Thread Alex Plehanov 
Guys,

I've cherry-picked IGNITE-12438 (One-way client-server connections) and
IGNITE-13038 (Web console removing) to 2.9.

Since there are no objections I will move IGNITE-13006 (Spring libs upgrade
to 5.2 version), IGNITE-12489 (Error during purges by expiration) and
IGNITE-12553 (public Java metrics API) to the next release.

I will cherry-pick ticket IGNITE-11942 (IGFS and Hadoop removing) after it
will be reviewed and merged to master.

What about IGNITE-12911 [1] (B+Tree Corrupted exception when using a key
extracted from a BinaryObject value object --- and SQL enabled)? Anton
Kalashnikov, Ilya Kasnacheev, can you please clarify the ticket status?

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

чт, 23 июл. 2020 г. в 12:08, Alexey Kuznetsov :

> Alex, Denis
>
> Issue with moving of Web Console to separate repository is merged to
> master.
> See:  https://issues.apache.org/jira/browse/IGNITE-13038
>
> Please, consider to cherry-pick to ignite-2.9
>
> ---
> Alexey Kuznetsov
>
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-23 Thread Alexey Kuznetsov 
Alex, Denis

Issue with moving of Web Console to separate repository is merged to master.
See:  https://issues.apache.org/jira/browse/IGNITE-13038

Please, consider to cherry-pick to ignite-2.9

---
Alexey Kuznetsov

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-22 Thread Ivan Bessonov 
Hi guys,

considering Denis's question: [1] ("inverse TCP connection establishment")
is
already in master. I think we should port it in 2.9, would be a good thing.

"Serverless functions" [2] support is code complete in a private branch,
it's safe
to say that the issue will be completed next week (I need to run all tests
and
pass the review, it'll take some time). If we're not in a hurry then it
might be worth
waiting. Are you ok with this estimation?

[1] https://issues.apache.org/jira/browse/IGNITE-12438
[2] https://issues.apache.org/jira/browse/IGNITE-13013

ср, 22 июл. 2020 г. в 18:19, Denis Magda :

> Sharing a correct link for the Web Console task:
> https://issues.apache.org/jira/browse/IGNITE-13038
>
> -
> Denis
>
>
> On Wed, Jul 22, 2020 at 7:59 AM Denis Magda  wrote:
>
> > Hi Alex,
> >
> > Thanks for wrapping this up and sharing the progress.
> >
> > I've continued the discussion in the Hadoop thread. Let's take a couple
> of
> > days to solve all open questions. Personally, I don't see any reason to
> put
> > the merge off to Ignite 3.0.
> >
> > Also, I would try to deliver the following two changes in Ignite 2.9:
> >
> >- Communication SPI changes [1] and serverless functions support.
> @Ivan
> >Bessonov , the first is completed but no
> >merged. The second should be already solved too. Could you please
> shed some
> >light on this?
> >- Phasing out Web Console [3]. It's ready for the review and I believe
> >that it can be merged quickly. @Alexey Kuznetsov
> >, could you please share your thoughts?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12438
> > [2] https://issues.apache.org/jira/browse/IGNITE-13013
> > [3] https://ggsystems.atlassian.net/browse/IGN-15304
> >
> > -
> > Denis
> >
> >
> > On Wed, Jul 22, 2020 at 12:22 AM Alex Plehanov 
> > wrote:
> >
> >> Guys,
> >>
> >> We are in code-freeze phase now. I've moved almost all non-blocker
> >> unresolved tickets from 2.9 to the next release. If you think that
> >> some ticket is a blocker and should be included into 2.9 release, please
> >> write a note in this thread.
> >>
> >> There are some tickets with "blocker" priority targeted to 2.9, some of
> >> them in "open" state and still unassigned, and I'm not sure we need all
> of
> >> these tickets in 2.9:
> >>
> >> IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> >> spring 5.2 version or later) - Is it really a blocker for 2.9 release?
> If
> >> yes, can somebody help with resolving this ticket?
> >>
> >> IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket
> in
> >> "Patch available" state. There is a thread on dev-list related to this
> >> ticket ([6]), but as far as I understand we still don't have consensus
> >> about version for this patch (2.9, 2.10, 3.0).
> >>
> >> IGNITE-12489 [3] (Error during purges by expiration: Unknown page type)
> -
> >> perhaps issue is already resolved by some related tickets, there is
> still
> >> no reproducer, no additional details and no work in progress. I propose
> to
> >> move this ticket to the next release.
> >>
> >> IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
> >> from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
> >> available" state, but there is no activity since May 2020. Anton
> >> Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is
> it
> >> still in progress?
> >>
> >> IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new
> metrics
> >> framework is already released in 2.8 and it's still marked with
> >> @IgniteExperemental annotation, I think this ticket is not a blocker. I
> >> propose to change the ticket priority and move it to the next release.
> >>
> >>
> >> [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> >> [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> >> [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> >> [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> >> [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> >> [6]:
> >>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
> >>
> >> пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
> >>
> >> > Ivan,
> >> >
> >> > Merged to 2.9.
> >> >
> >> > Thanks
> >> >
> >> > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> >> >
> >> >> Alex,
> >> >>
> >> >> Tracing is merged to master:
> >> >> https://issues.apache.org/jira/browse/IGNITE-13060
> >> >>
> >> >> Can you please port it to 2.9?
> >> >> For you convenience, there's PR versus 2.9 with conflicts resolved:
> >> >> https://github.com/apache/ignite/pull/8046/files
> >> >>
> >> >> --
> >> >> Best Regards,
> >> >> Ivan Rakov
> >> >>
> >> >> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov <
> plehanov.a...@gmail.com
> >> >
> >> >> wrote:
> >> >>
> >> >>> Ivan,
> >> >>>
> >> >>> Looks like master is broken after IGNITE-13246 (but everything is ok
> >> in
> >> >>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-22 Thread Denis Magda 
Sharing a correct link for the Web Console task:
https://issues.apache.org/jira/browse/IGNITE-13038

-
Denis


On Wed, Jul 22, 2020 at 7:59 AM Denis Magda  wrote:

> Hi Alex,
>
> Thanks for wrapping this up and sharing the progress.
>
> I've continued the discussion in the Hadoop thread. Let's take a couple of
> days to solve all open questions. Personally, I don't see any reason to put
> the merge off to Ignite 3.0.
>
> Also, I would try to deliver the following two changes in Ignite 2.9:
>
>- Communication SPI changes [1] and serverless functions support. @Ivan
>Bessonov , the first is completed but no
>merged. The second should be already solved too. Could you please shed some
>light on this?
>- Phasing out Web Console [3]. It's ready for the review and I believe
>that it can be merged quickly. @Alexey Kuznetsov
>, could you please share your thoughts?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12438
> [2] https://issues.apache.org/jira/browse/IGNITE-13013
> [3] https://ggsystems.atlassian.net/browse/IGN-15304
>
> -
> Denis
>
>
> On Wed, Jul 22, 2020 at 12:22 AM Alex Plehanov 
> wrote:
>
>> Guys,
>>
>> We are in code-freeze phase now. I've moved almost all non-blocker
>> unresolved tickets from 2.9 to the next release. If you think that
>> some ticket is a blocker and should be included into 2.9 release, please
>> write a note in this thread.
>>
>> There are some tickets with "blocker" priority targeted to 2.9, some of
>> them in "open" state and still unassigned, and I'm not sure we need all of
>> these tickets in 2.9:
>>
>> IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
>> spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
>> yes, can somebody help with resolving this ticket?
>>
>> IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in
>> "Patch available" state. There is a thread on dev-list related to this
>> ticket ([6]), but as far as I understand we still don't have consensus
>> about version for this patch (2.9, 2.10, 3.0).
>>
>> IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
>> perhaps issue is already resolved by some related tickets, there is still
>> no reproducer, no additional details and no work in progress. I propose to
>> move this ticket to the next release.
>>
>> IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
>> from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
>> available" state, but there is no activity since May 2020. Anton
>> Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it
>> still in progress?
>>
>> IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics
>> framework is already released in 2.8 and it's still marked with
>> @IgniteExperemental annotation, I think this ticket is not a blocker. I
>> propose to change the ticket priority and move it to the next release.
>>
>>
>> [1]: https://issues.apache.org/jira/browse/IGNITE-13006
>> [2]: https://issues.apache.org/jira/browse/IGNITE-11942
>> [3]: https://issues.apache.org/jira/browse/IGNITE-12489
>> [4]: https://issues.apache.org/jira/browse/IGNITE-12911
>> [5]: https://issues.apache.org/jira/browse/IGNITE-12553
>> [6]:
>>
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>>
>> пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
>>
>> > Ivan,
>> >
>> > Merged to 2.9.
>> >
>> > Thanks
>> >
>> > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
>> >
>> >> Alex,
>> >>
>> >> Tracing is merged to master:
>> >> https://issues.apache.org/jira/browse/IGNITE-13060
>> >>
>> >> Can you please port it to 2.9?
>> >> For you convenience, there's PR versus 2.9 with conflicts resolved:
>> >> https://github.com/apache/ignite/pull/8046/files
>> >>
>> >> --
>> >> Best Regards,
>> >> Ivan Rakov
>> >>
>> >> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov > >
>> >> wrote:
>> >>
>> >>> Ivan,
>> >>>
>> >>> Looks like master is broken after IGNITE-13246 (but everything is ok
>> in
>> >>> 2.9
>> >>> branch)
>> >>>
>> >>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
>> >>>
>> >>> > Zhenya, Ivan,
>> >>> >
>> >>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
>> branch.
>> >>> > Thank you.
>> >>> >
>> >>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
>> >>> >
>> >>> >> Guys,
>> >>> >>
>> >>> >> can you please backport
>> >>> >> https://issues.apache.org/jira/browse/IGNITE-13246
>> >>> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new
>> events in
>> >>> >> release.
>> >>> >>
>> >>> >> This time I prepared PR with resolved conflicts:
>> >>> >> https://github.com/apache/ignite/pull/8042
>> >>> >>
>> >>> >> Thank you!
>> >>> >>
>> >>> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>> >>> >> > >>> >> >:
>> >>> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > Alex, i also suggest to merge this
>> >>> >> > https://issues.apache.org/jir

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-22 Thread Denis Magda 
Hi Alex,

Thanks for wrapping this up and sharing the progress.

I've continued the discussion in the Hadoop thread. Let's take a couple of
days to solve all open questions. Personally, I don't see any reason to put
the merge off to Ignite 3.0.

Also, I would try to deliver the following two changes in Ignite 2.9:

   - Communication SPI changes [1] and serverless functions support. @Ivan
   Bessonov , the first is completed but no merged.
   The second should be already solved too. Could you please shed some light
   on this?
   - Phasing out Web Console [3]. It's ready for the review and I believe
   that it can be merged quickly. @Alexey Kuznetsov ,
   could you please share your thoughts?

[1] https://issues.apache.org/jira/browse/IGNITE-12438
[2] https://issues.apache.org/jira/browse/IGNITE-13013
[3] https://ggsystems.atlassian.net/browse/IGN-15304

-
Denis


On Wed, Jul 22, 2020 at 12:22 AM Alex Plehanov 
wrote:

> Guys,
>
> We are in code-freeze phase now. I've moved almost all non-blocker
> unresolved tickets from 2.9 to the next release. If you think that
> some ticket is a blocker and should be included into 2.9 release, please
> write a note in this thread.
>
> There are some tickets with "blocker" priority targeted to 2.9, some of
> them in "open" state and still unassigned, and I'm not sure we need all of
> these tickets in 2.9:
>
> IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
> yes, can somebody help with resolving this ticket?
>
> IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in
> "Patch available" state. There is a thread on dev-list related to this
> ticket ([6]), but as far as I understand we still don't have consensus
> about version for this patch (2.9, 2.10, 3.0).
>
> IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
> perhaps issue is already resolved by some related tickets, there is still
> no reproducer, no additional details and no work in progress. I propose to
> move this ticket to the next release.
>
> IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
> from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
> available" state, but there is no activity since May 2020. Anton
> Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it
> still in progress?
>
> IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics
> framework is already released in 2.8 and it's still marked with
> @IgniteExperemental annotation, I think this ticket is not a blocker. I
> propose to change the ticket priority and move it to the next release.
>
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> [6]:
>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>
> пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
>
> > Ivan,
> >
> > Merged to 2.9.
> >
> > Thanks
> >
> > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
> >
> >> Alex,
> >>
> >> Tracing is merged to master:
> >> https://issues.apache.org/jira/browse/IGNITE-13060
> >>
> >> Can you please port it to 2.9?
> >> For you convenience, there's PR versus 2.9 with conflicts resolved:
> >> https://github.com/apache/ignite/pull/8046/files
> >>
> >> --
> >> Best Regards,
> >> Ivan Rakov
> >>
> >> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
> >> wrote:
> >>
> >>> Ivan,
> >>>
> >>> Looks like master is broken after IGNITE-13246 (but everything is ok in
> >>> 2.9
> >>> branch)
> >>>
> >>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
> >>>
> >>> > Zhenya, Ivan,
> >>> >
> >>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> branch.
> >>> > Thank you.
> >>> >
> >>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
> >>> >
> >>> >> Guys,
> >>> >>
> >>> >> can you please backport
> >>> >> https://issues.apache.org/jira/browse/IGNITE-13246
> >>> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events
> in
> >>> >> release.
> >>> >>
> >>> >> This time I prepared PR with resolved conflicts:
> >>> >> https://github.com/apache/ignite/pull/8042
> >>> >>
> >>> >> Thank you!
> >>> >>
> >>> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
> >>> >>  >>> >> >:
> >>> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > Alex, i also suggest to merge this
> >>> >> > https://issues.apache.org/jira/browse/IGNITE-13229 too,
> GridClient
> >>> >> > leakage and further TC OOM preventing.
> >>> >> >
> >>> >> > >Ivan,
> >>> >> > >
> >>> >> > >It was already in release scope as discussed in this thread.
> >>> >> > >
> >>> >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com
> >:
> >>> >> > >
> >>> >> > >> Hi,

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-22 Thread Alex Plehanov 
Guys,

We are in code-freeze phase now. I've moved almost all non-blocker
unresolved tickets from 2.9 to the next release. If you think that
some ticket is a blocker and should be included into 2.9 release, please
write a note in this thread.

There are some tickets with "blocker" priority targeted to 2.9, some of
them in "open" state and still unassigned, and I'm not sure we need all of
these tickets in 2.9:

IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
yes, can somebody help with resolving this ticket?

IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in
"Patch available" state. There is a thread on dev-list related to this
ticket ([6]), but as far as I understand we still don't have consensus
about version for this patch (2.9, 2.10, 3.0).

IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
perhaps issue is already resolved by some related tickets, there is still
no reproducer, no additional details and no work in progress. I propose to
move this ticket to the next release.

IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
available" state, but there is no activity since May 2020. Anton
Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it
still in progress?

IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics
framework is already released in 2.8 and it's still marked with
@IgniteExperemental annotation, I think this ticket is not a blocker. I
propose to change the ticket priority and move it to the next release.


[1]: https://issues.apache.org/jira/browse/IGNITE-13006
[2]: https://issues.apache.org/jira/browse/IGNITE-11942
[3]: https://issues.apache.org/jira/browse/IGNITE-12489
[4]: https://issues.apache.org/jira/browse/IGNITE-12911
[5]: https://issues.apache.org/jira/browse/IGNITE-12553
[6]:
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html

пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :

> Ivan,
>
> Merged to 2.9.
>
> Thanks
>
> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
>
>> Alex,
>>
>> Tracing is merged to master:
>> https://issues.apache.org/jira/browse/IGNITE-13060
>>
>> Can you please port it to 2.9?
>> For you convenience, there's PR versus 2.9 with conflicts resolved:
>> https://github.com/apache/ignite/pull/8046/files
>>
>> --
>> Best Regards,
>> Ivan Rakov
>>
>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
>> wrote:
>>
>>> Ivan,
>>>
>>> Looks like master is broken after IGNITE-13246 (but everything is ok in
>>> 2.9
>>> branch)
>>>
>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
>>>
>>> > Zhenya, Ivan,
>>> >
>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
>>> > Thank you.
>>> >
>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
>>> >
>>> >> Guys,
>>> >>
>>> >> can you please backport
>>> >> https://issues.apache.org/jira/browse/IGNITE-13246
>>> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
>>> >> release.
>>> >>
>>> >> This time I prepared PR with resolved conflicts:
>>> >> https://github.com/apache/ignite/pull/8042
>>> >>
>>> >> Thank you!
>>> >>
>>> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>>> >> >> >> >:
>>> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > Alex, i also suggest to merge this
>>> >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
>>> >> > leakage and further TC OOM preventing.
>>> >> >
>>> >> > >Ivan,
>>> >> > >
>>> >> > >It was already in release scope as discussed in this thread.
>>> >> > >
>>> >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
>>> >> > >
>>> >> > >> Hi,
>>> >> > >>
>>> >> > >> We are still waiting for a final review of Tracing functionality
>>> [1]
>>> >> > until
>>> >> > >> the end of tomorrow (July 15).
>>> >> > >> We anticipate that it will be merged to Ignite master no later
>>> than
>>> >> July
>>> >> > >> 16.
>>> >> > >>
>>> >> > >> Sorry for being a bit late here. Alex P., can you include [1] to
>>> the
>>> >> > >> release scope?
>>> >> > >>
>>> >> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
>>> >> > >>
>>> >> > >> --
>>> >> > >> Best Regards,
>>> >> > >> Ivan Rakov
>>> >> > >>
>>> >> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
>>> >> > akuznet...@gridgain.com >
>>> >> > >> wrote:
>>> >> > >>
>>> >> > >>> Alex,
>>> >> > >>>
>>> >> > >>> Can you cherry-pick to Ignite 2.9 this issue:
>>> >> > >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
>>> >> > >>>
>>> >> > >>> This issue is about BASELINE events and it is very useful for
>>> >> > notification
>>> >> > >>> external tools about changes in baseline.
>>> >> > >>>
>>> >> > >>> Thank you!
>>> >> > >>>
>>> >> > >>> ---
>>> >> > >>> Alexey Kuznetsov
>>> >> > >>>
>>> >> > >>
>>> >> >
>>> >> >
>>> >> >
>>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-16 Thread Alex Plehanov 
Ivan,

Merged to 2.9.

Thanks

пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :

> Alex,
>
> Tracing is merged to master:
> https://issues.apache.org/jira/browse/IGNITE-13060
>
> Can you please port it to 2.9?
> For you convenience, there's PR versus 2.9 with conflicts resolved:
> https://github.com/apache/ignite/pull/8046/files
>
> --
> Best Regards,
> Ivan Rakov
>
> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
> wrote:
>
>> Ivan,
>>
>> Looks like master is broken after IGNITE-13246 (but everything is ok in
>> 2.9
>> branch)
>>
>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
>>
>> > Zhenya, Ivan,
>> >
>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
>> > Thank you.
>> >
>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
>> >
>> >> Guys,
>> >>
>> >> can you please backport
>> >> https://issues.apache.org/jira/browse/IGNITE-13246
>> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
>> >> release.
>> >>
>> >> This time I prepared PR with resolved conflicts:
>> >> https://github.com/apache/ignite/pull/8042
>> >>
>> >> Thank you!
>> >>
>> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>> >> > >> >:
>> >>
>> >> >
>> >> >
>> >> >
>> >> > Alex, i also suggest to merge this
>> >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
>> >> > leakage and further TC OOM preventing.
>> >> >
>> >> > >Ivan,
>> >> > >
>> >> > >It was already in release scope as discussed in this thread.
>> >> > >
>> >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
>> >> > >
>> >> > >> Hi,
>> >> > >>
>> >> > >> We are still waiting for a final review of Tracing functionality
>> [1]
>> >> > until
>> >> > >> the end of tomorrow (July 15).
>> >> > >> We anticipate that it will be merged to Ignite master no later
>> than
>> >> July
>> >> > >> 16.
>> >> > >>
>> >> > >> Sorry for being a bit late here. Alex P., can you include [1] to
>> the
>> >> > >> release scope?
>> >> > >>
>> >> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
>> >> > >>
>> >> > >> --
>> >> > >> Best Regards,
>> >> > >> Ivan Rakov
>> >> > >>
>> >> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
>> >> > akuznet...@gridgain.com >
>> >> > >> wrote:
>> >> > >>
>> >> > >>> Alex,
>> >> > >>>
>> >> > >>> Can you cherry-pick to Ignite 2.9 this issue:
>> >> > >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
>> >> > >>>
>> >> > >>> This issue is about BASELINE events and it is very useful for
>> >> > notification
>> >> > >>> external tools about changes in baseline.
>> >> > >>>
>> >> > >>> Thank you!
>> >> > >>>
>> >> > >>> ---
>> >> > >>> Alexey Kuznetsov
>> >> > >>>
>> >> > >>
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Sincerely yours,
>> >> Ivan Bessonov
>> >>
>> >
>>
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-16 Thread Ivan Rakov 
Alex,

Tracing is merged to master:
https://issues.apache.org/jira/browse/IGNITE-13060

Can you please port it to 2.9?
For you convenience, there's PR versus 2.9 with conflicts resolved:
https://github.com/apache/ignite/pull/8046/files

--
Best Regards,
Ivan Rakov

On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
wrote:

> Ivan,
>
> Looks like master is broken after IGNITE-13246 (but everything is ok in 2.9
> branch)
>
> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :
>
> > Zhenya, Ivan,
> >
> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
> > Thank you.
> >
> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
> >
> >> Guys,
> >>
> >> can you please backport
> >> https://issues.apache.org/jira/browse/IGNITE-13246
> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
> >> release.
> >>
> >> This time I prepared PR with resolved conflicts:
> >> https://github.com/apache/ignite/pull/8042
> >>
> >> Thank you!
> >>
> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
> >>  >> >:
> >>
> >> >
> >> >
> >> >
> >> > Alex, i also suggest to merge this
> >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
> >> > leakage and further TC OOM preventing.
> >> >
> >> > >Ivan,
> >> > >
> >> > >It was already in release scope as discussed in this thread.
> >> > >
> >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
> >> > >
> >> > >> Hi,
> >> > >>
> >> > >> We are still waiting for a final review of Tracing functionality
> [1]
> >> > until
> >> > >> the end of tomorrow (July 15).
> >> > >> We anticipate that it will be merged to Ignite master no later than
> >> July
> >> > >> 16.
> >> > >>
> >> > >> Sorry for being a bit late here. Alex P., can you include [1] to
> the
> >> > >> release scope?
> >> > >>
> >> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
> >> > >>
> >> > >> --
> >> > >> Best Regards,
> >> > >> Ivan Rakov
> >> > >>
> >> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
> >> > akuznet...@gridgain.com >
> >> > >> wrote:
> >> > >>
> >> > >>> Alex,
> >> > >>>
> >> > >>> Can you cherry-pick to Ignite 2.9 this issue:
> >> > >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
> >> > >>>
> >> > >>> This issue is about BASELINE events and it is very useful for
> >> > notification
> >> > >>> external tools about changes in baseline.
> >> > >>>
> >> > >>> Thank you!
> >> > >>>
> >> > >>> ---
> >> > >>> Alexey Kuznetsov
> >> > >>>
> >> > >>
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Sincerely yours,
> >> Ivan Bessonov
> >>
> >
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-15 Thread Alex Plehanov 
Ivan,

Looks like master is broken after IGNITE-13246 (but everything is ok in 2.9
branch)

ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :

> Zhenya, Ivan,
>
> I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
> Thank you.
>
> ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
>
>> Guys,
>>
>> can you please backport
>> https://issues.apache.org/jira/browse/IGNITE-13246
>> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
>> release.
>>
>> This time I prepared PR with resolved conflicts:
>> https://github.com/apache/ignite/pull/8042
>>
>> Thank you!
>>
>> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
>> > >:
>>
>> >
>> >
>> >
>> > Alex, i also suggest to merge this
>> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
>> > leakage and further TC OOM preventing.
>> >
>> > >Ivan,
>> > >
>> > >It was already in release scope as discussed in this thread.
>> > >
>> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
>> > >
>> > >> Hi,
>> > >>
>> > >> We are still waiting for a final review of Tracing functionality [1]
>> > until
>> > >> the end of tomorrow (July 15).
>> > >> We anticipate that it will be merged to Ignite master no later than
>> July
>> > >> 16.
>> > >>
>> > >> Sorry for being a bit late here. Alex P., can you include [1] to the
>> > >> release scope?
>> > >>
>> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
>> > >>
>> > >> --
>> > >> Best Regards,
>> > >> Ivan Rakov
>> > >>
>> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
>> > akuznet...@gridgain.com >
>> > >> wrote:
>> > >>
>> > >>> Alex,
>> > >>>
>> > >>> Can you cherry-pick to Ignite 2.9 this issue:
>> > >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
>> > >>>
>> > >>> This issue is about BASELINE events and it is very useful for
>> > notification
>> > >>> external tools about changes in baseline.
>> > >>>
>> > >>> Thank you!
>> > >>>
>> > >>> ---
>> > >>> Alexey Kuznetsov
>> > >>>
>> > >>
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Sincerely yours,
>> Ivan Bessonov
>>
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-15 Thread Alex Plehanov 
Zhenya, Ivan,

I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
Thank you.

ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :

> Guys,
>
> can you please backport https://issues.apache.org/jira/browse/IGNITE-13246
> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
> release.
>
> This time I prepared PR with resolved conflicts:
> https://github.com/apache/ignite/pull/8042
>
> Thank you!
>
> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky  >:
>
> >
> >
> >
> > Alex, i also suggest to merge this
> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
> > leakage and further TC OOM preventing.
> >
> > >Ivan,
> > >
> > >It was already in release scope as discussed in this thread.
> > >
> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
> > >
> > >> Hi,
> > >>
> > >> We are still waiting for a final review of Tracing functionality [1]
> > until
> > >> the end of tomorrow (July 15).
> > >> We anticipate that it will be merged to Ignite master no later than
> July
> > >> 16.
> > >>
> > >> Sorry for being a bit late here. Alex P., can you include [1] to the
> > >> release scope?
> > >>
> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
> > >>
> > >> --
> > >> Best Regards,
> > >> Ivan Rakov
> > >>
> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
> > akuznet...@gridgain.com >
> > >> wrote:
> > >>
> > >>> Alex,
> > >>>
> > >>> Can you cherry-pick to Ignite 2.9 this issue:
> > >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
> > >>>
> > >>> This issue is about BASELINE events and it is very useful for
> > notification
> > >>> external tools about changes in baseline.
> > >>>
> > >>> Thank you!
> > >>>
> > >>> ---
> > >>> Alexey Kuznetsov
> > >>>
> > >>
> >
> >
> >
> >
>
>
>
> --
> Sincerely yours,
> Ivan Bessonov
>

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-15 Thread Ivan Bessonov 
Guys,

can you please backport https://issues.apache.org/jira/browse/IGNITE-13246
to ignite-2.9? Me and Alexey Kuznetsov really want these new events in
release.

This time I prepared PR with resolved conflicts:
https://github.com/apache/ignite/pull/8042

Thank you!

вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky :

>
>
>
> Alex, i also suggest to merge this
> https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
> leakage and further TC OOM preventing.
>
> >Ivan,
> >
> >It was already in release scope as discussed in this thread.
> >
> >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
> >
> >> Hi,
> >>
> >> We are still waiting for a final review of Tracing functionality [1]
> until
> >> the end of tomorrow (July 15).
> >> We anticipate that it will be merged to Ignite master no later than July
> >> 16.
> >>
> >> Sorry for being a bit late here. Alex P., can you include [1] to the
> >> release scope?
> >>
> >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
> >>
> >> --
> >> Best Regards,
> >> Ivan Rakov
> >>
> >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov <
> akuznet...@gridgain.com >
> >> wrote:
> >>
> >>> Alex,
> >>>
> >>> Can you cherry-pick to Ignite 2.9 this issue:
> >>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
> >>>
> >>> This issue is about BASELINE events and it is very useful for
> notification
> >>> external tools about changes in baseline.
> >>>
> >>> Thank you!
> >>>
> >>> ---
> >>> Alexey Kuznetsov
> >>>
> >>
>
>
>
>



-- 
Sincerely yours,
Ivan Bessonov

Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-14 Thread Zhenya Stanilovsky 


 
Alex, i also suggest to merge this 
https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient leakage and 
further TC OOM preventing.
 
>Ivan,
>
>It was already in release scope as discussed in this thread.
>
>вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >:
> 
>> Hi,
>>
>> We are still waiting for a final review of Tracing functionality [1] until
>> the end of tomorrow (July 15).
>> We anticipate that it will be merged to Ignite master no later than July
>> 16.
>>
>> Sorry for being a bit late here. Alex P., can you include [1] to the
>> release scope?
>>
>> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
>>
>> --
>> Best Regards,
>> Ivan Rakov
>>
>> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov < akuznet...@gridgain.com >
>> wrote:
>>
>>> Alex,
>>>
>>> Can you cherry-pick to Ignite 2.9 this issue:
>>>  https://issues.apache.org/jira/browse/IGNITE-13246 ?
>>>
>>> This issue is about BASELINE events and it is very useful for notification
>>> external tools about changes in baseline.
>>>
>>> Thank you!
>>>
>>> ---
>>> Alexey Kuznetsov
>>>
>>