Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[dmagda]

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 <[hidden email]> 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 <[hidden email]>, 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
>    <[hidden email]>, 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 <[hidden email]>
> 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 <[hidden email]>:
>>
>> > Ivan,
>> >
>> > Merged to 2.9.
>> >
>> > Thanks
>> >
>> > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
>> >
>> >> 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 <[hidden email]
>> >
>> >> wrote:
>> >>
>> >>> Ivan,
>> >>>
>> >>> Looks like master is broken after IGNITE-13246 (but everything is ok
>> in
>> >>> 2.9
>> >>> branch)
>> >>>
>> >>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <[hidden email]>:
>> >>>
>> >>> > Zhenya, Ivan,
>> >>> >
>> >>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
>> branch.
>> >>> > Thank you.
>> >>> >
>> >>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <[hidden email]>:
>> >>> >
>> >>> >> 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
>> >>> >> <[hidden email]
>> >>> >> >:
>> >>> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > 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 < [hidden email]
>> >:
>> >>> >> > >
>> >>> >> > >> 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 <
>> >>> >> > [hidden email] >
>> >>> >> > >> 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
>> >>> >>
>> >>> >
>> >>>
>> >>
>>
>

[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 <[hidden email]>:

> 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 <[hidden email]> 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 <[hidden email]>, 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
> >    <[hidden email]>, 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 <[hidden email]>
> > 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 <[hidden email]>:
> >>
> >> > Ivan,
> >> >
> >> > Merged to 2.9.
> >> >
> >> > Thanks
> >> >
> >> > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
> >> >
> >> >> 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 <
> [hidden email]
> >> >
> >> >> wrote:
> >> >>
> >> >>> Ivan,
> >> >>>
> >> >>> Looks like master is broken after IGNITE-13246 (but everything is ok
> >> in
> >> >>> 2.9
> >> >>> branch)
> >> >>>
> >> >>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <[hidden email]
> >:
> >> >>>
> >> >>> > Zhenya, Ivan,
> >> >>> >
> >> >>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> >> branch.
> >> >>> > Thank you.
> >> >>> >
> >> >>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <[hidden email]
> >:
> >> >>> >
> >> >>> >> 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
> >> >>> >> <[hidden email]
> >> >>> >> >:
> >> >>> >>
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> > 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 <
> [hidden email]
> >> >:
> >> >>> >> > >
> >> >>> >> > >> 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 <
> >> >>> >> > [hidden email] >
> >> >>> >> > >> 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
> >> >>> >>
> >> >>> >
> >> >>>
> >> >>
> >>
> >
>

--
Sincerely yours,
Ivan Bessonov

[Alexey Kuznetsov-2]

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

[Alexey Plekhanov]

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 <[hidden email]>:

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

[Denis Mekhanikov]

Guys,

Is there a chance to squeeze the fix for the following issue in:
https://issues.apache.org/jira/browse/IGNITE-13306
<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 <[hidden email]>:

> 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 <[hidden email]>:
>
> > 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
> >
> >
>

[Ilya Kasnacheev]

Hello!

I don't think that IGNITE-13006
<https://issues.apache.org/jira/browse/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 <[hidden email]>:

> 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 <[hidden email]>:
>
>> Ivan,
>>
>> Merged to 2.9.
>>
>> Thanks
>>
>> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
>>
>>> 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 <[hidden email]>
>>> wrote:
>>>
>>>> Ivan,
>>>>
>>>> Looks like master is broken after IGNITE-13246 (but everything is ok in
>>>> 2.9
>>>> branch)
>>>>
>>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <[hidden email]>:
>>>>
>>>> > Zhenya, Ivan,
>>>> >
>>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
>>>> > Thank you.
>>>> >
>>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <[hidden email]>:
>>>> >
>>>> >> 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
>>>> >> <[hidden email]
>>>> >> >:
>>>> >>
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > 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 < [hidden email]
>>>> >:
>>>> >> > >
>>>> >> > >> 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 <
>>>> >> > [hidden email] >
>>>> >> > >> 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
>>>> >>
>>>> >
>>>>
>>>

[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 <[hidden email]>
wrote:

> Hello!
>
> I don't think that IGNITE-13006
> <https://issues.apache.org/jira/browse/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 <[hidden email]>:
>
> > 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 <[hidden email]>:
> >
> >> Ivan,
> >>
> >> Merged to 2.9.
> >>
> >> Thanks
> >>
> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
> >>
> >>> 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 <[hidden email]
> >
> >>> wrote:
> >>>
> >>>> Ivan,
> >>>>
> >>>> Looks like master is broken after IGNITE-13246 (but everything is ok
> in
> >>>> 2.9
> >>>> branch)
> >>>>
> >>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <[hidden email]>:
> >>>>
> >>>> > Zhenya, Ivan,
> >>>> >
> >>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> branch.
> >>>> > Thank you.
> >>>> >
> >>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <[hidden email]>:
> >>>> >
> >>>> >> 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
> >>>> >> <[hidden email]
> >>>> >> >:
> >>>> >>
> >>>> >> >
> >>>> >> >
> >>>> >> >
> >>>> >> > 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 < [hidden email]
> >>>> >:
> >>>> >> > >
> >>>> >> > >> 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 <
> >>>> >> > [hidden email] >
> >>>> >> > >> 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
> >>>> >>
> >>>> >
> >>>>
> >>>
>

[Alexey Plekhanov]

Ivan,

IGNITE-13306 cherry-picked to 2.9

пт, 31 июл. 2020 г. в 13:43, Ivan Rakov <[hidden email]>:

> 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 <[hidden email]>
> wrote:
>
>> Hello!
>>
>> I don't think that IGNITE-13006
>> <https://issues.apache.org/jira/browse/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 <[hidden email]>:
>>
>> > 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 <[hidden email]>:
>> >
>> >> Ivan,
>> >>
>> >> Merged to 2.9.
>> >>
>> >> Thanks
>> >>
>> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
>> >>
>> >>> 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 <
>> [hidden email]>
>> >>> wrote:
>> >>>
>> >>>> Ivan,
>> >>>>
>> >>>> Looks like master is broken after IGNITE-13246 (but everything is ok
>> in
>> >>>> 2.9
>> >>>> branch)
>> >>>>
>> >>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <[hidden email]
>> >:
>> >>>>
>> >>>> > Zhenya, Ivan,
>> >>>> >
>> >>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
>> branch.
>> >>>> > Thank you.
>> >>>> >
>> >>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <[hidden email]
>> >:
>> >>>> >
>> >>>> >> 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
>> >>>> >> <[hidden email]
>> >>>> >> >:
>> >>>> >>
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > 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 <
>> [hidden email]
>> >>>> >:
>> >>>> >> > >
>> >>>> >> > >> 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 <
>> >>>> >> > [hidden email] >
>> >>>> >> > >> 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
>> >>>> >>
>> >>>> >
>> >>>>
>> >>>
>>
>

[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 <[hidden email]>:

> Ivan,
>
> IGNITE-13306 cherry-picked to 2.9
>
> пт, 31 июл. 2020 г. в 13:43, Ivan Rakov <[hidden email]>:
>
> > 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 <
> [hidden email]>
> > wrote:
> >
> >> Hello!
> >>
> >> I don't think that IGNITE-13006
> >> <https://issues.apache.org/jira/browse/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 <[hidden email]>:
> >>
> >> > 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 <[hidden email]>:
> >> >
> >> >> Ivan,
> >> >>
> >> >> Merged to 2.9.
> >> >>
> >> >> Thanks
> >> >>
> >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
> >> >>
> >> >>> 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 <
> >> [hidden email]>
> >> >>> wrote:
> >> >>>
> >> >>>> Ivan,
> >> >>>>
> >> >>>> Looks like master is broken after IGNITE-13246 (but everything is
> ok
> >> in
> >> >>>> 2.9
> >> >>>> branch)
> >> >>>>
> >> >>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <
> [hidden email]
> >> >:
> >> >>>>
> >> >>>> > Zhenya, Ivan,
> >> >>>> >
> >> >>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> >> branch.
> >> >>>> > Thank you.
> >> >>>> >
> >> >>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <
> [hidden email]
> >> >:
> >> >>>> >
> >> >>>> >> 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
> >> >>>> >> <[hidden email]
> >> >>>> >> >:
> >> >>>> >>
> >> >>>> >> >
> >> >>>> >> >
> >> >>>> >> >
> >> >>>> >> > 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 <
> >> [hidden email]
> >> >>>> >:
> >> >>>> >> > >
> >> >>>> >> > >> 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 <
> >> >>>> >> > [hidden email] >
> >> >>>> >> > >> 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
> >> >>>> >>
> >> >>>> >
> >> >>>>
> >> >>>
> >>
> >
>

--
Sincerely yours, Ivan Daschinskiy

[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 <[hidden email]>:

> 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 <[hidden email]>:
>
> > Ivan,
> >
> > IGNITE-13306 cherry-picked to 2.9
> >
> > пт, 31 июл. 2020 г. в 13:43, Ivan Rakov <[hidden email]>:
> >
> > > 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 <
> > [hidden email]>
> > > wrote:
> > >
> > >> Hello!
> > >>
> > >> I don't think that IGNITE-13006
> > >> <https://issues.apache.org/jira/browse/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 <[hidden email]>:
> > >>
> > >> > 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 <[hidden email]
> >:
> > >> >
> > >> >> Ivan,
> > >> >>
> > >> >> Merged to 2.9.
> > >> >>
> > >> >> Thanks
> > >> >>
> > >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
> > >> >>
> > >> >>> 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 <
> > >> [hidden email]>
> > >> >>> wrote:
> > >> >>>
> > >> >>>> Ivan,
> > >> >>>>
> > >> >>>> Looks like master is broken after IGNITE-13246 (but everything is
> > ok
> > >> in
> > >> >>>> 2.9
> > >> >>>> branch)
> > >> >>>>
> > >> >>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <
> > [hidden email]
> > >> >:
> > >> >>>>
> > >> >>>> > Zhenya, Ivan,
> > >> >>>> >
> > >> >>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9
> > >> branch.
> > >> >>>> > Thank you.
> > >> >>>> >
> > >> >>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <
> > [hidden email]
> > >> >:
> > >> >>>> >
> > >> >>>> >> 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
> > >> >>>> >> <[hidden email]
> > >> >>>> >> >:
> > >> >>>> >>
> > >> >>>> >> >
> > >> >>>> >> >
> > >> >>>> >> >
> > >> >>>> >> > 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 <
> > >> [hidden email]
> > >> >>>> >:
> > >> >>>> >> > >
> > >> >>>> >> > >> 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 <
> > >> >>>> >> > [hidden email] >
> > >> >>>> >> > >> 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
> > >> >>>> >>
> > >> >>>> >
> > >> >>>>
> > >> >>>
> > >>
> > >
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy
>

[Alexey Plekhanov]

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 <[hidden email]>:

> 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 <[hidden email]>:
>
> > 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 <[hidden email]>:
> >
> > > Ivan,
> > >
> > > IGNITE-13306 cherry-picked to 2.9
> > >
> > > пт, 31 июл. 2020 г. в 13:43, Ivan Rakov <[hidden email]>:
> > >
> > > > 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 <
> > > [hidden email]>
> > > > wrote:
> > > >
> > > >> Hello!
> > > >>
> > > >> I don't think that IGNITE-13006
> > > >> <https://issues.apache.org/jira/browse/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 <[hidden email]
> >:
> > > >>
> > > >> > 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 <
> [hidden email]
> > >:
> > > >> >
> > > >> >> Ivan,
> > > >> >>
> > > >> >> Merged to 2.9.
> > > >> >>
> > > >> >> Thanks
> > > >> >>
> > > >> >> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
> > > >> >>
> > > >> >>> 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 <
> > > >> [hidden email]>
> > > >> >>> wrote:
> > > >> >>>
> > > >> >>>> Ivan,
> > > >> >>>>
> > > >> >>>> Looks like master is broken after IGNITE-13246 (but everything
> is
> > > ok
> > > >> in
> > > >> >>>> 2.9
> > > >> >>>> branch)
> > > >> >>>>
> > > >> >>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <
> > > [hidden email]
> > > >> >:
> > > >> >>>>
> > > >> >>>> > Zhenya, Ivan,
> > > >> >>>> >
> > > >> >>>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to
> ignite-2.9
> > > >> branch.
> > > >> >>>> > Thank you.
> > > >> >>>> >
> > > >> >>>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <
> > > [hidden email]
> > > >> >:
> > > >> >>>> >
> > > >> >>>> >> 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
> > > >> >>>> >> <[hidden email]
> > > >> >>>> >> >:
> > > >> >>>> >>
> > > >> >>>> >> >
> > > >> >>>> >> >
> > > >> >>>> >> >
> > > >> >>>> >> > 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 <
> > > >> [hidden email]
> > > >> >>>> >:
> > > >> >>>> >> > >
> > > >> >>>> >> > >> 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 <
> > > >> >>>> >> > [hidden email] >
> > > >> >>>> >> > >> 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
> > > >> >>>> >>
> > > >> >>>> >
> > > >> >>>>
> > > >> >>>
> > > >>
> > > >
> > >
> >
> >
> > --
> > Sincerely yours, Ivan Daschinskiy
> >
>

[Artem Budnikov]

Hi Everyone,

I looked at the documentation tasks for Ignite 2.9 [1] and noticed that
some of them were being worked on. I'll take a look at the other tickets
(unassigned or assigned to me). I hope I'll have enough time to finish
them by the time of the release.

-Artem

[1]:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9#ApacheIgnite2.9-Documentationtasksforimportantfeaturesimplementedin2.9

On 06.08.2020 15:05, Alex Plehanov wrote:

> 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 <[hidden email]>:
>
>> 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 <[hidden email]>:
>>
>>> 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 <[hidden email]>:
>>>
>>>> Ivan,
>>>>
>>>> IGNITE-13306 cherry-picked to 2.9
>>>>
>>>> пт, 31 июл. 2020 г. в 13:43, Ivan Rakov <[hidden email]>:
>>>>
>>>>> 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 <
>>>> [hidden email]>
>>>>> wrote:
>>>>>
>>>>>> Hello!
>>>>>>
>>>>>> I don't think that IGNITE-13006
>>>>>> <https://issues.apache.org/jira/browse/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 <[hidden email]
>>> :
>>>>>>> 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 <
>> [hidden email]
>>>> :
>>>>>>>> Ivan,
>>>>>>>>
>>>>>>>> Merged to 2.9.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <[hidden email]>:
>>>>>>>>
>>>>>>>>> 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 <
>>>>>> [hidden email]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Ivan,
>>>>>>>>>>
>>>>>>>>>> Looks like master is broken after IGNITE-13246 (but everything
>> is
>>>> ok
>>>>>> in
>>>>>>>>>> 2.9
>>>>>>>>>> branch)
>>>>>>>>>>
>>>>>>>>>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <
>>>> [hidden email]
>>>>>>> :
>>>>>>>>>>> Zhenya, Ivan,
>>>>>>>>>>>
>>>>>>>>>>> I've cherry-picked IGNITE-13229 and IGNITE-13246 to
>> ignite-2.9
>>>>>> branch.
>>>>>>>>>>> Thank you.
>>>>>>>>>>>
>>>>>>>>>>> ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <
>>>> [hidden email]
>>>>>>> :
>>>>>>>>>>>> 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
>>>>>>>>>>>> <[hidden email]
>>>>>>>>>>>>> :
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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 <
>>>>>> [hidden email]
>>>>>>>>>>> :
>>>>>>>>>>>>>>> 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 <
>>>>>>>>>>>>> [hidden email] >
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>
>>> --
>>> Sincerely yours, Ivan Daschinskiy
>>>

What is the release date for 2.9, from the cwiki it still says August 7 :
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[Alexey Plekhanov]

Hello,

> What is the release date for 2.9, from the cwiki it still says August 7
We have a performance drop on the new release and still trying to find the
problematic commit. I hope we will find it in a week + there are one or two
weeks needed for voting and further release steps.

пт, 14 авг. 2020 г. в 11:01, [hidden email] <[hidden email]
>:

> What is the release date for 2.9, from the cwiki it still says August 7 :
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[Pavel Tupitsyn]

Alex,

What's the status of the release?
Can we include a bug fix there [1]?

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

On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov <[hidden email]>
wrote:

> Hello,
>
> > What is the release date for 2.9, from the cwiki it still says August 7
> We have a performance drop on the new release and still trying to find the
> problematic commit. I hope we will find it in a week + there are one or two
> weeks needed for voting and further release steps.
>
> пт, 14 авг. 2020 г. в 11:01, [hidden email] <
> [hidden email]
> >:
>
> > What is the release date for 2.9, from the cwiki it still says August 7 :
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

[Alexey Plekhanov]

Pavel,

We still can't find the root cause of performance drop.

Ticket IGNITE-13369 still in progress. When it will be resolved? Is it
really critical bug? According to the user-list thread attached to the
ticket, there is a workaround exists for this problem and looks like it's
not so critical.

вт, 18 авг. 2020 г. в 12:30, Pavel Tupitsyn <[hidden email]>:

> Alex,
>
> What's the status of the release?
> Can we include a bug fix there [1]?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13369
>
> On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov <[hidden email]>
> wrote:
>
> > Hello,
> >
> > > What is the release date for 2.9, from the cwiki it still says August 7
> > We have a performance drop on the new release and still trying to find
> the
> > problematic commit. I hope we will find it in a week + there are one or
> two
> > weeks needed for voting and further release steps.
> >
> > пт, 14 авг. 2020 г. в 11:01, [hidden email] <
> > [hidden email]
> > >:
> >
> > > What is the release date for 2.9, from the cwiki it still says August
> 7 :
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>

[Pavel Tupitsyn]

Ok, I'm just asking, there is no rush for this ticket.
If the release is postponed anyway, I thought that we can include more
fixes.

On Tue, Aug 18, 2020 at 8:10 PM Alex Plehanov <[hidden email]>
wrote:

> Pavel,
>
> We still can't find the root cause of performance drop.
>
> Ticket IGNITE-13369 still in progress. When it will be resolved? Is it
> really critical bug? According to the user-list thread attached to the
> ticket, there is a workaround exists for this problem and looks like it's
> not so critical.
>
> вт, 18 авг. 2020 г. в 12:30, Pavel Tupitsyn <[hidden email]>:
>
> > Alex,
> >
> > What's the status of the release?
> > Can we include a bug fix there [1]?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-13369
> >
> > On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov <[hidden email]>
> > wrote:
> >
> > > Hello,
> > >
> > > > What is the release date for 2.9, from the cwiki it still says
> August 7
> > > We have a performance drop on the new release and still trying to find
> > the
> > > problematic commit. I hope we will find it in a week + there are one or
> > two
> > > weeks needed for voting and further release steps.
> > >
> > > пт, 14 авг. 2020 г. в 11:01, [hidden email] <
> > > [hidden email]
> > > >:
> > >
> > > > What is the release date for 2.9, from the cwiki it still says August
> > 7 :
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > >
> >
>

[Artem Budnikov]

Hi everyone,

We've set up a staging site for the Ignite 2.9 docs:
http://64.227.57.229/docs/2.9.0/installation/installing-using-docker

user/pass: ignite/apache2020

More content is being added, but that's basically what it will look like.

Your comments are welcome.

-Artem

On 18.08.2020 22:01, Pavel Tupitsyn wrote:

> Ok, I'm just asking, there is no rush for this ticket.
> If the release is postponed anyway, I thought that we can include more
> fixes.
>
> On Tue, Aug 18, 2020 at 8:10 PM Alex Plehanov <[hidden email]>
> wrote:
>
>> Pavel,
>>
>> We still can't find the root cause of performance drop.
>>
>> Ticket IGNITE-13369 still in progress. When it will be resolved? Is it
>> really critical bug? According to the user-list thread attached to the
>> ticket, there is a workaround exists for this problem and looks like it's
>> not so critical.
>>
>> вт, 18 авг. 2020 г. в 12:30, Pavel Tupitsyn <[hidden email]>:
>>
>>> Alex,
>>>
>>> What's the status of the release?
>>> Can we include a bug fix there [1]?
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-13369
>>>
>>> On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov <[hidden email]>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>>> What is the release date for 2.9, from the cwiki it still says
>> August 7
>>>> We have a performance drop on the new release and still trying to find
>>> the
>>>> problematic commit. I hope we will find it in a week + there are one or
>>> two
>>>> weeks needed for voting and further release steps.
>>>>
>>>> пт, 14 авг. 2020 г. в 11:01, [hidden email] <
>>>> [hidden email]
>>>>> :
>>>>> What is the release date for 2.9, from the cwiki it still says August
>>> 7 :
>>>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>>>>

[Ilya Kasnacheev]

Hello!

Search does not seem to work. Are we going to have a proper search results
page? It is often the case that there's none.

I can see that note blocks are just annotated with "Note." Can we have some
image there? Example is
http://64.227.57.229/docs/2.9.0/persistence/persistence-tuning

Regards,
--
Ilya Kasnacheev


ср, 19 авг. 2020 г. в 13:48, Artem Budnikov <[hidden email]>:

> Hi everyone,
>
> We've set up a staging site for the Ignite 2.9 docs:
> http://64.227.57.229/docs/2.9.0/installation/installing-using-docker
>
> user/pass: ignite/apache2020
>
> More content is being added, but that's basically what it will look like.
>
> Your comments are welcome.
>
> -Artem
>
> On 18.08.2020 22:01, Pavel Tupitsyn wrote:
> > Ok, I'm just asking, there is no rush for this ticket.
> > If the release is postponed anyway, I thought that we can include more
> > fixes.
> >
> > On Tue, Aug 18, 2020 at 8:10 PM Alex Plehanov <[hidden email]>
> > wrote:
> >
> >> Pavel,
> >>
> >> We still can't find the root cause of performance drop.
> >>
> >> Ticket IGNITE-13369 still in progress. When it will be resolved? Is it
> >> really critical bug? According to the user-list thread attached to the
> >> ticket, there is a workaround exists for this problem and looks like
> it's
> >> not so critical.
> >>
> >> вт, 18 авг. 2020 г. в 12:30, Pavel Tupitsyn <[hidden email]>:
> >>
> >>> Alex,
> >>>
> >>> What's the status of the release?
> >>> Can we include a bug fix there [1]?
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-13369
> >>>
> >>> On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov <
> [hidden email]>
> >>> wrote:
> >>>
> >>>> Hello,
> >>>>
> >>>>> What is the release date for 2.9, from the cwiki it still says
> >> August 7
> >>>> We have a performance drop on the new release and still trying to find
> >>> the
> >>>> problematic commit. I hope we will find it in a week + there are one
> or
> >>> two
> >>>> weeks needed for voting and further release steps.
> >>>>
> >>>> пт, 14 авг. 2020 г. в 11:01, [hidden email] <
> >>>> [hidden email]
> >>>>> :
> >>>>> What is the release date for 2.9, from the cwiki it still says August
> >>> 7 :
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >>>>>
>

[Artem Budnikov]

> Search does not seem to work.
It uses mockups right now, but it should be ready when the docs are
released.

> I can see that note blocks are just annotated with "Note." Can we have some
> image there?
Do you have a preference as to which image you would like to see there?

-Artem

On 19.08.2020 17:37, Ilya Kasnacheev wrote:

> Hello!
>
> Search does not seem to work. Are we going to have a proper search results
> page? It is often the case that there's none.
>
> I can see that note blocks are just annotated with "Note." Can we have some
> image there? Example is
> http://64.227.57.229/docs/2.9.0/persistence/persistence-tuning
>
> Regards,