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

This patch [1] interesting only a deployment where clients often reconnecting (stopping/starting) to cluster. In these cases Coordinator node could fail by OOM, even the cluster did not use MVCC caches. On Mon, Oct 12, 2020 at 1:41 PM Zhenya Stanilovsky wrote: > > > without [2] and [3] we obtain

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

without [2] and [3] we obtain unexpected fields in index creation and as a consequence buggy sql execution and pla of course.   >Guys, > >I've found 3 more tickets which were targeted to 2.9 but merged only to the >master branch ([1], [2], [3]). >Do we need these tickets in 2.9? Are they criti

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

Ivan, Thank you. We've got performance drop on our benchmarks too. We are trying to bisect changes and find problematic commit now. чт, 6 авг. 2020 г. в 14:51, Ivan Artiukhov : > Hello, > > I've compared performances of 2.9 and 2.8.1 using Yardstick and some > atomic/transactional/SQL operations

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

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

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

I recently found, that control.sh is broken since 2.8.0 a little bit. Script returns always 0 code, despite the fact, that CommandHandler returns code correctly. Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328, patch is available. пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :

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

Ivan, IGNITE-13306 cherry-picked to 2.9 пт, 31 июл. 2020 г. в 13:43, Ivan Rakov : > Hi Alex, > > https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master. > Can you please cherry-pick to 2.9? > > On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev > wrote: > >> Hello! >> >> I don't th

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

Hi Alex, https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master. Can you please cherry-pick to 2.9? On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev wrote: > Hello! > > I don't think that IGNITE-13006 > is a blocker in any > wa

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

Hello! I don't think that IGNITE-13006 is a blocker in any way. It is a good candidate for 3.0. ignite-spring will work with 4.x Spring as well as 5.x and the user is free to bump Spring version. I think bumping this dependency explicitly is in

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

Guys, Is there a chance to squeeze the fix for the following issue in: https://issues.apache.org/jira/browse/IGNITE-13306 ? The issue makes the CPU load metric show -1 on Java 11. This is a quite important metric, and this bug makes it harder to

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

Guys, I've cherry-picked IGNITE-12438 (One-way client-server connections) and IGNITE-13038 (Web console removing) to 2.9. Since there are no objections I will move IGNITE-13006 (Spring libs upgrade to 5.2 version), IGNITE-12489 (Error during purges by expiration) and IGNITE-12553 (public Java met

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

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

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

Hi guys, considering Denis's question: [1] ("inverse TCP connection establishment") is already in master. I think we should port it in 2.9, would be a good thing. "Serverless functions" [2] support is code complete in a private branch, it's safe to say that the issue will be completed next week (

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

Sharing a correct link for the Web Console task: https://issues.apache.org/jira/browse/IGNITE-13038 - Denis On Wed, Jul 22, 2020 at 7:59 AM Denis Magda wrote: > Hi Alex, > > Thanks for wrapping this up and sharing the progress. > > I've continued the discussion in the Hadoop thread. Let's take

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

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 change

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

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

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

Ivan, Merged to 2.9. Thanks пт, 17 июл. 2020 г. в 01:35, Ivan Rakov : > Alex, > > Tracing is merged to master: > https://issues.apache.org/jira/browse/IGNITE-13060 > > Can you please port it to 2.9? > For you convenience, there's PR versus 2.9 with conflicts resolved: > https://github.com/apach

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

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 A

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

Ivan, Looks like master is broken after IGNITE-13246 (but everything is ok in 2.9 branch) ср, 15 июл. 2020 г. в 18:54, Alex Plehanov : > Zhenya, Ivan, > > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch. > Thank you. > > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov : > >> Guy

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

Zhenya, Ivan, I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch. Thank you. ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov : > Guys, > > can you please backport https://issues.apache.org/jira/browse/IGNITE-13246 > to ignite-2.9? Me and Alexey Kuznetsov really want these new event

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

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

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

  Alex, i also suggest to merge this  https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient leakage and further TC OOM preventing.   >Ivan, > >It was already in release scope as discussed in this thread. > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >: >  >> Hi,