Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Alexey Zinoviev]

Igniters

Unfortunately, the ML model export/import feature
<https://issues.apache.org/jira/browse/IGNITE-6642> is under development
yet.
I need to delay it before the 2.10 release.



пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]>:

> Denis,
>
> Yes, I still ready to manage it.
> Today I will prepare a release page on wiki and will try to go over tickets
> list.
> Also, I have plans to cut the branch by the end of next week if there are
> no objections.
>
>
> пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
>
> > Igniters,
> >
> > Are we moving forward with this release? Alex Plehanov, are you still
> ready
> > to manage it? It seems like everyone agreed with the timeline you
> proposed
> > in the very beginning.
> >
> > -
> > Denis
> >
> >
> > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]> wrote:
> >
> > > Sergey, Ivan,
> > >
> > > Could you please check the questions below? If it's time-consuming to
> > > rework continuous queries, then the new mode can become available in
> the
> > > experimental state and should not let register continuous queries to
> > avoid
> > > potential deadlocks. Overall, this design gap in continuous queries was
> > > like a bomb that has just detonated [1]. Anyway, this new connectivity
> > mode
> > > will be priceless even if you can't use continuous queries with them
> > > because right now we cannot even start a thick client inside of a
> > > serverless function.
> > >
> > > Alexey Plehanov,
> > >
> > > It looks like we can proceed with the release taking your timelines.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <[hidden email]> wrote:
> > >
> > >> Ivan, Sergey,
> > >>
> > >> How much effort should we put to resolve the issue with
> > >> continuous queries? Are you working on that issue actively? Let's try
> to
> > >> guess what would be the ETA.
> > >>
> > >> -
> > >> Denis
> > >>
> > >>
> > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <[hidden email]>
> > >> wrote:
> > >>
> > >>> Hello,
> > >>>
> > >>> Sorry for the delay. Sergey Chugunov ([hidden email])
> just
> > >>> replied
> > >>> to the main conversation about "communication via discovery" [1]. We
> > >>> work on it
> > >>> together and recently have found one hard-to-fix scenario, detailed
> > >>> description is
> > >>> provided in Sergey's reply.
> > >>>
> > >>> In short, July 10th looks realistic only if we introduce new behavior
> > in
> > >>> its current
> > >>> implementation, with new setting and IgniteExperimental status.
> Blocker
> > >>> here is
> > >>> current implementation of Continuos Query protocol that in some cases
> > >>> (described
> > >>> at the end) initiates TCP connection right from discovery thread
> which
> > >>> obviously
> > >>> leads to deadlock. We haven't estimated efforts needed to redesign of
> > CQ
> > >>> protocol
> > >>> but it is definitely a risk and fixing it isn't feasible with a code
> > >>> freeze at 10th of July.
> > >>> So my verdict: we can include this new feature in 2.9 scope as
> > >>> experimental and with
> > >>> highlighted limitation on CQ usage. Is that OK?
> > >>>
> > >>> CQ limitation: server needs to open a communication connection to the
> > >>> client if during
> > >>> CQ registration client tries to p2p deploy new class not available on
> > >>> server classpath.
> > >>> In other cases registration of CQ should be fine.
> > >>>
> > >>> [1]
> > >>>
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > >>>
> > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <[hidden email]>:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> Indeed, the tracing feature is almost ready. Discovery,
> communication
> > >>>> and
> > >>>> transactions tracing will be introduced, as well as an option to
> > >>>> configure
> > >>>> tracing in runtime. Right now we are working on final performance
> > >>>> optimizations, but it's very likely that we'll complete this
> activity
> > >>>> before the code freeze date.
> > >>>> Let's include tracing to the 2.9 release scope.
> > >>>>
> > >>>> More info:
> > >>>>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> > >>>>
> > >>>> --
> > >>>> Best Regards,
> > >>>> Ivan Rakov
> > >>>>
> > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <[hidden email]>
> wrote:
> > >>>>
> > >>>> > Hi folks,
> > >>>> >
> > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable to me.
> > I'd
> > >>>> like
> > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]>, who is
> > >>>> about to
> > >>>> > finish with the tracing support, and @Ivan Bessonov
> > >>>> > <[hidden email]>, who is fixing a serious limitation for
> K8
> > >>>> > deployments [1]. Most likely, both features will be ready by the
> > code
> > >>>> > freeze date (July 10), but the guys should know it better.
> > >>>> >
> > >>>> > [1]
> > >>>> >
> > >>>>
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > >>>> >
> > >>>> > -
> > >>>> > Denis
> > >>>> >
> > >>>> >
> > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> > [hidden email]
> > >>>> >
> > >>>> > wrote:
> > >>>> >
> > >>>> >> Hello Igniters,
> > >>>> >>
> > >>>> >> AI 2.8.1 is finally released and as we discussed here [1] its
> time
> > to
> > >>>> >> start
> > >>>> >> the discussion about 2.9 release.
> > >>>> >>
> > >>>> >> I want to propose myself to be the release manager of the 2.9
> > >>>> release.
> > >>>> >>
> > >>>> >> What about release time, I agree with Maxim that we should
> deliver
> > >>>> >> features
> > >>>> >> as frequently as possible. If some feature doesn't fit into
> release
> > >>>> dates
> > >>>> >> we should better include it into the next release and schedule
> the
> > >>>> next
> > >>>> >> release earlier then postpone the current release.
> > >>>> >>
> > >>>> >> I propose the following dates for 2.9 release:
> > >>>> >>
> > >>>> >> Scope Freeze: June 26, 2020
> > >>>> >> Code Freeze: July 10, 2020
> > >>>> >> Voting Date: July 31, 2020
> > >>>> >> Release Date: August 7, 2019
> > >>>> >>
> > >>>> >> WDYT?
> > >>>> >>
> > >>>> >> [1] :
> > >>>> >>
> > >>>> >>
> > >>>>
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> > >>>> >>
> > >>>> >
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Sincerely yours,
> > >>> Ivan Bessonov
> > >>>
> > >>
> >
>

[Alexey Plekhanov]

Guys,

I've created the 2.9 release confluence page [1].
Also, I found that I don't have permission to Team City release tasks. Can
anyone give me such permissions?

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

пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]>:

> Igniters
>
> Unfortunately, the ML model export/import feature
> <https://issues.apache.org/jira/browse/IGNITE-6642> is under development
> yet.
> I need to delay it before the 2.10 release.
>
>
>
> пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]>:
>
> > Denis,
> >
> > Yes, I still ready to manage it.
> > Today I will prepare a release page on wiki and will try to go over
> tickets
> > list.
> > Also, I have plans to cut the branch by the end of next week if there are
> > no objections.
> >
> >
> > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
> >
> > > Igniters,
> > >
> > > Are we moving forward with this release? Alex Plehanov, are you still
> > ready
> > > to manage it? It seems like everyone agreed with the timeline you
> > proposed
> > > in the very beginning.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]> wrote:
> > >
> > > > Sergey, Ivan,
> > > >
> > > > Could you please check the questions below? If it's time-consuming to
> > > > rework continuous queries, then the new mode can become available in
> > the
> > > > experimental state and should not let register continuous queries to
> > > avoid
> > > > potential deadlocks. Overall, this design gap in continuous queries
> was
> > > > like a bomb that has just detonated [1]. Anyway, this new
> connectivity
> > > mode
> > > > will be priceless even if you can't use continuous queries with them
> > > > because right now we cannot even start a thick client inside of a
> > > > serverless function.
> > > >
> > > > Alexey Plehanov,
> > > >
> > > > It looks like we can proceed with the release taking your timelines.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <[hidden email]>
> wrote:
> > > >
> > > >> Ivan, Sergey,
> > > >>
> > > >> How much effort should we put to resolve the issue with
> > > >> continuous queries? Are you working on that issue actively? Let's
> try
> > to
> > > >> guess what would be the ETA.
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > > >>
> > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
> [hidden email]>
> > > >> wrote:
> > > >>
> > > >>> Hello,
> > > >>>
> > > >>> Sorry for the delay. Sergey Chugunov ([hidden email])
> > just
> > > >>> replied
> > > >>> to the main conversation about "communication via discovery" [1].
> We
> > > >>> work on it
> > > >>> together and recently have found one hard-to-fix scenario, detailed
> > > >>> description is
> > > >>> provided in Sergey's reply.
> > > >>>
> > > >>> In short, July 10th looks realistic only if we introduce new
> behavior
> > > in
> > > >>> its current
> > > >>> implementation, with new setting and IgniteExperimental status.
> > Blocker
> > > >>> here is
> > > >>> current implementation of Continuos Query protocol that in some
> cases
> > > >>> (described
> > > >>> at the end) initiates TCP connection right from discovery thread
> > which
> > > >>> obviously
> > > >>> leads to deadlock. We haven't estimated efforts needed to redesign
> of
> > > CQ
> > > >>> protocol
> > > >>> but it is definitely a risk and fixing it isn't feasible with a
> code
> > > >>> freeze at 10th of July.
> > > >>> So my verdict: we can include this new feature in 2.9 scope as
> > > >>> experimental and with
> > > >>> highlighted limitation on CQ usage. Is that OK?
> > > >>>
> > > >>> CQ limitation: server needs to open a communication connection to
> the
> > > >>> client if during
> > > >>> CQ registration client tries to p2p deploy new class not available
> on
> > > >>> server classpath.
> > > >>> In other cases registration of CQ should be fine.
> > > >>>
> > > >>> [1]
> > > >>>
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > >>>
> > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <[hidden email]>:
> > > >>>
> > > >>>> Hi,
> > > >>>>
> > > >>>> Indeed, the tracing feature is almost ready. Discovery,
> > communication
> > > >>>> and
> > > >>>> transactions tracing will be introduced, as well as an option to
> > > >>>> configure
> > > >>>> tracing in runtime. Right now we are working on final performance
> > > >>>> optimizations, but it's very likely that we'll complete this
> > activity
> > > >>>> before the code freeze date.
> > > >>>> Let's include tracing to the 2.9 release scope.
> > > >>>>
> > > >>>> More info:
> > > >>>>
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> > > >>>>
> > > >>>> --
> > > >>>> Best Regards,
> > > >>>> Ivan Rakov
> > > >>>>
> > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <[hidden email]>
> > wrote:
> > > >>>>
> > > >>>> > Hi folks,
> > > >>>> >
> > > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable to
> me.
> > > I'd
> > > >>>> like
> > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]>, who
> is
> > > >>>> about to
> > > >>>> > finish with the tracing support, and @Ivan Bessonov
> > > >>>> > <[hidden email]>, who is fixing a serious limitation
> for
> > K8
> > > >>>> > deployments [1]. Most likely, both features will be ready by the
> > > code
> > > >>>> > freeze date (July 10), but the guys should know it better.
> > > >>>> >
> > > >>>> > [1]
> > > >>>> >
> > > >>>>
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > >>>> >
> > > >>>> > -
> > > >>>> > Denis
> > > >>>> >
> > > >>>> >
> > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> > > [hidden email]
> > > >>>> >
> > > >>>> > wrote:
> > > >>>> >
> > > >>>> >> Hello Igniters,
> > > >>>> >>
> > > >>>> >> AI 2.8.1 is finally released and as we discussed here [1] its
> > time
> > > to
> > > >>>> >> start
> > > >>>> >> the discussion about 2.9 release.
> > > >>>> >>
> > > >>>> >> I want to propose myself to be the release manager of the 2.9
> > > >>>> release.
> > > >>>> >>
> > > >>>> >> What about release time, I agree with Maxim that we should
> > deliver
> > > >>>> >> features
> > > >>>> >> as frequently as possible. If some feature doesn't fit into
> > release
> > > >>>> dates
> > > >>>> >> we should better include it into the next release and schedule
> > the
> > > >>>> next
> > > >>>> >> release earlier then postpone the current release.
> > > >>>> >>
> > > >>>> >> I propose the following dates for 2.9 release:
> > > >>>> >>
> > > >>>> >> Scope Freeze: June 26, 2020
> > > >>>> >> Code Freeze: July 10, 2020
> > > >>>> >> Voting Date: July 31, 2020
> > > >>>> >> Release Date: August 7, 2019
> > > >>>> >>
> > > >>>> >> WDYT?
> > > >>>> >>
> > > >>>> >> [1] :
> > > >>>> >>
> > > >>>> >>
> > > >>>>
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> > > >>>> >>
> > > >>>> >
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Sincerely yours,
> > > >>> Ivan Bessonov
> > > >>>
> > > >>
> > >
> >
>

