Hi Igniters, There are two tickets I forgot to mention, it is optimisation of Native Persistence:
Performing data pages IO outside locks - https://issues.apache.org/jira/browse/IGNITE-7606 - Write removed dirty page during replacement without holding segment write lock - https://issues.apache.org/jira/browse/IGNITE-7698 - Page read during replacement should be outside of segment write lock Both are resovled, so no delays from their side. Sincerely, Dmitriy Pavlov пт, 23 мар. 2018 г. в 12:06, Ivan Rakov <ivan.glu...@gmail.com>: > I agree. > Fix of LOG_ONLY is critical for Ignite durability and can be done quickly. > Another reason to release 2.5 earlier is fix of > https://issues.apache.org/jira/browse/IGNITE-7751. It's another critical > bug that possibly can lead to checkpoint buffer overflow and corruption of > internal data structures even with Pages Write Throttling enabled. > > Best Regards, > Ivan Rakov > > On 22.03.2018 23:20, Dmitry Pavlov wrote: > > Hi Igniters, > > Why not? Let's release it a bit earlier. > > I think it would be good if Ivan will prepare fix for WAL LOG_ONLY: > http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html > Ivan, what do you think? > > Also it would be great if we can complete as much MTCGA tickets as we can. > Let's do this release with green TC. > > Sincerely, > Dmitriy Pavlov > > чт, 22 мар. 2018 г. в 22:08, Nikolay Izhikov <nizhi...@apache.org>: > >> Also, we has new API - ContinuousQueryWithTransformer merged for 2.5 >> release - [IGNITE-425] >> >> В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет: >> > Hello, guys >> > >> > I agree with earlier release. >> > >> > I propose to include my task IGNITE-7077 to 2.5 release. >> > >> > Valentin, do you have a time slot to review my implementation? >> > >> > В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет: >> > > Igniters, >> > > >> > > According to our regular schedule, every new Ignite version usually >> goes >> > > public once in 3 months. As you remember, the latest 2.4 release, >> which >> > > took us 5 months to improve and roll out, was based on the version of >> the >> > > source code dated by January. >> > > >> > > Since that time the master branch went far ahead and already >> incorporates >> > > many valuable fixes and capabilities such as: >> > > >> > > - Fixes provided as a part of "Gree Team City" activity. >> > > - Persistence: page replacement algorithm and throttling >> optimizations, >> > > out of memory in checkpointing buffer corrections, etc. Alex G and >> Ivan can >> > > shed more light here. >> > > - Data loading optimizations for SQL: streaming for JDBC thin >> driver and >> > > copy command >> > > - Genetic Algorithms Grid Contribution! >> > > - Java Thin Client developed by Alexey Kukushkin >> > > >> > > >> > > - the list goes on and on... Please share the contributions you are >> > > ready to release. >> > > >> > > So, why don't we go ahead and release the current master and possibly >> extra >> > > tickets that are in the review state earlier? What's about April 30 >> as the >> > > next release date? >> > > >> > > -- >> > > Densi > > >
