Hi Vladimir, The regression, as well as the performance, is definitely bad. Please work with Sergey to see how much time he needs to rerun the whole test set if you merge the changes.
I would target the end of the next week as a release date if the vote goes well. Probably, we can run the test suites over the weekend if your changes get to the branch. Nikolay Izhikov, follow up with Vladimir and Sergey tomorrow. If they decide to merge the fixes then you are free to merge your fixed for Spark examples. -- Denis On Thu, Mar 1, 2018 at 7:46 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > Hi, > > We found one nasty regression in DROP COLUMN feature and fixed it today. > Another problem is performance - we found that recent changes to TCP > communication metrics caused considerable slowdown in in-memory mode. I > almost fixed it and will merge the fix in the nearest day if benchmarks are > ok. > > That said I think we will be able to start vote in the beginning of the > next week. > > Any objections? > > Vladimir. > > On Mon, Feb 26, 2018 at 11:22 PM, Denis Magda <dma...@apache.org> wrote: > > > Good question! > > > > We've been waiting for a sign-off from Alexey Goncharuk and Sergey Kozlov > > who are benchmarking and trying to address performance issues in > > coopeartion. > > > > Guys, please share your results and forecast. > > > > -- > > Denis > > > > On Sun, Feb 25, 2018 at 12:10 AM, Pavel Tupitsyn <ptupit...@apache.org> > > wrote: > > > > > Igniters, > > > > > > Any update on the 2.4 release status? Anything else to merge there? > > > > > > Pavel > > > > > > On Mon, Feb 19, 2018 at 9:30 PM, Dmitriy Setrakyan < > > dsetrak...@apache.org> > > > wrote: > > > > > > > On Mon, Feb 19, 2018 at 1:37 AM, Vladimir Ozerov < > voze...@gridgain.com > > > > > > > wrote: > > > > > > > > > Alex, > > > > > > > > > > You get me right. DEFAULT -> LOG_ONLY doesn't introduce any > dramatic > > > > > changes when comparing 2.3 to 2.4 - Ignite was unsafe out of the > box > > in > > > > > 2.3, and it is unsafe in 2.4 as well. > > > > > > > > > > The very problem is that we claim ourselves to be ACID, while in > > > reality > > > > we > > > > > are only "AI" out of the box, because durability is not guaranteed > > due > > > to > > > > > zero backups and LOG_ONLY and consistency is not guaranteed due to > > > > > PRIMARY_SYNC. Neither Cassandra, nor Mongo or any others claim > > > themselves > > > > > to be ACID, so it is not valid to refer to their defaults. > > > > > > > > > > > > > Vladimir, > > > > Ignite can be fully ACID, but at the same time have non-ACID > defaults, > > as > > > > long as we clearly document how to get ACID behavior. I do not see an > > > issue > > > > with it. > > > > > > > > D. > > > > > > > > > >