[Anton Vinogradov-2]

You're now at the "Ignite Release Managers" group.
Please check you gain access.

On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <[hidden email]>
wrote:

> Guys,
>
> I've created the 2.9 release confluence page [1].
> Also, I found that I don't have permission to Team City release tasks. Can
> anyone give me such permissions?
>
> [1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>
> пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]>:
>
> > Igniters
> >
> > Unfortunately, the ML model export/import feature
> > <https://issues.apache.org/jira/browse/IGNITE-6642> is under development
> > yet.
> > I need to delay it before the 2.10 release.
> >
> >
> >
> > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]>:
> >
> > > Denis,
> > >
> > > Yes, I still ready to manage it.
> > > Today I will prepare a release page on wiki and will try to go over
> > tickets
> > > list.
> > > Also, I have plans to cut the branch by the end of next week if there
> are
> > > no objections.
> > >
> > >
> > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
> > >
> > > > Igniters,
> > > >
> > > > Are we moving forward with this release? Alex Plehanov, are you still
> > > ready
> > > > to manage it? It seems like everyone agreed with the timeline you
> > > proposed
> > > > in the very beginning.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]>
> wrote:
> > > >
> > > > > Sergey, Ivan,
> > > > >
> > > > > Could you please check the questions below? If it's time-consuming
> to
> > > > > rework continuous queries, then the new mode can become available
> in
> > > the
> > > > > experimental state and should not let register continuous queries
> to
> > > > avoid
> > > > > potential deadlocks. Overall, this design gap in continuous queries
> > was
> > > > > like a bomb that has just detonated [1]. Anyway, this new
> > connectivity
> > > > mode
> > > > > will be priceless even if you can't use continuous queries with
> them
> > > > > because right now we cannot even start a thick client inside of a
> > > > > serverless function.
> > > > >
> > > > > Alexey Plehanov,
> > > > >
> > > > > It looks like we can proceed with the release taking your
> timelines.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <[hidden email]>
> > wrote:
> > > > >
> > > > >> Ivan, Sergey,
> > > > >>
> > > > >> How much effort should we put to resolve the issue with
> > > > >> continuous queries? Are you working on that issue actively? Let's
> > try
> > > to
> > > > >> guess what would be the ETA.
> > > > >>
> > > > >> -
> > > > >> Denis
> > > > >>
> > > > >>
> > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
> > [hidden email]>
> > > > >> wrote:
> > > > >>
> > > > >>> Hello,
> > > > >>>
> > > > >>> Sorry for the delay. Sergey Chugunov ([hidden email])
> > > just
> > > > >>> replied
> > > > >>> to the main conversation about "communication via discovery" [1].
> > We
> > > > >>> work on it
> > > > >>> together and recently have found one hard-to-fix scenario,
> detailed
> > > > >>> description is
> > > > >>> provided in Sergey's reply.
> > > > >>>
> > > > >>> In short, July 10th looks realistic only if we introduce new
> > behavior
> > > > in
> > > > >>> its current
> > > > >>> implementation, with new setting and IgniteExperimental status.
> > > Blocker
> > > > >>> here is
> > > > >>> current implementation of Continuos Query protocol that in some
> > cases
> > > > >>> (described
> > > > >>> at the end) initiates TCP connection right from discovery thread
> > > which
> > > > >>> obviously
> > > > >>> leads to deadlock. We haven't estimated efforts needed to
> redesign
> > of
> > > > CQ
> > > > >>> protocol
> > > > >>> but it is definitely a risk and fixing it isn't feasible with a
> > code
> > > > >>> freeze at 10th of July.
> > > > >>> So my verdict: we can include this new feature in 2.9 scope as
> > > > >>> experimental and with
> > > > >>> highlighted limitation on CQ usage. Is that OK?
> > > > >>>
> > > > >>> CQ limitation: server needs to open a communication connection to
> > the
> > > > >>> client if during
> > > > >>> CQ registration client tries to p2p deploy new class not
> available
> > on
> > > > >>> server classpath.
> > > > >>> In other cases registration of CQ should be fine.
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > > >>>
> > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <[hidden email]>:
> > > > >>>
> > > > >>>> Hi,
> > > > >>>>
> > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
> > > communication
> > > > >>>> and
> > > > >>>> transactions tracing will be introduced, as well as an option to
> > > > >>>> configure
> > > > >>>> tracing in runtime. Right now we are working on final
> performance
> > > > >>>> optimizations, but it's very likely that we'll complete this
> > > activity
> > > > >>>> before the code freeze date.
> > > > >>>> Let's include tracing to the 2.9 release scope.
> > > > >>>>
> > > > >>>> More info:
> > > > >>>>
> > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> > > > >>>>
> > > > >>>> --
> > > > >>>> Best Regards,
> > > > >>>> Ivan Rakov
> > > > >>>>
> > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <[hidden email]>
> > > wrote:
> > > > >>>>
> > > > >>>> > Hi folks,
> > > > >>>> >
> > > > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable to
> > me.
> > > > I'd
> > > > >>>> like
> > > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]>, who
> > is
> > > > >>>> about to
> > > > >>>> > finish with the tracing support, and @Ivan Bessonov
> > > > >>>> > <[hidden email]>, who is fixing a serious limitation
> > for
> > > K8
> > > > >>>> > deployments [1]. Most likely, both features will be ready by
> the
> > > > code
> > > > >>>> > freeze date (July 10), but the guys should know it better.
> > > > >>>> >
> > > > >>>> > [1]
> > > > >>>> >
> > > > >>>>
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > > >>>> >
> > > > >>>> > -
> > > > >>>> > Denis
> > > > >>>> >
> > > > >>>> >
> > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> > > > [hidden email]
> > > > >>>> >
> > > > >>>> > wrote:
> > > > >>>> >
> > > > >>>> >> Hello Igniters,
> > > > >>>> >>
> > > > >>>> >> AI 2.8.1 is finally released and as we discussed here [1] its
> > > time
> > > > to
> > > > >>>> >> start
> > > > >>>> >> the discussion about 2.9 release.
> > > > >>>> >>
> > > > >>>> >> I want to propose myself to be the release manager of the 2.9
> > > > >>>> release.
> > > > >>>> >>
> > > > >>>> >> What about release time, I agree with Maxim that we should
> > > deliver
> > > > >>>> >> features
> > > > >>>> >> as frequently as possible. If some feature doesn't fit into
> > > release
> > > > >>>> dates
> > > > >>>> >> we should better include it into the next release and
> schedule
> > > the
> > > > >>>> next
> > > > >>>> >> release earlier then postpone the current release.
> > > > >>>> >>
> > > > >>>> >> I propose the following dates for 2.9 release:
> > > > >>>> >>
> > > > >>>> >> Scope Freeze: June 26, 2020
> > > > >>>> >> Code Freeze: July 10, 2020
> > > > >>>> >> Voting Date: July 31, 2020
> > > > >>>> >> Release Date: August 7, 2019
> > > > >>>> >>
> > > > >>>> >> WDYT?
> > > > >>>> >>
> > > > >>>> >> [1] :
> > > > >>>> >>
> > > > >>>> >>
> > > > >>>>
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> > > > >>>> >>
> > > > >>>> >
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> --
> > > > >>> Sincerely yours,
> > > > >>> Ivan Bessonov
> > > > >>>
> > > > >>
> > > >
> > >
> >
>

[Alexey Plekhanov]

Anton, thank you.

Guys,

I've cut the release branch. From now on please pin resolved in the master
branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
tickets to ignite-2.9 branch.

As far as the release branch cut was delayed, I propose to move code freeze
dates by one week (to 17 July 2020). WDYT?

I've moved long-time inactive non-blocker tickets (except documentation
related, we will deal with them later) from 2.9 release, please check your
Jira issues to have the correct "Fix version" field if your ticket is
planned to 2.9 release.

All currently pinned to 2.9 issues can be found on the release page [1].

I didn't get about [2] ticket mentioned in this thread, are we going to
include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please clarify?

