Hi folks, A side note from an external spectator. Should not we reflect on the release page [1] who is a release manager?
[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 Best regards, Ivan Pavlukhin пт, 17 апр. 2020 г. в 11:11, Nikolay Izhikov <nizhi...@apache.org>: > > Hello, Igniters. > > I’ve added all tickets proposed in this thread to 2.8.1 scope [1] > For now we have > > 61 resolved tickets. > 19 unresolved tickets. > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > > > 17 апр. 2020 г., в 01:38, Alex Plehanov <plehanov.a...@gmail.com> > > написал(а): > > > > Hello guys, > > > > I propose to cherry-pick to 2.8.1 following bug-fixes too, which are > > already in master: > > Scan query over an evicted partition can cause node failure (IGNITE-12734 > > [1]) > > Java thin client: There were problems with deserialization of some types on > > the client-side, these types can't be used (IGNITE-12624 > > [2], IGNITE-12468 [3]) > > Java thin client: Thread doesn't stop properly on client close when > > partition awareness is enabled, this prevents main() method from exiting > > (IGNITE-12743 [4]) > > > > Also, there is a performance fix for checkpoint read lock, which I propose > > to cherry-pick too (IGNITE-12491 [5]). This fix brings significant > > performance boost on environments with a large number of CPUs (there was > > some drop on such environments introduced in 2.8.0 for all transactional > > operations after IGNITE-12593 fixing) > > > > WDYT? > > > > [1]: https://issues.apache.org/jira/browse/IGNITE-12734 > > [2]: https://issues.apache.org/jira/browse/IGNITE-12624 > > [3]: https://issues.apache.org/jira/browse/IGNITE-12468 > > [4]: https://issues.apache.org/jira/browse/IGNITE-12743 > > [5]: https://issues.apache.org/jira/browse/IGNITE-12491 > > > > чт, 16 апр. 2020 г. в 18:48, Maxim Muzafarov <mmu...@apache.org>: > > > >> Nikolay, > >> > >> Probably, we should not wait for all blocker issues in minor bug-fix > >> releases except very special cases. I think we should release all > >> accumulated bug-fixes `as is` and schedule the next 2.8.2 release. > >> This will allow as to have shorten minor releases. > >> > >> On Thu, 16 Apr 2020 at 18:17, Nikolay Izhikov <nizhi...@apache.org> wrote: > >>> > >>> Hello, Igniters. > >>> > >>> I’m started to work on this 2.8.1 release [1] > >>> > >>> Resolved issues for release(28) - [2] > >>> Unresolved issues for release(30) - [3] > >>> > >>> My next step: > >>> > >>> 1. I want to double-check that all commits for the tickets with the > >> fixVersion=2.8.1 presented in corresponding release branch. > >>> And cherry-pick losted changes. > >>> > >>> 2. I want to reduce the scope of the release and exclude tickets that is > >> not ready for now. > >>> > >>> As you may know, 2.8.1 is a bug fix release. > >>> Therefore, I think we can wait only for a blocker issues. > >>> > >>> What do you think? > >>> > >>> [1] > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8.1 > >>> [2] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > >>> [3] > >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.8.1%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > >>> > >>> > >>>> 8 апр. 2020 г., в 20:15, Вячеслав Коптилин <slava.kopti...@gmail.com> > >> написал(а): > >>>> > >>>> Folks, > >>>> > >>>> I'd like to add ticket IGNITE-12805 "NullPointerException on node > >> restart > >>>> when 3rd party persistence and Ignite native persistence are used" to > >>>> ignite-2.8.1 scope. > >>>> > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-12805 > >>>> > >>>> Thanks, > >>>> S. > >>>> > >>>> вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev <ilya.kasnach...@gmail.com > >>> : > >>>> > >>>>> Hello! > >>>>> > >>>>> Done! > >>>>> > >>>>> Regards, > >>>>> -- > >>>>> Ilya Kasnacheev > >>>>> > >>>>> > >>>>> вт, 7 апр. 2020 г. в 12:31, Sergey <macrerg...@gmail.com>: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I'm proposing to add > >>>>>> https://issues.apache.org/jira/browse/IGNITE-12549 (fix > >> iterators/scan > >>>>>> queries for replicated caches) > >>>>>> to 2.8.1. > >>>>>> > >>>>>> Best regards, > >>>>>> Sergey Kosarev. > >>>>>> > >>>>>> > >>>>>> вс, 5 апр. 2020 г. в 01:22, Saikat Maitra <saikat.mai...@gmail.com>: > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> I observed that we already have release 2.8.1 branch > >>>>>>> https://github.com/apache/ignite/tree/ignite-2.8.1 > >>>>>>> > >>>>>>> In that case we should be ok to merge these 2 open PRs in master to > >>>>> make > >>>>>> it > >>>>>>> available for 2.9.0 release. > >>>>>>> > >>>>>>> https://github.com/apache/ignite/pull/7240 > >>>>>>> https://github.com/apache/ignite/pull/7227 > >>>>>>> > >>>>>>> Can you please review and confirm? > >>>>>>> > >>>>>>> Regards, > >>>>>>> Saikat > >>>>>>> > >>>>>>> On Fri, Mar 20, 2020 at 8:19 AM Maxim Muzafarov <mmu...@apache.org> > >>>>>> wrote: > >>>>>>> > >>>>>>>> Igniters, > >>>>>>>> > >>>>>>>> I support Nikolay Izhikov as the release manager of 2.8.1 Apache > >>>>>>>> Ignite release. Since no one else of committers, PMCs expressed a > >>>>>>>> desire to lead this release I think we can close this question and > >>>>>>>> focus on the release scope and dates. > >>>>>>>> > >>>>>>>> > >>>>>>>> Ivan, > >>>>>>>> > >>>>>>>> You helped me configuring TC.Bot that time, can you please help > >> again > >>>>>>>> and set `ignite-2.8.1` branch for guard under TC.Bot [1]? We should > >>>>>>>> start collecting TC statistics for the release branch as early as > >>>>>>>> possible. > >>>>>>>> > >>>>>>>> > >>>>>>>> [1] https://mtcga.gridgain.com/guard.html > >>>>>>>> > >>>>>>>> On Fri, 20 Mar 2020 at 14:48, Taras Ledkov <tled...@gridgain.com> > >>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> I propose to add the issue [1] related to SQL query execution to > >>>>> this > >>>>>>>> scope. > >>>>>>>>> > >>>>>>>>> We had omitted this case and Ignite 2.8 contains serious SQL > >> issue: > >>>>>>>>> cursor of a local query is not thread-safe. > >>>>>>>>> It is root cause of several SQL issue, e.g. JDBC thin client > >> cannot > >>>>>>>>> execute query from replicated cache, > >>>>>>>>> PME may hang after execute such queries from JDBC thin, etc. > >>>>>>>>> > >>>>>>>>> [1]. https://issues.apache.org/jira/browse/IGNITE-12800 > >>>>>>>>> > >>>>>>>>> On 19.03.2020 17:52, Denis Magda wrote: > >>>>>>>>>> Igniters, > >>>>>>>>>> > >>>>>>>>>> As long as 2.8.1 is inevitable and we already keep adding > >>>>> critical > >>>>>>>> issues > >>>>>>>>>> to the working queue, let's settle on the release time frames and > >>>>>>>> decide > >>>>>>>>>> who will be a release manager. This is the time proposed by Maxim > >>>>>>> and, > >>>>>>>>>> personally, I concur with such a schedule: > >>>>>>>>>> > >>>>>>>>>> - Scope Freeze: April 15, 2020 > >>>>>>>>>> - Code Freeze: April 22, 2020 > >>>>>>>>>> - Voting Date: April 27, 2020 > >>>>>>>>>> - Release Date: May 1, 2020 > >>>>>>>>>> > >>>>>>>>>> Do we agree on this time? Is there anybody who ready to drive the > >>>>>>>> release > >>>>>>>>>> as a release manager? > >>>>>>>>>> > >>>>>>>>>> - > >>>>>>>>>> Denis > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Thu, Mar 19, 2020 at 5:50 AM Sergey Antonov < > >>>>>>>> antonovserge...@gmail.com> > >>>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> Folks, > >>>>>>>>>>> > >>>>>>>>>>> I'd like to add ticket IGNITE-12774 Transaction hangs after too > >>>>>> many > >>>>>>>> open > >>>>>>>>>>> files NIO exception [1] to ignite-2.8.1 scope. > >>>>>>>>>>> > >>>>>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-12774 > >>>>>>>>>>> > >>>>>>>>>>> ср, 18 мар. 2020 г. в 16:53, Maxim Muzafarov <mmu...@apache.org > >>>>>> : > >>>>>>>>>>> > >>>>>>>>>>>> Folks, > >>>>>>>>>>>> > >>>>>>>>>>>> Can we add ignite-2.8.1 [2] branch under TC.Bot protection [1]? > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> [1] https://mtcga.gridgain.com/guard.html > >>>>>>>>>>>> [2] https://github.com/apache/ignite/tree/ignite-2.8.1 > >>>>>>>>>>>> > >>>>>>>>>>>> On Mon, 16 Mar 2020 at 16:32, Alexey Goncharuk > >>>>>>>>>>>> <alexey.goncha...@gmail.com> wrote: > >>>>>>>>>>>>> Folks, > >>>>>>>>>>>>> > >>>>>>>>>>>>> I've walked through all the commits to master since 2.8 branch > >>>>>> was > >>>>>>>> cut > >>>>>>>>>>>> and > >>>>>>>>>>>>> filtered some tickets that in my opinion are worth including > >>>>> to > >>>>>>>> 2.8.1 > >>>>>>>>>>>>> release below (note that they are ready end the effort of > >>>>>>> including > >>>>>>>>>>> them > >>>>>>>>>>>> to > >>>>>>>>>>>>> the release should be low as long as there are no implicit > >>>>>>>> dependencies > >>>>>>>>>>>>> between tickets). Please share your opinion on whether we > >>>>> should > >>>>>>>>>>> include > >>>>>>>>>>>>> them to the 2.8.1. > >>>>>>>>>>>>> > >>>>>>>>>>>>> IGNITE-12717 SQL: index creation refactoring > >>>>>>>>>>>>> IGNITE-12590 MERGE INTO query is failing on Ignite client node > >>>>>>>>>>>>> IGNITE-12671 Update of partition's states can stuck when > >>>>>> rebalance > >>>>>>>>>>>>> completed during exchange > >>>>>>>>>>>>> IGNITE-11798 Memory leak on unstable topology caused by > >>>>>> partition > >>>>>>>>>>>>> reservation > >>>>>>>>>>>>> IGNITE-12665 SQL: Potential race on MapResult close. > >>>>>>>>>>>>> IGNITE-12605 Historical (WAL) rebalance can start on a cleared > >>>>>>>>>>> partition > >>>>>>>>>>>> if > >>>>>>>>>>>>> some baseline node leaves the cluster and then joins back. > >>>>>>>>>>>>> IGNITE-12654 Some of rentingFutures in > >>>>>>> GridDhtPartitionTopologyImpl > >>>>>>>> may > >>>>>>>>>>>>> accumulate a huge number of eviction callbacks > >>>>>>>>>>>>> IGNITE-12631 Incorrect rewriting wal record type in marshalled > >>>>>>> mode > >>>>>>>>>>>> during > >>>>>>>>>>>>> iteration > >>>>>>>>>>>>> IGNITE-12621 Node leave may cause NullPointerException during > >>>>> IO > >>>>>>>>>>> message > >>>>>>>>>>>>> processing if security is enabled > >>>>>>>>>>>>> IGNITE-12636 Full rebalance instead of a historical one > >>>>>>>>>>>>> IGNITE-12618 Affinity cache for version of last server event > >>>>> can > >>>>>>> be > >>>>>>>>>>> wiped > >>>>>>>>>>>>> from history > >>>>>>>>>>>>> IGNITE-12013 NullPointerException is thrown by > >>>>>>> ExchangeLatchManager > >>>>>>>>>>>> during > >>>>>>>>>>>>> cache creation > >>>>>>>>>>>>> IGNITE-11797 Fix consistency issues for atomic and mixed > >>>>>> tx-atomic > >>>>>>>>>>> cache > >>>>>>>>>>>>> groups. > >>>>>>>>>>>>> IGNITE-12557 Destroy of big cache which is not only cache in > >>>>>> cache > >>>>>>>>>>> group > >>>>>>>>>>>>> causes IgniteOOME > >>>>>>>>>>>>> IGNITE-12567 H2Tree goes into illegal state when non-indexed > >>>>>>> columns > >>>>>>>>>>> are > >>>>>>>>>>>>> dropped > >>>>>>>>>>>>> IGNITE-12569 Can't set serialized enum to a BinaryObject's > >>>>> field > >>>>>>>>>>>>> IGNITE-12460 Cluster fails to find the node by consistent ID > >>>>>>>>>>>>> IGNITE-12459 Searching checkpoint record in WAL doesn't work > >>>>>> with > >>>>>>>>>>> segment > >>>>>>>>>>>>> compaction > >>>>>>>>>>>>> IGNITE-12548 Possible tx desync during recovery on near node > >>>>>> left. > >>>>>>>>>>>>> IGNITE-12546 Prevent partitions owned by other nodes switch > >>>>>> their > >>>>>>>> state > >>>>>>>>>>>> to > >>>>>>>>>>>>> MOVING due to counter difference on node join. > >>>>>>>>>>>>> IGNITE-12551 Partition desync if a partition is evicted then > >>>>>> owned > >>>>>>>>>>> again > >>>>>>>>>>>>> and historically rebalanced > >>>>>>>>>>>>> IGNITE-12536 Inconsistency between cache data and indexes when > >>>>>>> cache > >>>>>>>>>>>>> operation is interrupted > >>>>>>>>>>>>> IGNITE-12403 Throttle page difference output in > >>>>>> PageMemoryTracker > >>>>>>>>>>>>> IGNITE-12523 Continuously generated thread dumps in failure > >>>>>>>> processor > >>>>>>>>>>>> slow > >>>>>>>>>>>>> down the whole system > >>>>>>>>>>>>> IGNITE-12489 Error during purges by expiration: Unknown page > >>>>>> type > >>>>>>>>>>> > >>>>>>>>>>> -- > >>>>>>>>>>> BR, Sergey Antonov > >>>>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> Taras Ledkov > >>>>>>>>> Mail-To: tled...@gridgain.com > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>> > >> >
