Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hello. > [2] https://issues.apache.org/jira/browse/IGNITE-15781 Cherry-picked to 2.12. > 19 нояб. 2021 г., в 10:12, Pavel Tupitsyn написал(а): > > I'd like to add this simple fix as well [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-15954 > > On Fri, Nov 19, 2021 at 9:50 AM Maksim Timonin > wrote: > >> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of >> metrics in case there are too many partitions (> 2), we observed >> extensive heap usage. >> >> [1] https://github.com/apache/ignite/pull/9518/files >> [2] https://issues.apache.org/jira/browse/IGNITE-15781 >> >> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin >> wrote: >> >>> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it >>> in 1-2 days. >>> >>> https://issues.apache.org/jira/browse/IGNITE-15943 >>> >>> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov >> wrote: >>> Folks, I've fixed almost all the review comments [1]. Hopefully, the changes will be merged by the end of the week. [1] https://issues.apache.org/jira/browse/IGNITE-14744 On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev wrote: > > Hello, Pavel. > > The code freeze is blocked by two issues discussed above [1] [2]. The > issues are in the final review state and should be merged soon. > > The bugfix is useful and can be cherry-picked, thank you. > > [1] https://issues.apache.org/jira/browse/IGNITE-15530 > [2] https://issues.apache.org/jira/browse/IGNITE-14744 > > > пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn : > >> >> Igniters, >> >> What's the code freeze status? >> Can I cherry-pick a bugfix [1] ? >> >> [1] https://issues.apache.org/jira/browse/IGNITE-15807 >> >> On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky >> wrote: >> >>> Thanks, cherry-picked to master. >>> >>> вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev < >> namelc...@apache.org > : >>> Ivan, Yes, the patch can be cherry-picked. вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky < >> ivanda...@gmail.com > : > > Since code freeze is postponed, may be I can cherry-pick my patch >>> already > merged to master? > https://issues.apache.org/jira/browse/IGNITE-15806 > > пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev < namelc...@apache.org>: > >> Maksim T., Maxim M., Ok. >> >> I think we can move code freeze to +1 week to await these issues. >> >> пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov < mmu...@apache.org>: >>> >>> Folks, >>> >>> I've previously mentioned that I'd like to include the [1] issue in >>> the release. Currently, the status is "Patch Available" >> and it's >>> actively reviewing now. I'd be happy if we wait a couple >> of days >>> and >>> add this improvement to the release. >>> >>> I've also created an issue [2] to remove the ambiguity output >>> message >>> for the snapshot check and idle verify procedures. This is a minor >>> output message change, however, it was directly requested by users. >>> Would you don't mind if we include this issue in the release also? >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-14744 >>> [2] https://issues.apache.org/jira/browse/IGNITE-15849 >>> >>> On Fri, 29 Oct 2021 at 14:19, Maksim Timonin < timonin.ma...@gmail.com> >> wrote: Status update on my issue: IGNITE-15530 [1] is in "Patch Available" state, Anton Vinogradov >> agreed to review this ticket. Also, I'm preparing IndexQuery docs in ticket IGNITE-15745 [2]. >>> I'm >> going to submit a patch with docs today/tomorrow, and want to include them in 2.12 too. [1] https://issues.apache.org/jira/browse/IGNITE-15530 [2] https://issues.apache.org/jira/browse/IGNITE-15745 On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> wrote: > Hello! > > I have prepared a fix for sqlline.sh -e: > https://github.com/apache/ignite/pull/9536 > > If smbd reviews it, we can put it on 2.12. > > Regards, > -- > Ilya Kasnacheev > > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev < namelc...@apache.org>: > >> Maksim, ok. >> >> Ivan, >>
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Maksim, Pavel, +1 to cherry-pick these issues. пт, 19 нояб. 2021 г. в 11:45, Nikolay Izhikov : > > Hello. > > > [2] https://issues.apache.org/jira/browse/IGNITE-15781 > > Cherry-picked to 2.12. > > > 19 нояб. 2021 г., в 10:12, Pavel Tupitsyn написал(а): > > > > I'd like to add this simple fix as well [1] > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15954 > > > > On Fri, Nov 19, 2021 at 9:50 AM Maksim Timonin > > wrote: > > > >> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of > >> metrics in case there are too many partitions (> 2), we observed > >> extensive heap usage. > >> > >> [1] https://github.com/apache/ignite/pull/9518/files > >> [2] https://issues.apache.org/jira/browse/IGNITE-15781 > >> > >> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin > >> wrote: > >> > >>> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it > >>> in 1-2 days. > >>> > >>> https://issues.apache.org/jira/browse/IGNITE-15943 > >>> > >>> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov > >> wrote: > >>> > Folks, > > I've fixed almost all the review comments [1]. Hopefully, the changes > will be merged by the end of the week. > > [1] https://issues.apache.org/jira/browse/IGNITE-14744 > > On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev > wrote: > > > > Hello, Pavel. > > > > The code freeze is blocked by two issues discussed above [1] [2]. The > > issues are in the final review state and should be merged soon. > > > > The bugfix is useful and can be cherry-picked, thank you. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15530 > > [2] https://issues.apache.org/jira/browse/IGNITE-14744 > > > > > > пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn : > > > >> > >> Igniters, > >> > >> What's the code freeze status? > >> Can I cherry-pick a bugfix [1] ? > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-15807 > >> > >> On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky >>> > wrote: > >> > >>> Thanks, cherry-picked to master. > >>> > >>> вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev < > >> namelc...@apache.org > > : > >>> > Ivan, > > Yes, the patch can be cherry-picked. > > вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky < > >> ivanda...@gmail.com > > : > > > > Since code freeze is postponed, may be I can cherry-pick my > patch > >>> already > > merged to master? > > https://issues.apache.org/jira/browse/IGNITE-15806 > > > > пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev < > namelc...@apache.org>: > > > >> Maksim T., Maxim M., Ok. > >> > >> I think we can move code freeze to +1 week to await these > issues. > >> > >> пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov < > mmu...@apache.org>: > >>> > >>> Folks, > >>> > >>> I've previously mentioned that I'd like to include the [1] > issue in > >>> the release. Currently, the status is "Patch Available" > >> and > it's > >>> actively reviewing now. I'd be happy if we wait a couple > >> of > days > >>> and > >>> add this improvement to the release. > >>> > >>> I've also created an issue [2] to remove the ambiguity > output > >>> message > >>> for the snapshot check and idle verify procedures. This is > a minor > >>> output message change, however, it was directly requested > by users. > >>> Would you don't mind if we include this issue in the > release also? > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-14744 > >>> [2] https://issues.apache.org/jira/browse/IGNITE-15849 > >>> > >>> On Fri, 29 Oct 2021 at 14:19, Maksim Timonin < > timonin.ma...@gmail.com> > >> wrote: > > Status update on my issue: > > IGNITE-15530 [1] is in "Patch Available" state, Anton > Vinogradov > >> agreed to > review this ticket. > > Also, I'm preparing IndexQuery docs in ticket > IGNITE-15745 [2]. > >>> I'm > >> going > to submit a patch with docs today/tomorrow, and want to > include > them in > 2.12 too. > > [1] https://issues.apache.org/jira/browse/IGNITE-15530 > [2] https://issues.apache.org/jira/browse/IGNITE-15745 > > On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev < > >> ilya.kasnach...@gmail.com> > wrote: > > > Hello! > > > > I have prepared a fix for sqlline.sh -e: > > https://github.com/apache/ignite/pull/9536 > >>>
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hi all. Let's add simple and useful thin-client-pool monitoring in 2.12: https://issues.apache.org/jira/browse/IGNITE-15183 https://github.com/apache/ignite/pull/9525 19.11.2021 09:50, Maksim Timonin пишет: Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of metrics in case there are too many partitions (> 2), we observed extensive heap usage. [1] https://github.com/apache/ignite/pull/9518/files [2] https://issues.apache.org/jira/browse/IGNITE-15781 On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin wrote: Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it in 1-2 days. https://issues.apache.org/jira/browse/IGNITE-15943 On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov wrote: Folks, I've fixed almost all the review comments [1]. Hopefully, the changes will be merged by the end of the week. [1] https://issues.apache.org/jira/browse/IGNITE-14744 On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev wrote: Hello, Pavel. The code freeze is blocked by two issues discussed above [1] [2]. The issues are in the final review state and should be merged soon. The bugfix is useful and can be cherry-picked, thank you. [1] https://issues.apache.org/jira/browse/IGNITE-15530 [2] https://issues.apache.org/jira/browse/IGNITE-14744 пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn : Igniters, What's the code freeze status? Can I cherry-pick a bugfix [1] ? [1] https://issues.apache.org/jira/browse/IGNITE-15807 On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky wrote: Thanks, cherry-picked to master. вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev : Ivan, Yes, the patch can be cherry-picked. вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky : Since code freeze is postponed, may be I can cherry-pick my patch already merged to master? https://issues.apache.org/jira/browse/IGNITE-15806 пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev < namelc...@apache.org>: Maksim T., Maxim M., Ok. I think we can move code freeze to +1 week to await these issues. пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov < mmu...@apache.org>: Folks, I've previously mentioned that I'd like to include the [1] issue in the release. Currently, the status is "Patch Available" and it's actively reviewing now. I'd be happy if we wait a couple of days and add this improvement to the release. I've also created an issue [2] to remove the ambiguity output message for the snapshot check and idle verify procedures. This is a minor output message change, however, it was directly requested by users. Would you don't mind if we include this issue in the release also? [1] https://issues.apache.org/jira/browse/IGNITE-14744 [2] https://issues.apache.org/jira/browse/IGNITE-15849 On Fri, 29 Oct 2021 at 14:19, Maksim Timonin < timonin.ma...@gmail.com> wrote: Status update on my issue: IGNITE-15530 [1] is in "Patch Available" state, Anton Vinogradov agreed to review this ticket. Also, I'm preparing IndexQuery docs in ticket IGNITE-15745 [2]. I'm going to submit a patch with docs today/tomorrow, and want to include them in 2.12 too. [1] https://issues.apache.org/jira/browse/IGNITE-15530 [2] https://issues.apache.org/jira/browse/IGNITE-15745 On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev < ilya.kasnach...@gmail.com> wrote: Hello! I have prepared a fix for sqlline.sh -e: https://github.com/apache/ignite/pull/9536 If smbd reviews it, we can put it on 2.12. Regards, -- Ilya Kasnacheev чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev < namelc...@apache.org>: Maksim, ok. Ivan, The minor issues can be considered if they will be merged before the code freeze. ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn < ptupit...@apache.org : Ivan, every additional ticket potentially moves the release date further. Also, AFAIK, Igor is on vacation and can't do a review this week. On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky < ivanda...@gmail.com> wrote: Pavel, but what is the problem to include a minor refactoring? Especially before code freeze? ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn < ptupit...@apache.org>: Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we should inflate the scope with this. On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky < ivanda...@gmail.com wrote: Nikita, can we add https://issues.apache.org/jira/browse/IGNITE-15806 this ticket for release? ср, 27 окт. 2021 г. в 13:40, Maksim Timonin < timonin.ma...@gmail.com>: Hi, I'd like to include the ticket in 2.12. There was a performance issue, I spent some time trying to figure it out. I prepared some fixes and I am going to submit a patch this week. I think this issue is critical to include to 2.12 together with basic IndexQuery functionality, because this ticket provides expected behavior of querying indexes - sorted over all nodes results. - IGNITE-15530: IndexQuery has to use MergeSort reducer [1] [1] https://issues.apache.org/jira/brows
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Vladimir, +1. I have cherry-picked the issue. пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir : > > Hi all. > > > Let's add simple and useful thin-client-pool monitoring in 2.12: > > https://issues.apache.org/jira/browse/IGNITE-15183 > > https://github.com/apache/ignite/pull/9525 > > > 19.11.2021 09:50, Maksim Timonin пишет: > > Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of > > metrics in case there are too many partitions (> 2), we observed > > extensive heap usage. > > > > [1] https://github.com/apache/ignite/pull/9518/files > > [2] https://issues.apache.org/jira/browse/IGNITE-15781 > > > > On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin > > wrote: > > > >> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it > >> in 1-2 days. > >> > >> https://issues.apache.org/jira/browse/IGNITE-15943 > >> > >> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov wrote: > >> > >>> Folks, > >>> > >>> I've fixed almost all the review comments [1]. Hopefully, the changes > >>> will be merged by the end of the week. > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-14744 > >>> > >>> On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev > >>> wrote: > Hello, Pavel. > > The code freeze is blocked by two issues discussed above [1] [2]. The > issues are in the final review state and should be merged soon. > > The bugfix is useful and can be cherry-picked, thank you. > > [1] https://issues.apache.org/jira/browse/IGNITE-15530 > [2] https://issues.apache.org/jira/browse/IGNITE-14744 > > > пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn : > > > Igniters, > > > > What's the code freeze status? > > Can I cherry-pick a bugfix [1] ? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15807 > > > > On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky > >>> wrote: > >> Thanks, cherry-picked to master. > >> > >> вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev : > >>> Ivan, > >>> > >>> Yes, the patch can be cherry-picked. > >>> > >>> вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky : > Since code freeze is postponed, may be I can cherry-pick my > >>> patch > >> already > merged to master? > https://issues.apache.org/jira/browse/IGNITE-15806 > > пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev < > >>> namelc...@apache.org>: > > Maksim T., Maxim M., Ok. > > > > I think we can move code freeze to +1 week to await these > >>> issues. > > пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov < > >>> mmu...@apache.org>: > >> Folks, > >> > >> I've previously mentioned that I'd like to include the [1] > >>> issue in > >> the release. Currently, the status is "Patch Available" and > >>> it's > >> actively reviewing now. I'd be happy if we wait a couple of > >>> days > >> and > >> add this improvement to the release. > >> > >> I've also created an issue [2] to remove the ambiguity > >>> output > >> message > >> for the snapshot check and idle verify procedures. This is > >>> a minor > >> output message change, however, it was directly requested > >>> by users. > >> Would you don't mind if we include this issue in the > >>> release also? > >> [1] https://issues.apache.org/jira/browse/IGNITE-14744 > >> [2] https://issues.apache.org/jira/browse/IGNITE-15849 > >> > >> On Fri, 29 Oct 2021 at 14:19, Maksim Timonin < > >>> timonin.ma...@gmail.com> > > wrote: > >>> Status update on my issue: > >>> > >>> IGNITE-15530 [1] is in "Patch Available" state, Anton > >>> Vinogradov > > agreed to > >>> review this ticket. > >>> > >>> Also, I'm preparing IndexQuery docs in ticket > >>> IGNITE-15745 [2]. > >> I'm > > going > >>> to submit a patch with docs today/tomorrow, and want to > >>> include > >>> them in > >>> 2.12 too. > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15530 > >>> [2] https://issues.apache.org/jira/browse/IGNITE-15745 > >>> > >>> On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev < > > ilya.kasnach...@gmail.com> > >>> wrote: > >>> > Hello! > > I have prepared a fix for sqlline.sh -e: > https://github.com/apache/ignite/pull/9536 > > If smbd reviews it, we can put it on 2.12. > > Regards, > -- > Ilya Kasnacheev > > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev < > >>> namelc...@apache.org>: > > Maksim, ok. > > > > Ivan, > > The minor issues can be considered if they will be > >>> m
Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start
Sergey, not so easy to recognize the problem, also with logs, plz fill the
ticket and append link to this message or duplicate all logs there.
thanks !
>From: "Sergey Korotkov" < serge.korot...@gmail.com >
>To: u...@ignite.apache.org
>Cc:
>Subject: [2.11.0]: 'B+Tree is corrupted' exception in
>GridCacheTtlManager.expire() and
>PartitionsEvictManager$PartitionEvictionTask.run() on node start
>Date: Thu, 18 Nov 2021 14:24:59 +0300
>
>Hello,
>
>We have troubles with the CorruptedTreeException: B+Tree is corrupted
>during the node start after cluster restart. Looks like the caches with
>the Expiry Policy configured are source of the problems.
>
>I have attached the log from the problem node. The exact steps with
>timestamps are as folows. Before the deactivation cluster works fine
>about 5 days
>
>2021-11-08 10:54:44 cluster deactivate request
>
>2021-11-08 10:59:33 cluster deactivated
>
>2021-11-08 11:02:30 stop all nodes
>
>2021-11-08 11:02:39 start all nodes
>
>2021-11-08 11:03:14 auto-activation start
>
>2021-11-08 11:03:16 cluster activated
>
>2021-11-08 11:03:21 'B+Tree is corrupted' exception in
>GridCacheTtlManager.expire() on one of the nodes (see the
>10.12.86.29-ignite-2021-11-08.0.log):
>
>[2021-11-08 11:03:21,820][ERROR][ttl-cleanup-worker-#215][ROOT]{}
>Critical system error detected. Will be handled accordingly to
>configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false,
>timeout=0, super=AbstractFailureHandler
>[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
>SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
>[type=CRITICAL_ERROR, err=class
>o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree
>is corrupted [pages(groupId, pageId)=[], msg=Runtime failure on bounds:
>[lower=null, upper=PendingRow []
>org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>B+Tree is corrupted [pages(groupId, pageId)=[], msg=Runtime failure on
>bounds: [lower=null, upper=PendingRow []]]
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:6139)
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1133)
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1100)
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1095)
> at
>org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapManager.java:3076)
> at
>org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.java:3023)
> at
>org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:1255)
> at
>org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:246)
> at
>org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.lambda$body$0(GridCacheSharedTtlCleanupManager.java:193)
> at
>java.util.concurrent.ConcurrentHashMap.computeIfPresent(ConcurrentHashMap.java:1769)
> at
>org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:192)
> at
>org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
>Caused by:
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
>java.lang.IllegalStateException: Item not found: 3
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.findLowerUnbounded(BPlusTree.java:1079)
> at
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:1118)
> ... 11 common frames omitted
>Caused by:
>org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTreeRuntimeException:
>java.lang.IllegalStateException: Item not found: 3
> at
>org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.doInitFromLink(CacheDataRowAdapter.java:345)
> at
>org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:165)
> at
>org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:136)
> at
>org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:123)
> at
>org.apache.ignite.internal.processors.cache.tree.PendingRow.initKey(PendingRow.java:73)
> at
>org.apache.ignite.internal.processors.cache.tree.PendingEntriesTree.g
Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x
Folks, I've prepared the changes related to the legacy Service Grid removal for the 2.13 release. Here is the issue [1] and the PR [2] of these changes. Some important notes: - Removed GridServiceProcessor legacy implementation (internal) - The IGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED system property was removed (this is a breaking change) - The ATTR_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED node attribute was removed (this is a breaking change) - The node with 2.13 won't be able to connect to 2.12 (assume Ignite services are used) The legacy test suite [3] will be removed after the [1] issue will be merged. Who can take a look at this PR? [1] https://issues.apache.org/jira/browse/IGNITE-15758 [2] https://github.com/apache/ignite/pull/9577/files [3] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ServiceGridLegacyMode On Fri, 22 Oct 2021 at 12:43, Nikolay Izhikov wrote: > > Hello. > > In the scope of IEP-80 Breaking changes in Ignite-2.x PR for the following > API are prepared: > > 1. MVCC > - https://issues.apache.org/jira/browse/IGNITE-15757 > - https://github.com/apache/ignite/pull/9516 > > 2. LOCAL caches > - https://issues.apache.org/jira/browse/IGNITE-15756 > - https://github.com/apache/ignite/pull/9515 > > 3. CacheConfiguration#rebalanceDelay > - https://issues.apache.org/jira/browse/IGNITE-15764 > - https://github.com/apache/ignite/pull/9515 > > Please, review. > > > 15 окт. 2021 г., в 16:23, Nikolay Izhikov > > написал(а): > > > > THanks, Maksim. > > > > Tickets included in IEP scope and marked for d&r in 2.12-2.13 > > > >> 15 окт. 2021 г., в 16:03, Maxim Muzafarov написал(а): > >> > >> Let's deprecate RebalanceDelay and RebalanceMode=NONE also. > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-12662 > >> [2] https://issues.apache.org/jira/browse/IGNITE-14613 > >> > >> On Fri, 15 Oct 2021 at 15:46, Anton Vinogradov wrote: > >>> > >>> +1 > >>> > >>> On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev > >>> wrote: > >>> > +1 for deprecation in the 2.12 release > > пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov : > > > > Hello, Igniters. > > > > I’ve prepared IEP-80 [1] to track breaking changes that should be done > in Ignite 2.x. > > > > We agreed on the following algorithm to deal with breaking changes: > > > > - Ignite 2.[x] - deprecate the API + notification of the users. > > - Ignite 2.[x+1] - API removal. > > > > > > I propose to start these improvements with the d&r (depuration & > removal) of the following features: > > > > - LOCAL caches > > - MVCC caches > > - legacy service grid implementation > > - legacy JMX metrics beans. > > > > Deprecation in 2.12 > > Removal in 2.13 > > > > Please, share your opinion. > > > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475 > > > > -- > Best wishes, > Amelchev Nikita > > > >