[1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
[2]: https://issues.apache.org/jira/browse/IGNITE-13156

пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:

> You're now at the "Ignite Release Managers" group.
> Please check you gain access.
>
> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <[hidden email]>
> wrote:
>
> > Guys,
> >
> > I've created the 2.9 release confluence page [1].
> > Also, I found that I don't have permission to Team City release tasks.
> Can
> > anyone give me such permissions?
> >
> > [1]:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >
> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]>:
> >
> > > Igniters
> > >
> > > Unfortunately, the ML model export/import feature
> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
> development
> > > yet.
> > > I need to delay it before the 2.10 release.
> > >
> > >
> > >
> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]>:
> > >
> > > > Denis,
> > > >
> > > > Yes, I still ready to manage it.
> > > > Today I will prepare a release page on wiki and will try to go over
> > > tickets
> > > > list.
> > > > Also, I have plans to cut the branch by the end of next week if there
> > are
> > > > no objections.
> > > >
> > > >
> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Are we moving forward with this release? Alex Plehanov, are you
> still
> > > > ready
> > > > > to manage it? It seems like everyone agreed with the timeline you
> > > > proposed
> > > > > in the very beginning.
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]>
> > wrote:
> > > > >
> > > > > > Sergey, Ivan,
> > > > > >
> > > > > > Could you please check the questions below? If it's
> time-consuming
> > to
> > > > > > rework continuous queries, then the new mode can become available
> > in
> > > > the
> > > > > > experimental state and should not let register continuous queries
> > to
> > > > > avoid
> > > > > > potential deadlocks. Overall, this design gap in continuous
> queries
> > > was
> > > > > > like a bomb that has just detonated [1]. Anyway, this new
> > > connectivity
> > > > > mode
> > > > > > will be priceless even if you can't use continuous queries with
> > them
> > > > > > because right now we cannot even start a thick client inside of a
> > > > > > serverless function.
> > > > > >
> > > > > > Alexey Plehanov,
> > > > > >
> > > > > > It looks like we can proceed with the release taking your
> > timelines.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> > > > > >
> > > > > > -
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <[hidden email]>
> > > wrote:
> > > > > >
> > > > > >> Ivan, Sergey,
> > > > > >>
> > > > > >> How much effort should we put to resolve the issue with
> > > > > >> continuous queries? Are you working on that issue actively?
> Let's
> > > try
> > > > to
> > > > > >> guess what would be the ETA.
> > > > > >>
> > > > > >> -
> > > > > >> Denis
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
> > > [hidden email]>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Hello,
> > > > > >>>
> > > > > >>> Sorry for the delay. Sergey Chugunov (
> [hidden email])
> > > > just
> > > > > >>> replied
> > > > > >>> to the main conversation about "communication via discovery"
> [1].
> > > We
> > > > > >>> work on it
> > > > > >>> together and recently have found one hard-to-fix scenario,
> > detailed
> > > > > >>> description is
> > > > > >>> provided in Sergey's reply.
> > > > > >>>
> > > > > >>> In short, July 10th looks realistic only if we introduce new
> > > behavior
> > > > > in
> > > > > >>> its current
> > > > > >>> implementation, with new setting and IgniteExperimental status.
> > > > Blocker
> > > > > >>> here is
> > > > > >>> current implementation of Continuos Query protocol that in some
> > > cases
> > > > > >>> (described
> > > > > >>> at the end) initiates TCP connection right from discovery
> thread
> > > > which
> > > > > >>> obviously
> > > > > >>> leads to deadlock. We haven't estimated efforts needed to
> > redesign
> > > of
> > > > > CQ
> > > > > >>> protocol
> > > > > >>> but it is definitely a risk and fixing it isn't feasible with a
> > > code
> > > > > >>> freeze at 10th of July.
> > > > > >>> So my verdict: we can include this new feature in 2.9 scope as
> > > > > >>> experimental and with
> > > > > >>> highlighted limitation on CQ usage. Is that OK?
> > > > > >>>
> > > > > >>> CQ limitation: server needs to open a communication connection
> to
> > > the
> > > > > >>> client if during
> > > > > >>> CQ registration client tries to p2p deploy new class not
> > available
> > > on
> > > > > >>> server classpath.
> > > > > >>> In other cases registration of CQ should be fine.
> > > > > >>>
> > > > > >>> [1]
> > > > > >>>
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > > > >>>
> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <[hidden email]
> >:
> > > > > >>>
> > > > > >>>> Hi,
> > > > > >>>>
> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
> > > > communication
> > > > > >>>> and
> > > > > >>>> transactions tracing will be introduced, as well as an option
> to
> > > > > >>>> configure
> > > > > >>>> tracing in runtime. Right now we are working on final
> > performance
> > > > > >>>> optimizations, but it's very likely that we'll complete this
> > > > activity
> > > > > >>>> before the code freeze date.
> > > > > >>>> Let's include tracing to the 2.9 release scope.
> > > > > >>>>
> > > > > >>>> More info:
> > > > > >>>>
> > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> > > > > >>>>
> > > > > >>>> --
> > > > > >>>> Best Regards,
> > > > > >>>> Ivan Rakov
> > > > > >>>>
> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <[hidden email]
> >
> > > > wrote:
> > > > > >>>>
> > > > > >>>> > Hi folks,
> > > > > >>>> >
> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable
> to
> > > me.
> > > > > I'd
> > > > > >>>> like
> > > > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]>,
> who
> > > is
> > > > > >>>> about to
> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
> > > > > >>>> > <[hidden email]>, who is fixing a serious
> limitation
> > > for
> > > > K8
> > > > > >>>> > deployments [1]. Most likely, both features will be ready by
> > the
> > > > > code
> > > > > >>>> > freeze date (July 10), but the guys should know it better.
> > > > > >>>> >
> > > > > >>>> > [1]
> > > > > >>>> >
> > > > > >>>>
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> > > > > >>>> >
> > > > > >>>> > -
> > > > > >>>> > Denis
> > > > > >>>> >
> > > > > >>>> >
> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> > > > > [hidden email]
> > > > > >>>> >
> > > > > >>>> > wrote:
> > > > > >>>> >
> > > > > >>>> >> Hello Igniters,
> > > > > >>>> >>
> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed here [1]
> its
> > > > time
> > > > > to
> > > > > >>>> >> start
> > > > > >>>> >> the discussion about 2.9 release.
> > > > > >>>> >>
> > > > > >>>> >> I want to propose myself to be the release manager of the
> 2.9
> > > > > >>>> release.
> > > > > >>>> >>
> > > > > >>>> >> What about release time, I agree with Maxim that we should
> > > > deliver
> > > > > >>>> >> features
> > > > > >>>> >> as frequently as possible. If some feature doesn't fit into
> > > > release
> > > > > >>>> dates
> > > > > >>>> >> we should better include it into the next release and
> > schedule
> > > > the
> > > > > >>>> next
> > > > > >>>> >> release earlier then postpone the current release.
> > > > > >>>> >>
> > > > > >>>> >> I propose the following dates for 2.9 release:
> > > > > >>>> >>
> > > > > >>>> >> Scope Freeze: June 26, 2020
> > > > > >>>> >> Code Freeze: July 10, 2020
> > > > > >>>> >> Voting Date: July 31, 2020
> > > > > >>>> >> Release Date: August 7, 2019
> > > > > >>>> >>
> > > > > >>>> >> WDYT?
> > > > > >>>> >>
> > > > > >>>> >> [1] :
> > > > > >>>> >>
> > > > > >>>> >>
> > > > > >>>>
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> > > > > >>>> >>
> > > > > >>>> >
> > > > > >>>>
> > > > > >>>
> > > > > >>>
> > > > > >>> --
> > > > > >>> Sincerely yours,
> > > > > >>> Ivan Bessonov
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
>

[Alexey Plekhanov]

Guys,

Can somebody help with creating scheduled build triggers for nightly "Run
All" on TC for "ignite-2.9" branch?

Also, I found that we still have a nightly "Run All" for "ignite-2.8"
branch [1]. Do we still need it? Or just forgot to remove it after release?

[1] :
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv

пт, 3 июл. 2020 г. в 23:18, Alex Plehanov <[hidden email]>:

