Sure, here's PR with 3 cherry-picked commits that I mentioned: https://github.com/apache/ignite/pull/7708
вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov <nizhi...@apache.org>: > OK then, let’s include it in the 2.8.1 > > Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain > cherry-pick for all required commits? > > > 21 апр. 2020 г., в 17:01, Andrey Gura <ag...@apache.org> написал(а): > > > > Hi > > > >> IGNITE-12735 - Metric exporter implementation could lead to > NullPointerException from gauge which invoke communication > >> IGNITE-12568 - MessageFactory implementations refactoring > > > >> Personally, I’m against any refactoring improvements in bug fix release. > >> So, I propose to exclude IGNITE-12756 from 2.8.1 > > > >> Andrey, what do you think as a committer of this improvements? > > > > Mainly IGNITE-12756 brings some improvements related with TCP > > communication metrics (performance, memory footprint, IgniteSpiContext > > improved in order to provide ability to implement metrics related > > SPI's without using internal API's, code improvements) > > > > But! It also fixes potential NPE's which can be thrown on node start. > > So it would be great to include this fix to 2.8.1 release. > > > > On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov <nizhi...@apache.org> > wrote: > >> > >>> I've cherry-picked IGNITE-12734 to 2.8.1 branch. > >> > >> > >> Thanks! > >> > >>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI > metrics > >>>> improvement" - it depends > >>>> on https://issues.apache.org/jira/browse/IGNITE-12735 and > >>>> https://issues.apache.org/jira/browse/IGNITE-12568, > >>>> both were targeted to 2.9, but this has to be changed probably. > >> > >> IGNITE-12735 - Metric exporter implementation could lead to > NullPointerException from gauge which invoke communication > >> IGNITE-12568 - MessageFactory implementations refactoring > >> > >> Ivan, > >> Personally, I’m against any refactoring improvements in bug fix release. > >> So, I propose to exclude IGNITE-12756 from 2.8.1 > >> > >> Andrey, what do you think as a committer of this improvements? > >> > >> > >>> 21 апр. 2020 г., в 10:44, Alex Plehanov <plehanov.a...@gmail.com> > написал(а): > >>> > >>> Nikolay, > >>> > >>> I've cherry-picked IGNITE-12734 to 2.8.1 branch. > >>> > >>> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov <bessonov...@gmail.com>: > >>> > >>>> Hello, Igniters, > >>>> > >>>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI > metrics > >>>> improvement" - it depends > >>>> on https://issues.apache.org/jira/browse/IGNITE-12735 and > >>>> https://issues.apache.org/jira/browse/IGNITE-12568, > >>>> both were targeted to 2.9, but this has to be changed probably. > >>>> > >>>> There might be other issues that I didn't find, we should probably ask > >>>> Andrey Gura about it, he is the author of > >>>> those changes. > >>>> > >>>> So, release scope should be expanded a little bit, are you ok with it? > >>>> > >>>> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov <nizhi...@apache.org>: > >>>> > >>>>> Hello, Igniters. > >>>>> > >>>>> I perform cherry-pick for most commits targeted for 2.8.1 release. > >>>>> > >>>>> TC bot results - > >>>>> > >>>> > https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull%2F7690%2Fhead&action=Latest&baseBranchForTc=pull%2F7102%2Fhead > >>>>> > >>>>> I need help with cherry picking the following commits: > >>>>> > >>>>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from > >>>>> GridSecurityProcessor - Fixes #7523. > >>>>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649) > >>>>> - 0b185b192f IGNITE-12800 SQL: local queries cursors must be closed > or > >>>>> full read to unlock the GridH2Table. (#7551) > >>>>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - > Fixes > >>>>> #7494. > >>>>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement > >>>>> > >>>>> Denis Garus, > >>>>> Taras Ledkov, > >>>>> Alexey Plekhanov, > >>>>> Ivan Bessonov, > >>>>> > >>>>> Can you help me with above commits and cherry-pick your contribution > in > >>>>> ignite-2.8.1 branch? > >>>>> > >>>>> CHERRY PICKED: > >>>>> > >>>>> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method > >>>> which > >>>>> must not be used in production code (#7604) > >>>>> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails > BatchUpdateException > >>>>> if function is used (#7615) > >>>>> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory > restore > >>>>> is in progress. Fixes #7562 > >>>>> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with > failed > >>>>> deployment. (#7620) > >>>>> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606) > >>>>> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the > >>>> Timestamp > >>>>> and Guid params. (#7618) > >>>>> + 6f3515686f IGNITE-12769: histogramNames cache in > MetricRegistryMBean > >>>>> removed. (#7549) > >>>>> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - > Fixes > >>>>> #7516. > >>>>> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression. > >>>>> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on > >>>>> client close when partition awareness is enabled - Fixes #7522. > >>>>> + e389bb8f55 IGNITE-12728 Collect time statistics on > cache#putAllAsync - > >>>>> Fixes #7483. > >>>>> + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469. > >>>>> + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE > command > >>>>> (#7321) > >>>>> + 59917f0731 IGNITE-12624 Java thin client: typeId generation for > system > >>>>> types fixed - Fixes #7416. > >>>>> + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can > prevent > >>>>> late affinity switch. - Fixes #7425. > >>>>> + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology > caused by > >>>>> partition reservation (#7251) > >>>>> + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult > close. > >>>>> + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - > Fixes > >>>>> #7411. > >>>>> + 100101ccce IGNITE-12605: Reset initial update counter value before > >>>>> clearing a partition (#7341) > >>>>> + e17887bfbf IGNITE-12654 Some of rentingFutures in > >>>>> GridDhtPartitionTopologyImpl may accumulate a huge number of eviction > >>>>> callbacks - Fixes #7399. > >>>>> + bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy > cause > >>>>> failure handle and node shutdown - Fixes #7397. > >>>>> + 56a515db6d IGNITE-12631 Incorrect rewriting wal record type in > >>>>> marshalled mode during iteration - Fixes #7371. > >>>>> + 14dd160f90 IGNITE-12621 Node leave may cause NullPointerException > >>>> during > >>>>> IO message processing if security is enabled - Fixes #7366. > >>>>> + 67ac1d5d68 IGNITE-12636 Full rebalance instead of a historical one > - > >>>>> Fixes #7379. > >>>>> + 4433485d74 IGNTIE-12468 Java thin client: deserialization of > arrays, > >>>>> collections and maps fixed - Fixes #7320. > >>>>> + 0dfd98388e IGNITE-12618 Affinity cache for version of last server > event > >>>>> can be wiped from history - Fixes #7359. > >>>>> + e2c597fff1 IGNITE-12013 NullPointerException is thrown by > >>>>> ExchangeLatchManager during cache creation - Fixes #7335. > >>>>> + cebc76f1f5d7d077093ddaecbabcd8db2106c60a - IGNITE-12545 Introduce > >>>>> listener interface for components to react to partition map exchange > >>>> events > >>>>> + a9278eedf7 IGNITE-11797 Fixed partition consistency issues for > atomic > >>>>> and mixed tx-atomic cache groups. - Fixes #7315. > >>>>> + e160c8f231 IGNITE-12557 Fix possible IgniteOOM during cache > destroy. - > >>>>> Fixes #7298. > >>>>> + 41ed3294ec IGNITE-12567 H2Tree goes into illegal state when > non-indexed > >>>>> columns are dropped - Fixes #7290. > >>>>> + e89c71d3cb IGNITE-12569 Can't set serialized enum to a > BinaryObject's > >>>>> field - Fixes #7292. > >>>>> + 66593af03aeac37d0e76b6c010e8386f6f0c36c7 - IGNITE-12479 Make binary > >>>>> metadata be registered only once per type creation > >>>>> + 6668d86ad4 IGNITE-12460 Cluster fails to find the node by > consistent ID > >>>>> - Fixes #7151. > >>>>> + 214044ae2e IGNITE-12459 Searching checkpoint record in WAL doesn't > work > >>>>> with segment compaction - Fixes #7148. > >>>>> + b677b36cc4 IGNITE-12548 Fixed tx desync during recovery on near > node > >>>>> left. - Fixes #7274. > >>>>> + 223281be93 IGNITE-12546 Prevent partitions owned by other nodes > switch > >>>>> their state to MOVING due to counter difference on node join. - Fixes > >>>> #7273. > >>>>> + 5bd385935bcba9a1cc271497d1818e9bb4f0318a IGNITE-12227 Fix failed > >>>>> compilation due to concurrent merge > >>>>> + 5e95f65bbc IGNITE-12551 Partition desync if a partition is evicted > then > >>>>> owned again and historically rebalanced. - Fixes #7270. > >>>>> + 1fbc284fd0 IGNITE-12101 Fixed NullPointerException when > >>>>> IgniteQueue.removeAll is called. - Fixes #7266. > >>>>> + b9bab88cbb IGNITE-12536: Inconsistency between cache data and > indexes > >>>>> when cache operation is interrupted. > >>>>> + 50f8f8c5be IGNITE-12403 Throttle output of bytes in > >>>>> PageMemoryTracker/tests - Fixes #7086. > >>>>> + 594061d906 IGNITE-12523 Added throttling for thread dumps > generation on > >>>>> system failure. > >>>>> + c97b08e672 IGNITE-12491 Dirty pages count calculation optimized. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> 18 апр. 2020 г., в 18:59, Nikolay Izhikov <nizhikov....@gmail.com> > >>>>> написал(а): > >>>>>> > >>>>>> Hello, Igniters. > >>>>>> > >>>>>> After some scripting I got the following lists of commits to > transfer > >>>>> from master to 2.8.1 > >>>>>> It will be very helpful if someone double check my results. > >>>>>> > >>>>>> I did the following: > >>>>>> > >>>>>> 1. Export all resolved tickets targeted to 2.8.1 from Mira > >>>>>> 2. Found commit difference between 2.8.0 and master > >>>>>> > >>>>>> git merge-base upstream-http/ignite-2.8 upstream-http/master > >>>>>> git log --pretty=oneline --abbrev-commit > >>>>> 9265c04a368c4cf0fc331aac5a71f7d0db365ea8..HEAD > >>>>>> > >>>>>> 3. Filter commits to transfer preserving order with the dirty python > >>>>> script: > >>>>>> > >>>>>> ``` > >>>>>> tickets = set() > >>>>>> founded = {} > >>>>>> with open("/Users/sbt-izhikov-nv/src/ignite-2.8.1/resolved.csv") as > >>>>> file_in: > >>>>>> for line in file_in: > >>>>>> if not line.startswith('-'): > >>>>>> ticket = line[:-1] > >>>>>> tickets.add(ticket) > >>>>>> founded[ticket] = 0 > >>>>>> print(tickets) > >>>>>> > >>>>>> with > >>>>> > open("/Users/sbt-izhikov-nv/src/ignite-2.8.1/commits-after-cut-2.8.txt") > >>>> as > >>>>> file_in: > >>>>>> for commit_msg in file_in: > >>>>>> for ticket in tickets: > >>>>>> if ticket in commit_msg: > >>>>>> print(commit_msg) > >>>>>> founded[ticket] += 1 > >>>>>> > >>>>>> for ticket in founded.keys(): > >>>>>> if founded[ticket] != 1: > >>>>>> print(ticket + " = " + str(founded[ticket])) > >>>>>> ``` > >>>>>> > >>>>>> Results: > >>>>>> > >>>>>> > >>>>>> TO CHERRY PICK (FROM BOTTOM TO TOP): > >>>>>> 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from > >>>>> GridSecurityProcessor - Fixes #7523. > >>>>>> a65e51c914 IGNITE-12790 Introduce distributed SQL configuration and > >>>>> ability to disable SQL functions. (#7593) > >>>>>> d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method > >>>> which > >>>>> must not be used in production code (#7604) > >>>>>> 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails > BatchUpdateException > >>>>> if function is used (#7615) > >>>>>> 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649) > >>>>>> b8167296b1 IGNITE-12805 Fixed NullPointerException when memory > restore > >>>>> is in progress. Fixes #7562 > >>>>>> f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed > >>>>> deployment. (#7620) > >>>>>> 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606) > >>>>>> 2b1d2b4dec IGNITE-12859: Support of .Net service call with the > >>>> Timestamp > >>>>> and Guid params. (#7618) > >>>>>> 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean > >>>>> removed. (#7549) > >>>>>> 0b185b192f IGNITE-12800 SQL: local queries cursors must be closed > or > >>>>> full read to unlock the GridH2Table. (#7551) > >>>>>> 795617fc94 IGNITE-12774 Handle "Too many open files" exception - > Fixes > >>>>> #7516. > >>>>>> 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression. > >>>>>> bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - > Fixes > >>>>> #7494. > >>>>>> ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on > >>>>> client close when partition awareness is enabled - Fixes #7522. > >>>>>> 13637a2dfe IGNITE-12745: Compute job view implemented. (#7495) > >>>>>> e389bb8f55 IGNITE-12728 Collect time statistics on > cache#putAllAsync - > >>>>> Fixes #7483. > >>>>>> 4921fcf1fe IGNITE-12701 : Disallow silent deactivation in CLI and > REST. > >>>>> (#7471) > >>>>>> 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement > >>>>>> e4f9be52f8 IGNITE-12717 SQL: index creation refactoring (#7474) > >>>>>> 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469. > >>>>>> f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command > >>>>> (#7321) > >>>>>> 59917f0731 IGNITE-12624 Java thin client: typeId generation for > system > >>>>> types fixed - Fixes #7416. > >>>>>> cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can > prevent > >>>>> late affinity switch. - Fixes #7425. > >>>>>> 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused > by > >>>>> partition reservation (#7251) > >>>>>> 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close. > >>>>>> 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - > Fixes > >>>>> #7411. > >>>>>> 100101ccce IGNITE-12605: Reset initial update counter value before > >>>>> clearing a partition (#7341) > >>>>>> e17887bfbf IGNITE-12654 Some of rentingFutures in > >>>>> GridDhtPartitionTopologyImpl may accumulate a huge number of eviction > >>>>> callbacks - Fixes #7399. > >>>>>> bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy > cause > >>>>> failure handle and node shutdown - Fixes #7397. > >>>>>> 56a515db6d IGNITE-12631 Incorrect rewriting wal record type in > >>>>> marshalled mode during iteration - Fixes #7371. > >>>>>> 14dd160f90 IGNITE-12621 Node leave may cause NullPointerException > >>>> during > >>>>> IO message processing if security is enabled - Fixes #7366. > >>>>>> 67ac1d5d68 IGNITE-12636 Full rebalance instead of a historical one - > >>>>> Fixes #7379. > >>>>>> 4433485d74 IGNTIE-12468 Java thin client: deserialization of arrays, > >>>>> collections and maps fixed - Fixes #7320. > >>>>>> 0dfd98388e IGNITE-12618 Affinity cache for version of last server > event > >>>>> can be wiped from history - Fixes #7359. > >>>>>> e2c597fff1 IGNITE-12013 NullPointerException is thrown by > >>>>> ExchangeLatchManager during cache creation - Fixes #7335. > >>>>>> a9278eedf7 IGNITE-11797 Fixed partition consistency issues for > atomic > >>>>> and mixed tx-atomic cache groups. - Fixes #7315. > >>>>>> e160c8f231 IGNITE-12557 Fix possible IgniteOOM during cache > destroy. - > >>>>> Fixes #7298. > >>>>>> 41ed3294ec IGNITE-12567 H2Tree goes into illegal state when > non-indexed > >>>>> columns are dropped - Fixes #7290. > >>>>>> e89c71d3cb IGNITE-12569 Can't set serialized enum to a > BinaryObject's > >>>>> field - Fixes #7292. > >>>>>> 6668d86ad4 IGNITE-12460 Cluster fails to find the node by > consistent ID > >>>>> - Fixes #7151. > >>>>>> 214044ae2e IGNITE-12459 Searching checkpoint record in WAL doesn't > work > >>>>> with segment compaction - Fixes #7148. > >>>>>> b677b36cc4 IGNITE-12548 Fixed tx desync during recovery on near node > >>>>> left. - Fixes #7274. > >>>>>> 223281be93 IGNITE-12546 Prevent partitions owned by other nodes > switch > >>>>> their state to MOVING due to counter difference on node join. - Fixes > >>>> #7273. > >>>>>> 5e95f65bbc IGNITE-12551 Partition desync if a partition is evicted > then > >>>>> owned again and historically rebalanced. - Fixes #7270. > >>>>>> 1fbc284fd0 IGNITE-12101 Fixed NullPointerException when > >>>>> IgniteQueue.removeAll is called. - Fixes #7266. > >>>>>> b9bab88cbb IGNITE-12536: Inconsistency between cache data and > indexes > >>>>> when cache operation is interrupted. > >>>>>> 50f8f8c5be IGNITE-12403 Throttle output of bytes in > >>>>> PageMemoryTracker/tests - Fixes #7086. > >>>>>> 594061d906 IGNITE-12523 Added throttling for thread dumps > generation on > >>>>> system failure. > >>>>>> c97b08e672 IGNITE-12491 Dirty pages count calculation optimized. > >>>>>> > >>>>>> ALREADY IN 2.8.1: > >>>>>> 1b51981c43 IGNITE-8343 Skip IPv6 address if node is started in > 'prefer > >>>>> IPv4' mode. > >>>>>> bd67b31819 IGNITE-12549 Fix query mapping on REPLICATED cache during > >>>>> rebalance (#7277) > >>>>>> 87a7c4de90 IGNITE-12863 Initialize PojoField accessor after > >>>>> deserialization - Fixes #7624. > >>>>>> 1f34def836 IGNITE-12860 .NET: Fix NRE in BinaryStructure.GetFieldId > >>>>>> ad6759f955 IGNITE-12757 Visor CMD: Fixed invalid properties - Fixes > >>>>> #7505. > >>>>>> 5100ec3e5c IGNITE-12672 Fix incorrect parsing of lower-case > statements > >>>>> in Spring Data. > >>>>>> 6a81a7d6db IGNITE-12768: MetricRegistryMBean doesn't show histogram > >>>>> values in case when histogram name contains underscore character > (#7542) > >>>>>> 8246bd8427 IGNITE-12746 Regression in GridCacheColocatedDebugTest: > >>>>> putAll of sorted keys causes deadlock - Fixes #7507. > >>>>>> > >>>>>> > >>>>>> CLOSED WITHOUT FIX: > >>>>>> IGNITE-12775 = 0 > >>>>>> IGNITE-7414 = 0 > >>>>>> IGNITE-10477 = 0 > >>>>>> IGNITE-8625 = 0 > >>>>>> IGNITE-11862 = 0 > >>>>>> IGNITE-10313 = 0 > >>>>>> IGNITE-10011 = 0 > >>>>>> IGNITE-12767 = 0 > >>>>>> > >>>>>> > >>>>>>> 17 апр. 2020 г., в 19:58, Alexey Goncharuk < > >>>> alexey.goncha...@gmail.com> > >>>>> написал(а): > >>>>>>> > >>>>>>> Thanks, I will keep the original ticket in patch available then and > >>>>> leave a > >>>>>>> comment. > >>>>>>> > >>>>>>> Let us know if need any help with moving commits to the release > >>>> branch. > >>>>>>> > >>>>>>> пт, 17 апр. 2020 г. в 18:18, Nikolay Izhikov <nizhi...@apache.org > >: > >>>>>>> > >>>>>>>> Please, don’t cherry pick tickets to 2.8.1 > >>>>>>>> It seems I have to cherry pick many previous tickets for 2.8.1 to > >>>> avoid > >>>>>>>> conflicts. > >>>>>>>> > >>>>>>>>> 17 апр. 2020 г., в 18:01, Alexey Goncharuk < > >>>>> alexey.goncha...@gmail.com> > >>>>>>>> написал(а): > >>>>>>>>> > >>>>>>>>> Nikolay, > >>>>>>>>> > >>>>>>>>> If I merge a ticket that is already targeted for 2.8.1 to > master, do > >>>>> you > >>>>>>>>> prefer this ticket to be cherry-picket to 2.8.1 yourself or > should I > >>>>>>>> merge > >>>>>>>>> it to the release branch? > >>>>>>>>> > >>>>>>>>> пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin <vololo...@gmail.com > >: > >>>>>>>>> > >>>>>>>>>> Great! > >>>>>>>>>> > >>>>>>>>>> Best regards, > >>>>>>>>>> Ivan Pavlukhin > >>>>>>>>>> > >>>>>>>>>> пт, 17 апр. 2020 г. в 12:48, Nikolay Izhikov < > nizhi...@apache.org > >>>>> : > >>>>>>>>>>> > >>>>>>>>>>> OK, let’s try it > >>>>>>>>>>> > >>>>>>>>>>>> I do not know who is a manager for 2.8.1. > >>>>>>>>>>> > >>>>>>>>>>> I am. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> 17 апр. 2020 г., в 12:42, Ivan Pavlukhin <vololo...@gmail.com > > > >>>>>>>>>> написал(а): > >>>>>>>>>>>> > >>>>>>>>>>>>> We didn’t it for the previous releases. > >>>>>>>>>>>>> Why we should start to do it?) > >>>>>>>>>>>> > >>>>>>>>>>>> Because it seems to be a good thing, is not it? I suppose it > is > >>>>>>>>>>>> important to know who is a release manager (the current thread > >>>>> subject > >>>>>>>>>>>> has a "Manager" keyword). E.g. I do not know who is a manager > for > >>>>>>>>>>>> 2.8.1. > >>>>>>>>>>>> > >>>>>>>>>>>> Best regards, > >>>>>>>>>>>> Ivan Pavlukhin > >>>>>>>>>>>> > >>>>>>>>>>>> пт, 17 апр. 2020 г. в 12:27, Nikolay Izhikov < > >>>> nizhi...@apache.org > >>>>>> : > >>>>>>>>>>>>> > >>>>>>>>>>>>> Hello, > >>>>>>>>>>>>> > >>>>>>>>>>>>>> Should not we reflect on the release page [1] who is a > release > >>>>>>>>>> manager? > >>>>>>>>>>>>> > >>>>>>>>>>>>> We didn’t it for the previous releases. > >>>>>>>>>>>>> Why we should start to do it?) > >>>>>>>>>>>>> > >>>>>>>>>>>>>> I suggest to include these fixes into 2.8.1 release: > >>>>>>>>>>>>> > >>>>>>>>>>>>> Thanks, included. > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> 17 апр. 2020 г., в 12:20, Ivan Rakov <ivan.glu...@gmail.com > > > >>>>>>>>>> написал(а): > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Hi, > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I suggest to include these fixes into 2.8.1 release: > >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12101 > >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12651 > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Fri, Apr 17, 2020 at 11:32 AM Ivan Pavlukhin < > >>>>>>>> vololo...@gmail.com> > >>>>>>>>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> 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 > >>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> -- > >>>> Sincerely yours, > >>>> Ivan Bessonov > >>>> > >> > >> > > -- Sincerely yours, Ivan Bessonov
