[jira] [Created] (IGNITE-14259) Ducktests pre-merge presentation
Anton Vinogradov created IGNITE-14259: - Summary: Ducktests pre-merge presentation Key: IGNITE-14259 URL: https://issues.apache.org/jira/browse/IGNITE-14259 Project: Ignite Issue Type: Bug Reporter: Anton Vinogradov Assignee: Anton Vinogradov A webinar-like presentation is required to discuss what we got before the merge. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCCUSS] Ignite 2.9.2. Index compatibility issue 2.x -> 2.9
Ok, I see, thanks for the answer! On Fri, Feb 26, 2021 at 2:13 PM Ilya Kasnacheev wrote: > Hello! > > I don't think we should fix it in 2.9.2 if the fix will already be > available in 2.10. > > Anyone who sees this bug is welcome to upgrade to 2.10. > > Regards, > -- > Ilya Kasnacheev > > > пт, 26 февр. 2021 г. в 11:32, Max Timonin : > > > Hi, Igniters! > > > > There was a compatibility issue [1] with upgrading an old version of > Ignite > > to 2.9. Inlined JavaObjects just are skipped and then it leads to > undefined > > behavior: > > 1. In best case it just fails with BPlusTreeCorruptedException; > > 2. But in some cases Ignite may *silently* make a wrong decision while > > comparing, then results of queries will be invalid. > > > > Workaround is to rebuild indexes. > > > > For the new release 2.10 this bug was fixed today (commits are [2], [3]). > > > > WDYT, is it worth to backport those commits to the previous Ignite > version? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > [2] > > > > > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228 > > [3] > > > > > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4 > > >
Enable Lucky Orange and Yandex Metrics on Java API docs
Hi devs, Per this ticket: https://issues.apache.org/jira/browse/IGNITE-14215, I have enabled these on the general website and also on the online documentation, but I am stuck with adding these metrics to the templates used for API docs and rebuild them. Could someone please help? Thanks in advance. Mauricio
[jira] [Created] (IGNITE-14260) Replace HomeAway picture with Vrbo
Denis A. Magda created IGNITE-14260: --- Summary: Replace HomeAway picture with Vrbo Key: IGNITE-14260 URL: https://issues.apache.org/jira/browse/IGNITE-14260 Project: Ignite Issue Type: Task Components: website Reporter: Denis A. Magda HomeAway was rebranded to Vrbo. We need to replace the HomeAway logo on the main page with the Vrbo one: https://www.vrbo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14261) Add references to the new documentation metrics pages from the legacy page
Maxim Muzafarov created IGNITE-14261: Summary: Add references to the new documentation metrics pages from the legacy page Key: IGNITE-14261 URL: https://issues.apache.org/jira/browse/IGNITE-14261 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.10 The legacy JMX metrics [1] must have a reference to the new metrics framework which was introduced in the 2.8 release. [1] https://ignite.apache.org/docs/latest/monitoring-metrics/metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Maxim, The issue is fixed and is merged to master now. Best Regards, Igor On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov wrote: > Hello Igor, > > > I believe I could fix the ticket [1] by the end of the next week. > Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > On Fri, 26 Feb 2021 at 11:20, Max Timonin wrote: > > > > Hi, Maxim! > > > > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick > > > > 1. > > > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228 > > 2. > > > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4 > > > > > > https://issues.apache.org/jira/browse/IGNITE-14206 > > > > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov > wrote: > > > > > Anton, > > > > > > Your improvement is very important, for sure, but it's almost 2 months > > > have passed since the initiation of the release branch. I think we > > > should prepare the changes as fast as possible for now and initiate > > > with the next one release. In general, it would be nice to have a > > > release plan for the year ahead so each developer will understand on > > > which release his changes can get into. > > > > > > That's why I'm going to prepare an RC-build on Monday 1-st March. > > > > > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov wrote: > > > > > > > > Maxim, > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13873 > > > > Is ready for review, is it possible to wait for it? > > > > > > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov > > > wrote: > > > > > > > > > Folks, > > > > > > > > > > > > > > > I'd like to cherry-pick to the release branch the following fixes: > > > > > > > > > > Fix security context for JDBC bulk-load operations > > > > > https://issues.apache.org/jira/browse/IGNITE-13472 > > > > > > > > > > Fixed an issue that caused a deadlock when user cache was created > in > > > > > parallel with TTL worker was in progress. > > > > > https://issues.apache.org/jira/browse/IGNITE-14078 > > > > > > > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov > > > wrote: > > > > > > > > > > > > Maxim, Igor, > > > > > > > > > > > > Thanks for sharing details. > > > > > > Let's wait for these fixes. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego > > > wrote: > > > > > > > > > > > > > > Maxim, > > > > > > > > > > > > > > I believe I could fix the ticket [1] by the end of the next > week. > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin < > > > timonin.ma...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > Hi! I've today found an issue [1], there is wrong handling of > > > > > inlined POJO. > > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work > with > > > > > > > > multi-column indexes created on old AI versions that contain > > > inlined > > > > > POJO > > > > > > > > keys in the middle. > > > > > > > > > > > > > > > > I'm working on the fix and asked Konstantin Orlov to review > it. I > > > > > think > > > > > > > > that it will take only a couple of days to fix this issue. > From > > > my > > > > > side, it > > > > > > > > looks like a release blocker, but we've been living with that > > > since > > > > > 2.9.0. > > > > > > > > WDYT if the release can wait for the fix? > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > > > > > > > > > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov < > > > mmu...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > > > > Do we have any estimations of how long does it take to fix > the > > > > > issue > > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure, > > > however, I > > > > > > > > > tend to continue with the release (if fixing the bug > require a > > > few > > > > > > > > > weeks) and prepare a batch of fixes for the 2.10.1. > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > > > There was a ticket filed about the new feature, > transactions > > > in > > > > > C++ > > > > > > > > thin > > > > > > > > > > client, making this feature unusable if there's more > than one > > > > > > > > connection > > > > > > > > > > endpoint: > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204 >
Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
The following commit should be cherry-picked: 0675e2a7e800730c9c8230332b82809754ddae5a Sorry for a delay. Best Regards, Igor On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego wrote: > Maxim, > > The issue is fixed and is merged to master now. > > Best Regards, > Igor > > > On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov wrote: > >> Hello Igor, >> >> > I believe I could fix the ticket [1] by the end of the next week. >> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT? >> >> >> >> [1] https://issues.apache.org/jira/browse/IGNITE-14204 >> >> On Fri, 26 Feb 2021 at 11:20, Max Timonin >> wrote: >> > >> > Hi, Maxim! >> > >> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick >> > >> > 1. >> > >> https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228 >> > 2. >> > >> https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4 >> > >> > >> > https://issues.apache.org/jira/browse/IGNITE-14206 >> > >> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov >> wrote: >> > >> > > Anton, >> > > >> > > Your improvement is very important, for sure, but it's almost 2 months >> > > have passed since the initiation of the release branch. I think we >> > > should prepare the changes as fast as possible for now and initiate >> > > with the next one release. In general, it would be nice to have a >> > > release plan for the year ahead so each developer will understand on >> > > which release his changes can get into. >> > > >> > > That's why I'm going to prepare an RC-build on Monday 1-st March. >> > > >> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov wrote: >> > > > >> > > > Maxim, >> > > > >> > > > https://issues.apache.org/jira/browse/IGNITE-13873 >> > > > Is ready for review, is it possible to wait for it? >> > > > >> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov > > >> > > wrote: >> > > > >> > > > > Folks, >> > > > > >> > > > > >> > > > > I'd like to cherry-pick to the release branch the following fixes: >> > > > > >> > > > > Fix security context for JDBC bulk-load operations >> > > > > https://issues.apache.org/jira/browse/IGNITE-13472 >> > > > > >> > > > > Fixed an issue that caused a deadlock when user cache was created >> in >> > > > > parallel with TTL worker was in progress. >> > > > > https://issues.apache.org/jira/browse/IGNITE-14078 >> > > > > >> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov >> > > wrote: >> > > > > > >> > > > > > Maxim, Igor, >> > > > > > >> > > > > > Thanks for sharing details. >> > > > > > Let's wait for these fixes. >> > > > > > >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 >> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204 >> > > > > > >> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego >> > > wrote: >> > > > > > > >> > > > > > > Maxim, >> > > > > > > >> > > > > > > I believe I could fix the ticket [1] by the end of the next >> week. >> > > > > > > >> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 >> > > > > > > >> > > > > > > Best Regards, >> > > > > > > Igor >> > > > > > > >> > > > > > > >> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin < >> > > timonin.ma...@gmail.com> >> > > > > wrote: >> > > > > > > >> > > > > > > > Hi! I've today found an issue [1], there is wrong handling >> of >> > > > > inlined POJO. >> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work >> with >> > > > > > > > multi-column indexes created on old AI versions that contain >> > > inlined >> > > > > POJO >> > > > > > > > keys in the middle. >> > > > > > > > >> > > > > > > > I'm working on the fix and asked Konstantin Orlov to review >> it. I >> > > > > think >> > > > > > > > that it will take only a couple of days to fix this issue. >> From >> > > my >> > > > > side, it >> > > > > > > > looks like a release blocker, but we've been living with >> that >> > > since >> > > > > 2.9.0. >> > > > > > > > WDYT if the release can wait for the fix? >> > > > > > > > >> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 >> > > > > > > > >> > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov < >> > > mmu...@apache.org> >> > > > > wrote: >> > > > > > > > >> > > > > > > > > Folks, >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > Do we have any estimations of how long does it take to >> fix the >> > > > > issue >> > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure, >> > > however, I >> > > > > > > > > tend to continue with the release (if fixing the bug >> require a >> > > few >> > > > > > > > > weeks) and prepare a batch of fixes for the 2.10.1. >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 >> > > > > > > > > >> > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev < >> > > > > ilya.kasnach...@gmail.com >> > > > > > > > > >> > > > > > > > > wrote: >> > > > > > > > > > >> > > > > > > > > > Hello! >> > > > > >
Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Igor, Many thanks for fixing the issue! I've cherry-picked it to the 2.10 branch. Folks, I'll finalize the latest changes for the documentation pages and prepare the rc build shortly. On Mon, 1 Mar 2021 at 21:08, Igor Sapego wrote: > > The following commit should be cherry-picked: > 0675e2a7e800730c9c8230332b82809754ddae5a > > Sorry for a delay. > > Best Regards, > Igor > > > On Mon, Mar 1, 2021 at 9:06 PM Igor Sapego wrote: >> >> Maxim, >> >> The issue is fixed and is merged to master now. >> >> Best Regards, >> Igor >> >> >> On Sun, Feb 28, 2021 at 8:12 PM Maxim Muzafarov wrote: >>> >>> Hello Igor, >>> >>> > I believe I could fix the ticket [1] by the end of the next week. >>> Should we still wait a bit for t his fix or postpone it to 2.10.1? WDYT? >>> >>> >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-14204 >>> >>> On Fri, 26 Feb 2021 at 11:20, Max Timonin wrote: >>> > >>> > Hi, Maxim! >>> > >>> > The bug IGNITE-14206 [1] fixed. There are 2 commits to cherry-pick >>> > >>> > 1. >>> > https://github.com/apache/ignite/commit/851f650ba03e0b6c081cfe23f411fd2bf6be0228 >>> > 2. >>> > https://github.com/apache/ignite/commit/93b74922bd04b164301d7bc5a2788b9693d4a8a4 >>> > >>> > >>> > https://issues.apache.org/jira/browse/IGNITE-14206 >>> > >>> > On Wed, Feb 24, 2021 at 5:47 PM Maxim Muzafarov wrote: >>> > >>> > > Anton, >>> > > >>> > > Your improvement is very important, for sure, but it's almost 2 months >>> > > have passed since the initiation of the release branch. I think we >>> > > should prepare the changes as fast as possible for now and initiate >>> > > with the next one release. In general, it would be nice to have a >>> > > release plan for the year ahead so each developer will understand on >>> > > which release his changes can get into. >>> > > >>> > > That's why I'm going to prepare an RC-build on Monday 1-st March. >>> > > >>> > > On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov wrote: >>> > > > >>> > > > Maxim, >>> > > > >>> > > > https://issues.apache.org/jira/browse/IGNITE-13873 >>> > > > Is ready for review, is it possible to wait for it? >>> > > > >>> > > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov >>> > > wrote: >>> > > > >>> > > > > Folks, >>> > > > > >>> > > > > >>> > > > > I'd like to cherry-pick to the release branch the following fixes: >>> > > > > >>> > > > > Fix security context for JDBC bulk-load operations >>> > > > > https://issues.apache.org/jira/browse/IGNITE-13472 >>> > > > > >>> > > > > Fixed an issue that caused a deadlock when user cache was created in >>> > > > > parallel with TTL worker was in progress. >>> > > > > https://issues.apache.org/jira/browse/IGNITE-14078 >>> > > > > >>> > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov >>> > > wrote: >>> > > > > > >>> > > > > > Maxim, Igor, >>> > > > > > >>> > > > > > Thanks for sharing details. >>> > > > > > Let's wait for these fixes. >>> > > > > > >>> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 >>> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204 >>> > > > > > >>> > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego >>> > > wrote: >>> > > > > > > >>> > > > > > > Maxim, >>> > > > > > > >>> > > > > > > I believe I could fix the ticket [1] by the end of the next >>> > > > > > > week. >>> > > > > > > >>> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 >>> > > > > > > >>> > > > > > > Best Regards, >>> > > > > > > Igor >>> > > > > > > >>> > > > > > > >>> > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin < >>> > > timonin.ma...@gmail.com> >>> > > > > wrote: >>> > > > > > > >>> > > > > > > > Hi! I've today found an issue [1], there is wrong handling of >>> > > > > inlined POJO. >>> > > > > > > > This bug appeared in 2.9.0 and makes it impossible to work >>> > > > > > > > with >>> > > > > > > > multi-column indexes created on old AI versions that contain >>> > > inlined >>> > > > > POJO >>> > > > > > > > keys in the middle. >>> > > > > > > > >>> > > > > > > > I'm working on the fix and asked Konstantin Orlov to review >>> > > > > > > > it. I >>> > > > > think >>> > > > > > > > that it will take only a couple of days to fix this issue. >>> > > > > > > > From >>> > > my >>> > > > > side, it >>> > > > > > > > looks like a release blocker, but we've been living with that >>> > > since >>> > > > > 2.9.0. >>> > > > > > > > WDYT if the release can wait for the fix? >>> > > > > > > > >>> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 >>> > > > > > > > >>> > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov < >>> > > mmu...@apache.org> >>> > > > > wrote: >>> > > > > > > > >>> > > > > > > > > Folks, >>> > > > > > > > > >>> > > > > > > > > >>> > > > > > > > > Do we have any estimations of how long does it take to fix >>> > > > > > > > > the >>> > > > > issue >>> > > > > > > > > [1] in C++ thin client? The bug must be fixed for sure, >>> > > however, I >>> > > > > > > > > tend to continue with the release (if fixing th
[MTCGA]: new failures in builds [5896176, 5891007] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master Cache (Restarts) 1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E No changes in the build *Test with high flaky rate in master SqlSystemViewsSelfTest.testCachesViews https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=770739345863533708&branch=%3Cdefault%3E&tab=testDetails Changes may lead to failure were done by - maxim muzafarov https://ci.ignite.apache.org/viewModification.html?modId=917740 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 22:44:39 01-03-2021
Re: [jira] [Created] (IGNITE-14208) .NET: Examples multi targeting
Thanks for the tip Pavel
On Thu, Feb 25, 2021 at 10:27 PM Pavel Tupitsyn
wrote:
> Raymond,
>
> You can explicitly reference ConfigurationManager to use the latest Redis
> version:
>
>
> Version="5.0.0" />
>
> This will give you NU1608 warning, but should work.
>
> I've filed a separate ticket
> https://issues.apache.org/jira/browse/IGNITE-14243,
> thanks for the heads up.
>
> Pavel
>
> On Fri, Feb 19, 2021 at 12:45 AM Raymond Wilson <
> raymond_wil...@trimble.com>
> wrote:
>
> > Big +1 for this.
> >
> > On a related note, we just ran into a versioning issue related to the
> .Net
> > Standard 2.0 support in IA. We use .Net Core 3.1 with IA 2.8.1 and wanted
> > to use the StackExchange Redis client. However, the latest client has a
> > dependency on System.Diagnostics.PerformanceCounter 5.0.0, but IA C#
> 2.8.1
> > has a specific dependency for System.Diagnostics.PerformanceCounter <
> > 5.0.0.
> >
> > This means we're having to use a slightly older version of the Redis
> client
> > before they moved to support .Net Core 3.1
> >
> >
> > On Fri, Feb 19, 2021 at 4:55 AM Pavel Tupitsyn (Jira)
> > wrote:
> >
> > > Pavel Tupitsyn created IGNITE-14208:
> > > ---
> > >
> > > Summary: .NET: Examples multi targeting
> > > Key: IGNITE-14208
> > > URL:
> https://issues.apache.org/jira/browse/IGNITE-14208
> > > Project: Ignite
> > > Issue Type: Improvement
> > > Components: platforms
> > > Reporter: Pavel Tupitsyn
> > > Assignee: Pavel Tupitsyn
> > > Fix For: 2.11
> > >
> > >
> > > Currently examples require .NET SDK 2.1, which is quite old. Users are
> > > more likely to have .NET Core 3.1 or .NET 5 installed.
> > >
> > > Fix example projects and replace
> > >
> > > {code}
> > > netcoreapp2.1
> > > {code}
> > >
> > > with
> > >
> > > {code}
> > > netcoreapp2.1;netcoreapp3.1;net5
> > > {code}
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian Jira
> > > (v8.3.4#803005)
> > >
> >
> >
> > --
> >
[MTCGA]: new failures in builds [5896330] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master LongDestroyDurableBackgroundTaskTest.testLongIndexDeletionWithRebalance https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5525392503365591188&branch=%3Cdefault%3E&tab=testDetails No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 06:14:39 02-03-2021
[jira] [Created] (IGNITE-14262) Get rid of numerous ExecutionCancelledException.
Stanilovsky Evgeny created IGNITE-14262: --- Summary: Get rid of numerous ExecutionCancelledException. Key: IGNITE-14262 URL: https://issues.apache.org/jira/browse/IGNITE-14262 Project: Ignite Issue Type: Improvement Components: sql Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny We have numerous ExecutionCancelledException exceptions, for example while calling: CalciteQueryProcessorTest#testCountWithJoin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14263) Failure handler is triggered by NPE on unstable topology
Pavel Vinokurov created IGNITE-14263:
Summary: Failure handler is triggered by NPE on unstable topology
Key: IGNITE-14263
URL: https://issues.apache.org/jira/browse/IGNITE-14263
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Pavel Vinokurov
Attachments: Reproducer.java
Restarting servers and clients produced the following exception:
{code:java}
SEVERE: 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=SYSTEM_WORKER_TERMINATION, err=class
o.a.i.IgniteCheckedException: null]]
class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7759)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:268)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:217)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:168)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3431)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3222)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.ownOrphans(GridDhtPartitionTopologyImpl.java:2075)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.onExchangeDone(GridDhtPartitionTopologyImpl.java:2059)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2535)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:159)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:475)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8.run(GridDhtPartitionsExchangeFuture.java:5119)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initDone(GridDhtPartitionsExchangeFuture.java:5002)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.clientOnlyExchange(GridDhtPartitionsExchangeFuture.java:1592)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:1052)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3403)
... 3 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