> Anton, thank you.
>
> Guys,
>
> I've cut the release branch. From now on please pin resolved in the master
> branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
> tickets to ignite-2.9 branch.
>
> As far as the release branch cut was delayed, I propose to move code
> freeze dates by one week (to 17 July 2020). WDYT?
>
> I've moved long-time inactive non-blocker tickets (except documentation
> related, we will deal with them later) from 2.9 release, please check your
> Jira issues to have the correct "Fix version" field if your ticket is
> planned to 2.9 release.
>
> All currently pinned to 2.9 issues can be found on the release page [1].
>
> I didn't get about [2] ticket mentioned in this thread, are we going to
> include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please clarify?
>
> [1]: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> [2]: https://issues.apache.org/jira/browse/IGNITE-13156
>
> пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:
>
>> You're now at the "Ignite Release Managers" group.
>> Please check you gain access.
>>
>> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <[hidden email]>
>> wrote:
>>
>> > Guys,
>> >
>> > I've created the 2.9 release confluence page [1].
>> > Also, I found that I don't have permission to Team City release tasks.
>> Can
>> > anyone give me such permissions?
>> >
>> > [1]:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>> >
>> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]>:
>> >
>> > > Igniters
>> > >
>> > > Unfortunately, the ML model export/import feature
>> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
>> development
>> > > yet.
>> > > I need to delay it before the 2.10 release.
>> > >
>> > >
>> > >
>> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]>:
>> > >
>> > > > Denis,
>> > > >
>> > > > Yes, I still ready to manage it.
>> > > > Today I will prepare a release page on wiki and will try to go over
>> > > tickets
>> > > > list.
>> > > > Also, I have plans to cut the branch by the end of next week if
>> there
>> > are
>> > > > no objections.
>> > > >
>> > > >
>> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
>> > > >
>> > > > > Igniters,
>> > > > >
>> > > > > Are we moving forward with this release? Alex Plehanov, are you
>> still
>> > > > ready
>> > > > > to manage it? It seems like everyone agreed with the timeline you
>> > > > proposed
>> > > > > in the very beginning.
>> > > > >
>> > > > > -
>> > > > > Denis
>> > > > >
>> > > > >
>> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]>
>> > wrote:
>> > > > >
>> > > > > > Sergey, Ivan,
>> > > > > >
>> > > > > > Could you please check the questions below? If it's
>> time-consuming
>> > to
>> > > > > > rework continuous queries, then the new mode can become
>> available
>> > in
>> > > > the
>> > > > > > experimental state and should not let register continuous
>> queries
>> > to
>> > > > > avoid
>> > > > > > potential deadlocks. Overall, this design gap in continuous
>> queries
>> > > was
>> > > > > > like a bomb that has just detonated [1]. Anyway, this new
>> > > connectivity
>> > > > > mode
>> > > > > > will be priceless even if you can't use continuous queries with
>> > them
>> > > > > > because right now we cannot even start a thick client inside of
>> a
>> > > > > > serverless function.
>> > > > > >
>> > > > > > Alexey Plehanov,
>> > > > > >
>> > > > > > It looks like we can proceed with the release taking your
>> > timelines.
>> > > > > >
>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
>> > > > > >
>> > > > > > -
>> > > > > > Denis
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <[hidden email]>
>> > > wrote:
>> > > > > >
>> > > > > >> Ivan, Sergey,
>> > > > > >>
>> > > > > >> How much effort should we put to resolve the issue with
>> > > > > >> continuous queries? Are you working on that issue actively?
>> Let's
>> > > try
>> > > > to
>> > > > > >> guess what would be the ETA.
>> > > > > >>
>> > > > > >> -
>> > > > > >> Denis
>> > > > > >>
>> > > > > >>
>> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
>> > > [hidden email]>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >>> Hello,
>> > > > > >>>
>> > > > > >>> Sorry for the delay. Sergey Chugunov (
>> [hidden email])
>> > > > just
>> > > > > >>> replied
>> > > > > >>> to the main conversation about "communication via discovery"
>> [1].
>> > > We
>> > > > > >>> work on it
>> > > > > >>> together and recently have found one hard-to-fix scenario,
>> > detailed
>> > > > > >>> description is
>> > > > > >>> provided in Sergey's reply.
>> > > > > >>>
>> > > > > >>> In short, July 10th looks realistic only if we introduce new
>> > > behavior
>> > > > > in
>> > > > > >>> its current
>> > > > > >>> implementation, with new setting and IgniteExperimental
>> status.
>> > > > Blocker
>> > > > > >>> here is
>> > > > > >>> current implementation of Continuos Query protocol that in
>> some
>> > > cases
>> > > > > >>> (described
>> > > > > >>> at the end) initiates TCP connection right from discovery
>> thread
>> > > > which
>> > > > > >>> obviously
>> > > > > >>> leads to deadlock. We haven't estimated efforts needed to
>> > redesign
>> > > of
>> > > > > CQ
>> > > > > >>> protocol
>> > > > > >>> but it is definitely a risk and fixing it isn't feasible with
>> a
>> > > code
>> > > > > >>> freeze at 10th of July.
>> > > > > >>> So my verdict: we can include this new feature in 2.9 scope as
>> > > > > >>> experimental and with
>> > > > > >>> highlighted limitation on CQ usage. Is that OK?
>> > > > > >>>
>> > > > > >>> CQ limitation: server needs to open a communication
>> connection to
>> > > the
>> > > > > >>> client if during
>> > > > > >>> CQ registration client tries to p2p deploy new class not
>> > available
>> > > on
>> > > > > >>> server classpath.
>> > > > > >>> In other cases registration of CQ should be fine.
>> > > > > >>>
>> > > > > >>> [1]
>> > > > > >>>
>> > > > >
>> > > >
>> > >
>> >
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>> > > > > >>>
>> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <[hidden email]
>> >:
>> > > > > >>>
>> > > > > >>>> Hi,
>> > > > > >>>>
>> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
>> > > > communication
>> > > > > >>>> and
>> > > > > >>>> transactions tracing will be introduced, as well as an
>> option to
>> > > > > >>>> configure
>> > > > > >>>> tracing in runtime. Right now we are working on final
>> > performance
>> > > > > >>>> optimizations, but it's very likely that we'll complete this
>> > > > activity
>> > > > > >>>> before the code freeze date.
>> > > > > >>>> Let's include tracing to the 2.9 release scope.
>> > > > > >>>>
>> > > > > >>>> More info:
>> > > > > >>>>
>> > > >
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
>> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
>> > > > > >>>>
>> > > > > >>>> --
>> > > > > >>>> Best Regards,
>> > > > > >>>> Ivan Rakov
>> > > > > >>>>
>> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <
>> [hidden email]>
>> > > > wrote:
>> > > > > >>>>
>> > > > > >>>> > Hi folks,
>> > > > > >>>> >
>> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable
>> to
>> > > me.
>> > > > > I'd
>> > > > > >>>> like
>> > > > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]>,
>> who
>> > > is
>> > > > > >>>> about to
>> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
>> > > > > >>>> > <[hidden email]>, who is fixing a serious
>> limitation
>> > > for
>> > > > K8
>> > > > > >>>> > deployments [1]. Most likely, both features will be ready
>> by
>> > the
>> > > > > code
>> > > > > >>>> > freeze date (July 10), but the guys should know it better.
>> > > > > >>>> >
>> > > > > >>>> > [1]
>> > > > > >>>> >
>> > > > > >>>>
>> > > > >
>> > > >
>> > >
>> >
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>> > > > > >>>> >
>> > > > > >>>> > -
>> > > > > >>>> > Denis
>> > > > > >>>> >
>> > > > > >>>> >
>> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
>> > > > > [hidden email]
>> > > > > >>>> >
>> > > > > >>>> > wrote:
>> > > > > >>>> >
>> > > > > >>>> >> Hello Igniters,
>> > > > > >>>> >>
>> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed here [1]
>> its
>> > > > time
>> > > > > to
>> > > > > >>>> >> start
>> > > > > >>>> >> the discussion about 2.9 release.
>> > > > > >>>> >>
>> > > > > >>>> >> I want to propose myself to be the release manager of the
>> 2.9
>> > > > > >>>> release.
>> > > > > >>>> >>
>> > > > > >>>> >> What about release time, I agree with Maxim that we should
>> > > > deliver
>> > > > > >>>> >> features
>> > > > > >>>> >> as frequently as possible. If some feature doesn't fit
>> into
>> > > > release
>> > > > > >>>> dates
>> > > > > >>>> >> we should better include it into the next release and
>> > schedule
>> > > > the
>> > > > > >>>> next
>> > > > > >>>> >> release earlier then postpone the current release.
>> > > > > >>>> >>
>> > > > > >>>> >> I propose the following dates for 2.9 release:
>> > > > > >>>> >>
>> > > > > >>>> >> Scope Freeze: June 26, 2020
>> > > > > >>>> >> Code Freeze: July 10, 2020
>> > > > > >>>> >> Voting Date: July 31, 2020
>> > > > > >>>> >> Release Date: August 7, 2019
>> > > > > >>>> >>
>> > > > > >>>> >> WDYT?
>> > > > > >>>> >>
>> > > > > >>>> >> [1] :
>> > > > > >>>> >>
>> > > > > >>>> >>
>> > > > > >>>>
>> > > > >
>> > > >
>> > >
>> >
>> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
>> > > > > >>>> >>
>> > > > > >>>> >
>> > > > > >>>>
>> > > > > >>>
>> > > > > >>>
>> > > > > >>> --
>> > > > > >>> Sincerely yours,
>> > > > > >>> Ivan Bessonov
>> > > > > >>>
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> >
>>
>

[Ilya Kasnacheev]

Hello!

I have changed the schedule condition so ignite-2.9 will be run instead.
Please check if it works tomorrow.

Regards,
--
Ilya Kasnacheev


вт, 7 июл. 2020 г. в 16:42, Alex Plehanov <[hidden email]>:

> Guys,
>
> Can somebody help with creating scheduled build triggers for nightly "Run
> All" on TC for "ignite-2.9" branch?
>
> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
> branch [1]. Do we still need it? Or just forgot to remove it after release?
>
> [1] :
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
>
> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov <[hidden email]>:
>
> > Anton, thank you.
> >
> > Guys,
> >
> > I've cut the release branch. From now on please pin resolved in the
> master
> > branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
> > tickets to ignite-2.9 branch.
> >
> > As far as the release branch cut was delayed, I propose to move code
> > freeze dates by one week (to 17 July 2020). WDYT?
> >
> > I've moved long-time inactive non-blocker tickets (except documentation
> > related, we will deal with them later) from 2.9 release, please check
> your
> > Jira issues to have the correct "Fix version" field if your ticket is
> > planned to 2.9 release.
> >
> > All currently pinned to 2.9 issues can be found on the release page [1].
> >
> > I didn't get about [2] ticket mentioned in this thread, are we going to
> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
> clarify?
> >
> > [1]:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
> >
> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:
> >
> >> You're now at the "Ignite Release Managers" group.
> >> Please check you gain access.
> >>
> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <[hidden email]>
> >> wrote:
> >>
> >> > Guys,
> >> >
> >> > I've created the 2.9 release confluence page [1].
> >> > Also, I found that I don't have permission to Team City release tasks.
> >> Can
> >> > anyone give me such permissions?
> >> >
> >> > [1]:
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >> >
> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]
> >:
> >> >
> >> > > Igniters
> >> > >
> >> > > Unfortunately, the ML model export/import feature
> >> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
> >> development
> >> > > yet.
> >> > > I need to delay it before the 2.10 release.
> >> > >
> >> > >
> >> > >
> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <[hidden email]
> >:
> >> > >
> >> > > > Denis,
> >> > > >
> >> > > > Yes, I still ready to manage it.
> >> > > > Today I will prepare a release page on wiki and will try to go
> over
> >> > > tickets
> >> > > > list.
> >> > > > Also, I have plans to cut the branch by the end of next week if
> >> there
> >> > are
> >> > > > no objections.
> >> > > >
> >> > > >
> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
> >> > > >
> >> > > > > Igniters,
> >> > > > >
> >> > > > > Are we moving forward with this release? Alex Plehanov, are you
> >> still
> >> > > > ready
> >> > > > > to manage it? It seems like everyone agreed with the timeline
> you
> >> > > > proposed
> >> > > > > in the very beginning.
> >> > > > >
> >> > > > > -
> >> > > > > Denis
> >> > > > >
> >> > > > >
> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]>
> >> > wrote:
> >> > > > >
> >> > > > > > Sergey, Ivan,
> >> > > > > >
> >> > > > > > Could you please check the questions below? If it's
> >> time-consuming
> >> > to
> >> > > > > > rework continuous queries, then the new mode can become
> >> available
> >> > in
> >> > > > the
> >> > > > > > experimental state and should not let register continuous
> >> queries
> >> > to
> >> > > > > avoid
> >> > > > > > potential deadlocks. Overall, this design gap in continuous
> >> queries
> >> > > was
> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
> >> > > connectivity
> >> > > > > mode
> >> > > > > > will be priceless even if you can't use continuous queries
> with
> >> > them
> >> > > > > > because right now we cannot even start a thick client inside
> of
> >> a
> >> > > > > > serverless function.
> >> > > > > >
> >> > > > > > Alexey Plehanov,
> >> > > > > >
> >> > > > > > It looks like we can proceed with the release taking your
> >> > timelines.
> >> > > > > >
> >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> >> > > > > >
> >> > > > > > -
> >> > > > > > Denis
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <
> [hidden email]>
> >> > > wrote:
> >> > > > > >
> >> > > > > >> Ivan, Sergey,
> >> > > > > >>
> >> > > > > >> How much effort should we put to resolve the issue with
> >> > > > > >> continuous queries? Are you working on that issue actively?
> >> Let's
> >> > > try
> >> > > > to
> >> > > > > >> guess what would be the ETA.
> >> > > > > >>
> >> > > > > >> -
> >> > > > > >> Denis
> >> > > > > >>
> >> > > > > >>
> >> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
> >> > > [hidden email]>
> >> > > > > >> wrote:
> >> > > > > >>
> >> > > > > >>> Hello,
> >> > > > > >>>
> >> > > > > >>> Sorry for the delay. Sergey Chugunov (
> >> [hidden email])
> >> > > > just
> >> > > > > >>> replied
> >> > > > > >>> to the main conversation about "communication via discovery"
> >> [1].
> >> > > We
> >> > > > > >>> work on it
> >> > > > > >>> together and recently have found one hard-to-fix scenario,
> >> > detailed
> >> > > > > >>> description is
> >> > > > > >>> provided in Sergey's reply.
> >> > > > > >>>
> >> > > > > >>> In short, July 10th looks realistic only if we introduce new
> >> > > behavior
> >> > > > > in
> >> > > > > >>> its current
> >> > > > > >>> implementation, with new setting and IgniteExperimental
> >> status.
> >> > > > Blocker
> >> > > > > >>> here is
> >> > > > > >>> current implementation of Continuos Query protocol that in
> >> some
> >> > > cases
> >> > > > > >>> (described
> >> > > > > >>> at the end) initiates TCP connection right from discovery
> >> thread
> >> > > > which
> >> > > > > >>> obviously
> >> > > > > >>> leads to deadlock. We haven't estimated efforts needed to
> >> > redesign
> >> > > of
> >> > > > > CQ
> >> > > > > >>> protocol
> >> > > > > >>> but it is definitely a risk and fixing it isn't feasible
> with
> >> a
> >> > > code
> >> > > > > >>> freeze at 10th of July.
> >> > > > > >>> So my verdict: we can include this new feature in 2.9 scope
> as
> >> > > > > >>> experimental and with
> >> > > > > >>> highlighted limitation on CQ usage. Is that OK?
> >> > > > > >>>
> >> > > > > >>> CQ limitation: server needs to open a communication
> >> connection to
> >> > > the
> >> > > > > >>> client if during
> >> > > > > >>> CQ registration client tries to p2p deploy new class not
> >> > available
> >> > > on
> >> > > > > >>> server classpath.
> >> > > > > >>> In other cases registration of CQ should be fine.
> >> > > > > >>>
> >> > > > > >>> [1]
> >> > > > > >>>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> >> > > > > >>>
> >> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <
> [hidden email]
> >> >:
> >> > > > > >>>
> >> > > > > >>>> Hi,
> >> > > > > >>>>
> >> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
> >> > > > communication
> >> > > > > >>>> and
> >> > > > > >>>> transactions tracing will be introduced, as well as an
> >> option to
> >> > > > > >>>> configure
> >> > > > > >>>> tracing in runtime. Right now we are working on final
> >> > performance
> >> > > > > >>>> optimizations, but it's very likely that we'll complete
> this
> >> > > > activity
> >> > > > > >>>> before the code freeze date.
> >> > > > > >>>> Let's include tracing to the 2.9 release scope.
> >> > > > > >>>>
> >> > > > > >>>> More info:
> >> > > > > >>>>
> >> > > >
> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> >> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> >> > > > > >>>>
> >> > > > > >>>> --
> >> > > > > >>>> Best Regards,
> >> > > > > >>>> Ivan Rakov
> >> > > > > >>>>
> >> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <
> >> [hidden email]>
> >> > > > wrote:
> >> > > > > >>>>
> >> > > > > >>>> > Hi folks,
> >> > > > > >>>> >
> >> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds
> reasonable
> >> to
> >> > > me.
> >> > > > > I'd
> >> > > > > >>>> like
> >> > > > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]
> >,
> >> who
> >> > > is
> >> > > > > >>>> about to
> >> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
> >> > > > > >>>> > <[hidden email]>, who is fixing a serious
> >> limitation
> >> > > for
> >> > > > K8
> >> > > > > >>>> > deployments [1]. Most likely, both features will be ready
> >> by
> >> > the
> >> > > > > code
> >> > > > > >>>> > freeze date (July 10), but the guys should know it
> better.
> >> > > > > >>>> >
> >> > > > > >>>> > [1]
> >> > > > > >>>> >
> >> > > > > >>>>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> >> > > > > >>>> >
> >> > > > > >>>> > -
> >> > > > > >>>> > Denis
> >> > > > > >>>> >
> >> > > > > >>>> >
> >> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> >> > > > > [hidden email]
> >> > > > > >>>> >
> >> > > > > >>>> > wrote:
> >> > > > > >>>> >
> >> > > > > >>>> >> Hello Igniters,
> >> > > > > >>>> >>
> >> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed here
> [1]
> >> its
> >> > > > time
> >> > > > > to
> >> > > > > >>>> >> start
> >> > > > > >>>> >> the discussion about 2.9 release.
> >> > > > > >>>> >>
> >> > > > > >>>> >> I want to propose myself to be the release manager of
> the
> >> 2.9
> >> > > > > >>>> release.
> >> > > > > >>>> >>
> >> > > > > >>>> >> What about release time, I agree with Maxim that we
> should
> >> > > > deliver
> >> > > > > >>>> >> features
> >> > > > > >>>> >> as frequently as possible. If some feature doesn't fit
> >> into
> >> > > > release
> >> > > > > >>>> dates
> >> > > > > >>>> >> we should better include it into the next release and
> >> > schedule
> >> > > > the
> >> > > > > >>>> next
> >> > > > > >>>> >> release earlier then postpone the current release.
> >> > > > > >>>> >>
> >> > > > > >>>> >> I propose the following dates for 2.9 release:
> >> > > > > >>>> >>
> >> > > > > >>>> >> Scope Freeze: June 26, 2020
> >> > > > > >>>> >> Code Freeze: July 10, 2020
> >> > > > > >>>> >> Voting Date: July 31, 2020
> >> > > > > >>>> >> Release Date: August 7, 2019
> >> > > > > >>>> >>
> >> > > > > >>>> >> WDYT?
> >> > > > > >>>> >>
> >> > > > > >>>> >> [1] :
> >> > > > > >>>> >>
> >> > > > > >>>> >>
> >> > > > > >>>>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> >> > > > > >>>> >>
> >> > > > > >>>> >
> >> > > > > >>>>
> >> > > > > >>>
> >> > > > > >>>
> >> > > > > >>> --
> >> > > > > >>> Sincerely yours,
> >> > > > > >>> Ivan Bessonov
> >> > > > > >>>
> >> > > > > >>
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

[Ilya Kasnacheev]

Hello!

I have also set up nightly builds to (hopefully) build 2.9

Regards,
--
Ilya Kasnacheev


вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev <[hidden email]>:

> Hello!
>
> I have changed the schedule condition so ignite-2.9 will be run instead.
> Please check if it works tomorrow.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov <[hidden email]>:
>
>> Guys,
>>
>> Can somebody help with creating scheduled build triggers for nightly "Run
>> All" on TC for "ignite-2.9" branch?
>>
>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
>> branch [1]. Do we still need it? Or just forgot to remove it after
>> release?
>>
>> [1] :
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
>>
>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov <[hidden email]>:
>>
>> > Anton, thank you.
>> >
>> > Guys,
>> >
>> > I've cut the release branch. From now on please pin resolved in the
>> master
>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
>> > tickets to ignite-2.9 branch.
>> >
>> > As far as the release branch cut was delayed, I propose to move code
>> > freeze dates by one week (to 17 July 2020). WDYT?
>> >
>> > I've moved long-time inactive non-blocker tickets (except documentation
>> > related, we will deal with them later) from 2.9 release, please check
>> your
>> > Jira issues to have the correct "Fix version" field if your ticket is
>> > planned to 2.9 release.
>> >
>> > All currently pinned to 2.9 issues can be found on the release page [1].
>> >
>> > I didn't get about [2] ticket mentioned in this thread, are we going to
>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
>> clarify?
>> >
>> > [1]:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
>> >
>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:
>> >
>> >> You're now at the "Ignite Release Managers" group.
>> >> Please check you gain access.
>> >>
>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <[hidden email]
>> >
>> >> wrote:
>> >>
>> >> > Guys,
>> >> >
>> >> > I've created the 2.9 release confluence page [1].
>> >> > Also, I found that I don't have permission to Team City release
>> tasks.
>> >> Can
>> >> > anyone give me such permissions?
>> >> >
>> >> > [1]:
>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>> >> >
>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <[hidden email]
>> >:
>> >> >
>> >> > > Igniters
>> >> > >
>> >> > > Unfortunately, the ML model export/import feature
>> >> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
>> >> development
>> >> > > yet.
>> >> > > I need to delay it before the 2.10 release.
>> >> > >
>> >> > >
>> >> > >
>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
>> [hidden email]>:
>> >> > >
>> >> > > > Denis,
>> >> > > >
>> >> > > > Yes, I still ready to manage it.
>> >> > > > Today I will prepare a release page on wiki and will try to go
>> over
>> >> > > tickets
>> >> > > > list.
>> >> > > > Also, I have plans to cut the branch by the end of next week if
>> >> there
>> >> > are
>> >> > > > no objections.
>> >> > > >
>> >> > > >
>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
>> >> > > >
>> >> > > > > Igniters,
>> >> > > > >
>> >> > > > > Are we moving forward with this release? Alex Plehanov, are you
>> >> still
>> >> > > > ready
>> >> > > > > to manage it? It seems like everyone agreed with the timeline
>> you
>> >> > > > proposed
>> >> > > > > in the very beginning.
>> >> > > > >
>> >> > > > > -
>> >> > > > > Denis
>> >> > > > >
>> >> > > > >
>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <[hidden email]
>> >
>> >> > wrote:
>> >> > > > >
>> >> > > > > > Sergey, Ivan,
>> >> > > > > >
>> >> > > > > > Could you please check the questions below? If it's
>> >> time-consuming
>> >> > to
>> >> > > > > > rework continuous queries, then the new mode can become
>> >> available
>> >> > in
>> >> > > > the
>> >> > > > > > experimental state and should not let register continuous
>> >> queries
>> >> > to
>> >> > > > > avoid
>> >> > > > > > potential deadlocks. Overall, this design gap in continuous
>> >> queries
>> >> > > was
>> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
>> >> > > connectivity
>> >> > > > > mode
>> >> > > > > > will be priceless even if you can't use continuous queries
>> with
>> >> > them
>> >> > > > > > because right now we cannot even start a thick client inside
>> of
>> >> a
>> >> > > > > > serverless function.
>> >> > > > > >
>> >> > > > > > Alexey Plehanov,
>> >> > > > > >
>> >> > > > > > It looks like we can proceed with the release taking your
>> >> > timelines.
>> >> > > > > >
>> >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
>> >> > > > > >
>> >> > > > > > -
>> >> > > > > > Denis
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <
>> [hidden email]>
>> >> > > wrote:
>> >> > > > > >
>> >> > > > > >> Ivan, Sergey,
>> >> > > > > >>
>> >> > > > > >> How much effort should we put to resolve the issue with
>> >> > > > > >> continuous queries? Are you working on that issue actively?
>> >> Let's
>> >> > > try
>> >> > > > to
>> >> > > > > >> guess what would be the ETA.
>> >> > > > > >>
>> >> > > > > >> -
>> >> > > > > >> Denis
>> >> > > > > >>
>> >> > > > > >>
>> >> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
>> >> > > [hidden email]>
>> >> > > > > >> wrote:
>> >> > > > > >>
>> >> > > > > >>> Hello,
>> >> > > > > >>>
>> >> > > > > >>> Sorry for the delay. Sergey Chugunov (
>> >> [hidden email])
>> >> > > > just
>> >> > > > > >>> replied
>> >> > > > > >>> to the main conversation about "communication via
>> discovery"
>> >> [1].
>> >> > > We
>> >> > > > > >>> work on it
>> >> > > > > >>> together and recently have found one hard-to-fix scenario,
>> >> > detailed
>> >> > > > > >>> description is
>> >> > > > > >>> provided in Sergey's reply.
>> >> > > > > >>>
>> >> > > > > >>> In short, July 10th looks realistic only if we introduce
>> new
>> >> > > behavior
>> >> > > > > in
>> >> > > > > >>> its current
>> >> > > > > >>> implementation, with new setting and IgniteExperimental
>> >> status.
>> >> > > > Blocker
>> >> > > > > >>> here is
>> >> > > > > >>> current implementation of Continuos Query protocol that in
>> >> some
>> >> > > cases
>> >> > > > > >>> (described
>> >> > > > > >>> at the end) initiates TCP connection right from discovery
>> >> thread
>> >> > > > which
>> >> > > > > >>> obviously
>> >> > > > > >>> leads to deadlock. We haven't estimated efforts needed to
>> >> > redesign
>> >> > > of
>> >> > > > > CQ
>> >> > > > > >>> protocol
>> >> > > > > >>> but it is definitely a risk and fixing it isn't feasible
>> with
>> >> a
>> >> > > code
>> >> > > > > >>> freeze at 10th of July.
>> >> > > > > >>> So my verdict: we can include this new feature in 2.9
>> scope as
>> >> > > > > >>> experimental and with
>> >> > > > > >>> highlighted limitation on CQ usage. Is that OK?
>> >> > > > > >>>
>> >> > > > > >>> CQ limitation: server needs to open a communication
>> >> connection to
>> >> > > the
>> >> > > > > >>> client if during
>> >> > > > > >>> CQ registration client tries to p2p deploy new class not
>> >> > available
>> >> > > on
>> >> > > > > >>> server classpath.
>> >> > > > > >>> In other cases registration of CQ should be fine.
>> >> > > > > >>>
>> >> > > > > >>> [1]
>> >> > > > > >>>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>> >> > > > > >>>
>> >> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <
>> [hidden email]
>> >> >:
>> >> > > > > >>>
>> >> > > > > >>>> Hi,
>> >> > > > > >>>>
>> >> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
>> >> > > > communication
>> >> > > > > >>>> and
>> >> > > > > >>>> transactions tracing will be introduced, as well as an
>> >> option to
>> >> > > > > >>>> configure
>> >> > > > > >>>> tracing in runtime. Right now we are working on final
>> >> > performance
>> >> > > > > >>>> optimizations, but it's very likely that we'll complete
>> this
>> >> > > > activity
>> >> > > > > >>>> before the code freeze date.
>> >> > > > > >>>> Let's include tracing to the 2.9 release scope.
>> >> > > > > >>>>
>> >> > > > > >>>> More info:
>> >> > > > > >>>>
>> >> > > >
>> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
>> >> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
>> >> > > > > >>>>
>> >> > > > > >>>> --
>> >> > > > > >>>> Best Regards,
>> >> > > > > >>>> Ivan Rakov
>> >> > > > > >>>>
>> >> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <
>> >> [hidden email]>
>> >> > > > wrote:
>> >> > > > > >>>>
>> >> > > > > >>>> > Hi folks,
>> >> > > > > >>>> >
>> >> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds
>> reasonable
>> >> to
>> >> > > me.
>> >> > > > > I'd
>> >> > > > > >>>> like
>> >> > > > > >>>> > only to hear inputs of @Ivan Rakov <[hidden email]
>> >,
>> >> who
>> >> > > is
>> >> > > > > >>>> about to
>> >> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
>> >> > > > > >>>> > <[hidden email]>, who is fixing a serious
>> >> limitation
>> >> > > for
>> >> > > > K8
>> >> > > > > >>>> > deployments [1]. Most likely, both features will be
>> ready
>> >> by
>> >> > the
>> >> > > > > code
>> >> > > > > >>>> > freeze date (July 10), but the guys should know it
>> better.
>> >> > > > > >>>> >
>> >> > > > > >>>> > [1]
>> >> > > > > >>>> >
>> >> > > > > >>>>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>> >> > > > > >>>> >
>> >> > > > > >>>> > -
>> >> > > > > >>>> > Denis
>> >> > > > > >>>> >
>> >> > > > > >>>> >
>> >> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
>> >> > > > > [hidden email]
>> >> > > > > >>>> >
>> >> > > > > >>>> > wrote:
>> >> > > > > >>>> >
>> >> > > > > >>>> >> Hello Igniters,
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed here
>> [1]
>> >> its
>> >> > > > time
>> >> > > > > to
>> >> > > > > >>>> >> start
>> >> > > > > >>>> >> the discussion about 2.9 release.
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> I want to propose myself to be the release manager of
>> the
>> >> 2.9
>> >> > > > > >>>> release.
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> What about release time, I agree with Maxim that we
>> should
>> >> > > > deliver
>> >> > > > > >>>> >> features
>> >> > > > > >>>> >> as frequently as possible. If some feature doesn't fit
>> >> into
>> >> > > > release
>> >> > > > > >>>> dates
>> >> > > > > >>>> >> we should better include it into the next release and
>> >> > schedule
>> >> > > > the
>> >> > > > > >>>> next
>> >> > > > > >>>> >> release earlier then postpone the current release.
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> I propose the following dates for 2.9 release:
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> Scope Freeze: June 26, 2020
>> >> > > > > >>>> >> Code Freeze: July 10, 2020
>> >> > > > > >>>> >> Voting Date: July 31, 2020
>> >> > > > > >>>> >> Release Date: August 7, 2019
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> WDYT?
>> >> > > > > >>>> >>
>> >> > > > > >>>> >> [1] :
>> >> > > > > >>>> >>
>> >> > > > > >>>> >>
>> >> > > > > >>>>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
>> >> > > > > >>>> >>
>> >> > > > > >>>> >
>> >> > > > > >>>>
>> >> > > > > >>>
>> >> > > > > >>>
>> >> > > > > >>> --
>> >> > > > > >>> Sincerely yours,
>> >> > > > > >>> Ivan Bessonov
>> >> > > > > >>>
>> >> > > > > >>
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
>>
>

[Ilya Kasnacheev]

Hello!

It seems that it works and we now have 2.9 nightlies.

Guys, can you please bump the master POM version to 2.10.0-SNAPSHOT?

Regards,
--
Ilya Kasnacheev


пт, 10 июл. 2020 г. в 17:43, Ilya Kasnacheev <[hidden email]>:

> Hello!
>
> I have also set up nightly builds to (hopefully) build 2.9
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev <[hidden email]>:
>
>> Hello!
>>
>> I have changed the schedule condition so ignite-2.9 will be run instead.
>> Please check if it works tomorrow.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov <[hidden email]>:
>>
>>> Guys,
>>>
>>> Can somebody help with creating scheduled build triggers for nightly "Run
>>> All" on TC for "ignite-2.9" branch?
>>>
>>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
>>> branch [1]. Do we still need it? Or just forgot to remove it after
>>> release?
>>>
>>> [1] :
>>>
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
>>>
>>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov <[hidden email]>:
>>>
>>> > Anton, thank you.
>>> >
>>> > Guys,
>>> >
>>> > I've cut the release branch. From now on please pin resolved in the
>>> master
>>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
>>> > tickets to ignite-2.9 branch.
>>> >
>>> > As far as the release branch cut was delayed, I propose to move code
>>> > freeze dates by one week (to 17 July 2020). WDYT?
>>> >
>>> > I've moved long-time inactive non-blocker tickets (except documentation
>>> > related, we will deal with them later) from 2.9 release, please check
>>> your
>>> > Jira issues to have the correct "Fix version" field if your ticket is
>>> > planned to 2.9 release.
>>> >
>>> > All currently pinned to 2.9 issues can be found on the release page
>>> [1].
>>> >
>>> > I didn't get about [2] ticket mentioned in this thread, are we going to
>>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
>>> clarify?
>>> >
>>> > [1]:
>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
>>> >
>>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:
>>> >
>>> >> You're now at the "Ignite Release Managers" group.
>>> >> Please check you gain access.
>>> >>
>>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <
>>> [hidden email]>
>>> >> wrote:
>>> >>
>>> >> > Guys,
>>> >> >
>>> >> > I've created the 2.9 release confluence page [1].
>>> >> > Also, I found that I don't have permission to Team City release
>>> tasks.
>>> >> Can
>>> >> > anyone give me such permissions?
>>> >> >
>>> >> > [1]:
>>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>>> >> >
>>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <
>>> [hidden email]>:
>>> >> >
>>> >> > > Igniters
>>> >> > >
>>> >> > > Unfortunately, the ML model export/import feature
>>> >> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
>>> >> development
>>> >> > > yet.
>>> >> > > I need to delay it before the 2.10 release.
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
>>> [hidden email]>:
>>> >> > >
>>> >> > > > Denis,
>>> >> > > >
>>> >> > > > Yes, I still ready to manage it.
>>> >> > > > Today I will prepare a release page on wiki and will try to go
>>> over
>>> >> > > tickets
>>> >> > > > list.
>>> >> > > > Also, I have plans to cut the branch by the end of next week if
>>> >> there
>>> >> > are
>>> >> > > > no objections.
>>> >> > > >
>>> >> > > >
>>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
>>> >> > > >
>>> >> > > > > Igniters,
>>> >> > > > >
>>> >> > > > > Are we moving forward with this release? Alex Plehanov, are
>>> you
>>> >> still
>>> >> > > > ready
>>> >> > > > > to manage it? It seems like everyone agreed with the timeline
>>> you
>>> >> > > > proposed
>>> >> > > > > in the very beginning.
>>> >> > > > >
>>> >> > > > > -
>>> >> > > > > Denis
>>> >> > > > >
>>> >> > > > >
>>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <
>>> [hidden email]>
>>> >> > wrote:
>>> >> > > > >
>>> >> > > > > > Sergey, Ivan,
>>> >> > > > > >
>>> >> > > > > > Could you please check the questions below? If it's
>>> >> time-consuming
>>> >> > to
>>> >> > > > > > rework continuous queries, then the new mode can become
>>> >> available
>>> >> > in
>>> >> > > > the
>>> >> > > > > > experimental state and should not let register continuous
>>> >> queries
>>> >> > to
>>> >> > > > > avoid
>>> >> > > > > > potential deadlocks. Overall, this design gap in continuous
>>> >> queries
>>> >> > > was
>>> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
>>> >> > > connectivity
>>> >> > > > > mode
>>> >> > > > > > will be priceless even if you can't use continuous queries
>>> with
>>> >> > them
>>> >> > > > > > because right now we cannot even start a thick client
>>> inside of
>>> >> a
>>> >> > > > > > serverless function.
>>> >> > > > > >
>>> >> > > > > > Alexey Plehanov,
>>> >> > > > > >
>>> >> > > > > > It looks like we can proceed with the release taking your
>>> >> > timelines.
>>> >> > > > > >
>>> >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
>>> >> > > > > >
>>> >> > > > > > -
>>> >> > > > > > Denis
>>> >> > > > > >
>>> >> > > > > >
>>> >> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <
>>> [hidden email]>
>>> >> > > wrote:
>>> >> > > > > >
>>> >> > > > > >> Ivan, Sergey,
>>> >> > > > > >>
>>> >> > > > > >> How much effort should we put to resolve the issue with
>>> >> > > > > >> continuous queries? Are you working on that issue actively?
>>> >> Let's
>>> >> > > try
>>> >> > > > to
>>> >> > > > > >> guess what would be the ETA.
>>> >> > > > > >>
>>> >> > > > > >> -
>>> >> > > > > >> Denis
>>> >> > > > > >>
>>> >> > > > > >>
>>> >> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
>>> >> > > [hidden email]>
>>> >> > > > > >> wrote:
>>> >> > > > > >>
>>> >> > > > > >>> Hello,
>>> >> > > > > >>>
>>> >> > > > > >>> Sorry for the delay. Sergey Chugunov (
>>> >> [hidden email])
>>> >> > > > just
>>> >> > > > > >>> replied
>>> >> > > > > >>> to the main conversation about "communication via
>>> discovery"
>>> >> [1].
>>> >> > > We
>>> >> > > > > >>> work on it
>>> >> > > > > >>> together and recently have found one hard-to-fix scenario,
>>> >> > detailed
>>> >> > > > > >>> description is
>>> >> > > > > >>> provided in Sergey's reply.
>>> >> > > > > >>>
>>> >> > > > > >>> In short, July 10th looks realistic only if we introduce
>>> new
>>> >> > > behavior
>>> >> > > > > in
>>> >> > > > > >>> its current
>>> >> > > > > >>> implementation, with new setting and IgniteExperimental
>>> >> status.
>>> >> > > > Blocker
>>> >> > > > > >>> here is
>>> >> > > > > >>> current implementation of Continuos Query protocol that in
>>> >> some
>>> >> > > cases
>>> >> > > > > >>> (described
>>> >> > > > > >>> at the end) initiates TCP connection right from discovery
>>> >> thread
>>> >> > > > which
>>> >> > > > > >>> obviously
>>> >> > > > > >>> leads to deadlock. We haven't estimated efforts needed to
>>> >> > redesign
>>> >> > > of
>>> >> > > > > CQ
>>> >> > > > > >>> protocol
>>> >> > > > > >>> but it is definitely a risk and fixing it isn't feasible
>>> with
>>> >> a
>>> >> > > code
>>> >> > > > > >>> freeze at 10th of July.
>>> >> > > > > >>> So my verdict: we can include this new feature in 2.9
>>> scope as
>>> >> > > > > >>> experimental and with
>>> >> > > > > >>> highlighted limitation on CQ usage. Is that OK?
>>> >> > > > > >>>
>>> >> > > > > >>> CQ limitation: server needs to open a communication
>>> >> connection to
>>> >> > > the
>>> >> > > > > >>> client if during
>>> >> > > > > >>> CQ registration client tries to p2p deploy new class not
>>> >> > available
>>> >> > > on
>>> >> > > > > >>> server classpath.
>>> >> > > > > >>> In other cases registration of CQ should be fine.
>>> >> > > > > >>>
>>> >> > > > > >>> [1]
>>> >> > > > > >>>
>>> >> > > > >
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>>> >> > > > > >>>
>>> >> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <
>>> [hidden email]
>>> >> >:
>>> >> > > > > >>>
>>> >> > > > > >>>> Hi,
>>> >> > > > > >>>>
>>> >> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
>>> >> > > > communication
>>> >> > > > > >>>> and
>>> >> > > > > >>>> transactions tracing will be introduced, as well as an
>>> >> option to
>>> >> > > > > >>>> configure
>>> >> > > > > >>>> tracing in runtime. Right now we are working on final
>>> >> > performance
>>> >> > > > > >>>> optimizations, but it's very likely that we'll complete
>>> this
>>> >> > > > activity
>>> >> > > > > >>>> before the code freeze date.
>>> >> > > > > >>>> Let's include tracing to the 2.9 release scope.
>>> >> > > > > >>>>
>>> >> > > > > >>>> More info:
>>> >> > > > > >>>>
>>> >> > > >
>>> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
>>> >> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
>>> >> > > > > >>>>
>>> >> > > > > >>>> --
>>> >> > > > > >>>> Best Regards,
>>> >> > > > > >>>> Ivan Rakov
>>> >> > > > > >>>>
>>> >> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <
>>> >> [hidden email]>
>>> >> > > > wrote:
>>> >> > > > > >>>>
>>> >> > > > > >>>> > Hi folks,
>>> >> > > > > >>>> >
>>> >> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds
>>> reasonable
>>> >> to
>>> >> > > me.
>>> >> > > > > I'd
>>> >> > > > > >>>> like
>>> >> > > > > >>>> > only to hear inputs of @Ivan Rakov <
>>> [hidden email]>,
>>> >> who
>>> >> > > is
>>> >> > > > > >>>> about to
>>> >> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
>>> >> > > > > >>>> > <[hidden email]>, who is fixing a serious
>>> >> limitation
>>> >> > > for
>>> >> > > > K8
>>> >> > > > > >>>> > deployments [1]. Most likely, both features will be
>>> ready
>>> >> by
>>> >> > the
>>> >> > > > > code
>>> >> > > > > >>>> > freeze date (July 10), but the guys should know it
>>> better.
>>> >> > > > > >>>> >
>>> >> > > > > >>>> > [1]
>>> >> > > > > >>>> >
>>> >> > > > > >>>>
>>> >> > > > >
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
>>> >> > > > > >>>> >
>>> >> > > > > >>>> > -
>>> >> > > > > >>>> > Denis
>>> >> > > > > >>>> >
>>> >> > > > > >>>> >
>>> >> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
>>> >> > > > > [hidden email]
>>> >> > > > > >>>> >
>>> >> > > > > >>>> > wrote:
>>> >> > > > > >>>> >
>>> >> > > > > >>>> >> Hello Igniters,
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed here
>>> [1]
>>> >> its
>>> >> > > > time
>>> >> > > > > to
>>> >> > > > > >>>> >> start
>>> >> > > > > >>>> >> the discussion about 2.9 release.
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> I want to propose myself to be the release manager of
>>> the
>>> >> 2.9
>>> >> > > > > >>>> release.
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> What about release time, I agree with Maxim that we
>>> should
>>> >> > > > deliver
>>> >> > > > > >>>> >> features
>>> >> > > > > >>>> >> as frequently as possible. If some feature doesn't fit
>>> >> into
>>> >> > > > release
>>> >> > > > > >>>> dates
>>> >> > > > > >>>> >> we should better include it into the next release and
>>> >> > schedule
>>> >> > > > the
>>> >> > > > > >>>> next
>>> >> > > > > >>>> >> release earlier then postpone the current release.
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> I propose the following dates for 2.9 release:
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> Scope Freeze: June 26, 2020
>>> >> > > > > >>>> >> Code Freeze: July 10, 2020
>>> >> > > > > >>>> >> Voting Date: July 31, 2020
>>> >> > > > > >>>> >> Release Date: August 7, 2019
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> WDYT?
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >> [1] :
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >>
>>> >> > > > > >>>>
>>> >> > > > >
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
>>> >> > > > > >>>> >>
>>> >> > > > > >>>> >
>>> >> > > > > >>>>
>>> >> > > > > >>>
>>> >> > > > > >>>
>>> >> > > > > >>> --
>>> >> > > > > >>> Sincerely yours,
>>> >> > > > > >>> Ivan Bessonov
>>> >> > > > > >>>
>>> >> > > > > >>
>>> >> > > > >
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> >
>>>
>>

[Alexey Plekhanov]

Ilya,
Yes, it works, thank you.

I will update POM version today.

пн, 13 июл. 2020 г. в 16:01, Ilya Kasnacheev <[hidden email]>:

> Hello!
>
> It seems that it works and we now have 2.9 nightlies.
>
> Guys, can you please bump the master POM version to 2.10.0-SNAPSHOT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 10 июл. 2020 г. в 17:43, Ilya Kasnacheev <[hidden email]>:
>
> > Hello!
> >
> > I have also set up nightly builds to (hopefully) build 2.9
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev <[hidden email]>:
> >
> >> Hello!
> >>
> >> I have changed the schedule condition so ignite-2.9 will be run instead.
> >> Please check if it works tomorrow.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov <[hidden email]>:
> >>
> >>> Guys,
> >>>
> >>> Can somebody help with creating scheduled build triggers for nightly
> "Run
> >>> All" on TC for "ignite-2.9" branch?
> >>>
> >>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
> >>> branch [1]. Do we still need it? Or just forgot to remove it after
> >>> release?
> >>>
> >>> [1] :
> >>>
> >>>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly&branch_IgniteTests24Java8=ignite-2.8&tab=buildTypeStatusDiv
> >>>
> >>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov <[hidden email]>:
> >>>
> >>> > Anton, thank you.
> >>> >
> >>> > Guys,
> >>> >
> >>> > I've cut the release branch. From now on please pin resolved in the
> >>> master
> >>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to
> 2.9
> >>> > tickets to ignite-2.9 branch.
> >>> >
> >>> > As far as the release branch cut was delayed, I propose to move code
> >>> > freeze dates by one week (to 17 July 2020). WDYT?
> >>> >
> >>> > I've moved long-time inactive non-blocker tickets (except
> documentation
> >>> > related, we will deal with them later) from 2.9 release, please check
> >>> your
> >>> > Jira issues to have the correct "Fix version" field if your ticket is
> >>> > planned to 2.9 release.
> >>> >
> >>> > All currently pinned to 2.9 issues can be found on the release page
> >>> [1].
> >>> >
> >>> > I didn't get about [2] ticket mentioned in this thread, are we going
> to
> >>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
> >>> clarify?
> >>> >
> >>> > [1]:
> >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
> >>> >
> >>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov <[hidden email]>:
> >>> >
> >>> >> You're now at the "Ignite Release Managers" group.
> >>> >> Please check you gain access.
> >>> >>
> >>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov <
> >>> [hidden email]>
> >>> >> wrote:
> >>> >>
> >>> >> > Guys,
> >>> >> >
> >>> >> > I've created the 2.9 release confluence page [1].
> >>> >> > Also, I found that I don't have permission to Team City release
> >>> tasks.
> >>> >> Can
> >>> >> > anyone give me such permissions?
> >>> >> >
> >>> >> > [1]:
> >>> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
> >>> >> >
> >>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev <
> >>> [hidden email]>:
> >>> >> >
> >>> >> > > Igniters
> >>> >> > >
> >>> >> > > Unfortunately, the ML model export/import feature
> >>> >> > > <https://issues.apache.org/jira/browse/IGNITE-6642> is under
> >>> >> development
> >>> >> > > yet.
> >>> >> > > I need to delay it before the 2.10 release.
> >>> >> > >
> >>> >> > >
> >>> >> > >
> >>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
> >>> [hidden email]>:
> >>> >> > >
> >>> >> > > > Denis,
> >>> >> > > >
> >>> >> > > > Yes, I still ready to manage it.
> >>> >> > > > Today I will prepare a release page on wiki and will try to go
> >>> over
> >>> >> > > tickets
> >>> >> > > > list.
> >>> >> > > > Also, I have plans to cut the branch by the end of next week
> if
> >>> >> there
> >>> >> > are
> >>> >> > > > no objections.
> >>> >> > > >
> >>> >> > > >
> >>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda <[hidden email]>:
> >>> >> > > >
> >>> >> > > > > Igniters,
> >>> >> > > > >
> >>> >> > > > > Are we moving forward with this release? Alex Plehanov, are
> >>> you
> >>> >> still
> >>> >> > > > ready
> >>> >> > > > > to manage it? It seems like everyone agreed with the
> timeline
> >>> you
> >>> >> > > > proposed
> >>> >> > > > > in the very beginning.
> >>> >> > > > >
> >>> >> > > > > -
> >>> >> > > > > Denis
> >>> >> > > > >
> >>> >> > > > >
> >>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <
> >>> [hidden email]>
> >>> >> > wrote:
> >>> >> > > > >
> >>> >> > > > > > Sergey, Ivan,
> >>> >> > > > > >
> >>> >> > > > > > Could you please check the questions below? If it's
> >>> >> time-consuming
> >>> >> > to
> >>> >> > > > > > rework continuous queries, then the new mode can become
> >>> >> available
> >>> >> > in
> >>> >> > > > the
> >>> >> > > > > > experimental state and should not let register continuous
> >>> >> queries
> >>> >> > to
> >>> >> > > > > avoid
> >>> >> > > > > > potential deadlocks. Overall, this design gap in
> continuous
> >>> >> queries
> >>> >> > > was
> >>> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
> >>> >> > > connectivity
> >>> >> > > > > mode
> >>> >> > > > > > will be priceless even if you can't use continuous queries
> >>> with
> >>> >> > them
> >>> >> > > > > > because right now we cannot even start a thick client
> >>> inside of
> >>> >> a
> >>> >> > > > > > serverless function.
> >>> >> > > > > >
> >>> >> > > > > > Alexey Plehanov,
> >>> >> > > > > >
> >>> >> > > > > > It looks like we can proceed with the release taking your
> >>> >> > timelines.
> >>> >> > > > > >
> >>> >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
> >>> >> > > > > >
> >>> >> > > > > > -
> >>> >> > > > > > Denis
> >>> >> > > > > >
> >>> >> > > > > >
> >>> >> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <
> >>> [hidden email]>
> >>> >> > > wrote:
> >>> >> > > > > >
> >>> >> > > > > >> Ivan, Sergey,
> >>> >> > > > > >>
> >>> >> > > > > >> How much effort should we put to resolve the issue with
> >>> >> > > > > >> continuous queries? Are you working on that issue
> actively?
> >>> >> Let's
> >>> >> > > try
> >>> >> > > > to
> >>> >> > > > > >> guess what would be the ETA.
> >>> >> > > > > >>
> >>> >> > > > > >> -
> >>> >> > > > > >> Denis
> >>> >> > > > > >>
> >>> >> > > > > >>
> >>> >> > > > > >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <
> >>> >> > > [hidden email]>
> >>> >> > > > > >> wrote:
> >>> >> > > > > >>
> >>> >> > > > > >>> Hello,
> >>> >> > > > > >>>
> >>> >> > > > > >>> Sorry for the delay. Sergey Chugunov (
> >>> >> [hidden email])
> >>> >> > > > just
> >>> >> > > > > >>> replied
> >>> >> > > > > >>> to the main conversation about "communication via
> >>> discovery"
> >>> >> [1].
> >>> >> > > We
> >>> >> > > > > >>> work on it
> >>> >> > > > > >>> together and recently have found one hard-to-fix
> scenario,
> >>> >> > detailed
> >>> >> > > > > >>> description is
> >>> >> > > > > >>> provided in Sergey's reply.
> >>> >> > > > > >>>
> >>> >> > > > > >>> In short, July 10th looks realistic only if we introduce
> >>> new
> >>> >> > > behavior
> >>> >> > > > > in
> >>> >> > > > > >>> its current
> >>> >> > > > > >>> implementation, with new setting and IgniteExperimental
> >>> >> status.
> >>> >> > > > Blocker
> >>> >> > > > > >>> here is
> >>> >> > > > > >>> current implementation of Continuos Query protocol that
> in
> >>> >> some
> >>> >> > > cases
> >>> >> > > > > >>> (described
> >>> >> > > > > >>> at the end) initiates TCP connection right from
> discovery
> >>> >> thread
> >>> >> > > > which
> >>> >> > > > > >>> obviously
> >>> >> > > > > >>> leads to deadlock. We haven't estimated efforts needed
> to
> >>> >> > redesign
> >>> >> > > of
> >>> >> > > > > CQ
> >>> >> > > > > >>> protocol
> >>> >> > > > > >>> but it is definitely a risk and fixing it isn't feasible
> >>> with
> >>> >> a
> >>> >> > > code
> >>> >> > > > > >>> freeze at 10th of July.
> >>> >> > > > > >>> So my verdict: we can include this new feature in 2.9
> >>> scope as
> >>> >> > > > > >>> experimental and with
> >>> >> > > > > >>> highlighted limitation on CQ usage. Is that OK?
> >>> >> > > > > >>>
> >>> >> > > > > >>> CQ limitation: server needs to open a communication
> >>> >> connection to
> >>> >> > > the
> >>> >> > > > > >>> client if during
> >>> >> > > > > >>> CQ registration client tries to p2p deploy new class not
> >>> >> > available
> >>> >> > > on
> >>> >> > > > > >>> server classpath.
> >>> >> > > > > >>> In other cases registration of CQ should be fine.
> >>> >> > > > > >>>
> >>> >> > > > > >>> [1]
> >>> >> > > > > >>>
> >>> >> > > > >
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> >>> >> > > > > >>>
> >>> >> > > > > >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <
> >>> [hidden email]
> >>> >> >:
> >>> >> > > > > >>>
> >>> >> > > > > >>>> Hi,
> >>> >> > > > > >>>>
> >>> >> > > > > >>>> Indeed, the tracing feature is almost ready. Discovery,
> >>> >> > > > communication
> >>> >> > > > > >>>> and
> >>> >> > > > > >>>> transactions tracing will be introduced, as well as an
> >>> >> option to
> >>> >> > > > > >>>> configure
> >>> >> > > > > >>>> tracing in runtime. Right now we are working on final
> >>> >> > performance
> >>> >> > > > > >>>> optimizations, but it's very likely that we'll complete
> >>> this
> >>> >> > > > activity
> >>> >> > > > > >>>> before the code freeze date.
> >>> >> > > > > >>>> Let's include tracing to the 2.9 release scope.
> >>> >> > > > > >>>>
> >>> >> > > > > >>>> More info:
> >>> >> > > > > >>>>
> >>> >> > > >
> >>> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing
> >>> >> > > > > >>>> https://issues.apache.org/jira/browse/IGNITE-13060
> >>> >> > > > > >>>>
> >>> >> > > > > >>>> --
> >>> >> > > > > >>>> Best Regards,
> >>> >> > > > > >>>> Ivan Rakov
> >>> >> > > > > >>>>
> >>> >> > > > > >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <
> >>> >> [hidden email]>
> >>> >> > > > wrote:
> >>> >> > > > > >>>>
> >>> >> > > > > >>>> > Hi folks,
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> > The timelines proposed by Alex Plekhanov sounds
> >>> reasonable
> >>> >> to
> >>> >> > > me.
> >>> >> > > > > I'd
> >>> >> > > > > >>>> like
> >>> >> > > > > >>>> > only to hear inputs of @Ivan Rakov <
> >>> [hidden email]>,
> >>> >> who
> >>> >> > > is
> >>> >> > > > > >>>> about to
> >>> >> > > > > >>>> > finish with the tracing support, and @Ivan Bessonov
> >>> >> > > > > >>>> > <[hidden email]>, who is fixing a serious
> >>> >> limitation
> >>> >> > > for
> >>> >> > > > K8
> >>> >> > > > > >>>> > deployments [1]. Most likely, both features will be
> >>> ready
> >>> >> by
> >>> >> > the
> >>> >> > > > > code
> >>> >> > > > > >>>> > freeze date (July 10), but the guys should know it
> >>> better.
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> > [1]
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>>
> >>> >> > > > >
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> > -
> >>> >> > > > > >>>> > Denis
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <
> >>> >> > > > > [hidden email]
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> > wrote:
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>> >> Hello Igniters,
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> AI 2.8.1 is finally released and as we discussed
> here
> >>> [1]
> >>> >> its
> >>> >> > > > time
> >>> >> > > > > to
> >>> >> > > > > >>>> >> start
> >>> >> > > > > >>>> >> the discussion about 2.9 release.
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> I want to propose myself to be the release manager
> of
> >>> the
> >>> >> 2.9
> >>> >> > > > > >>>> release.
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> What about release time, I agree with Maxim that we
> >>> should
> >>> >> > > > deliver
> >>> >> > > > > >>>> >> features
> >>> >> > > > > >>>> >> as frequently as possible. If some feature doesn't
> fit
> >>> >> into
> >>> >> > > > release
> >>> >> > > > > >>>> dates
> >>> >> > > > > >>>> >> we should better include it into the next release
> and
> >>> >> > schedule
> >>> >> > > > the
> >>> >> > > > > >>>> next
> >>> >> > > > > >>>> >> release earlier then postpone the current release.
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> I propose the following dates for 2.9 release:
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> Scope Freeze: June 26, 2020
> >>> >> > > > > >>>> >> Code Freeze: July 10, 2020
> >>> >> > > > > >>>> >> Voting Date: July 31, 2020
> >>> >> > > > > >>>> >> Release Date: August 7, 2019
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> WDYT?
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >> [1] :
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>>
> >>> >> > > > >
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575
> >>> >> > > > > >>>> >>
> >>> >> > > > > >>>> >
> >>> >> > > > > >>>>
> >>> >> > > > > >>>
> >>> >> > > > > >>>
> >>> >> > > > > >>> --
> >>> >> > > > > >>> Sincerely yours,
> >>> >> > > > > >>> Ivan Bessonov
> >>> >> > > > > >>>
> >>> >> > > > > >>
> >>> >> > > > >
> >>> >> > > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>> >
> >>>
> >>
>

[Alexey Kuznetsov-2]

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

[Ivan Rakov]

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
>

[Alexey Plekhanov]

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

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

 
 
 
 

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

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,

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]

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,

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]

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

[dmagda]

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