Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
I fill the ticket with drop problem, plz take a look [1] [1] https://issues.apache.org/jira/browse/IGNITE-14205 >Ilya, > >Thanks! >I've added this step to the Release Process wiki page also [1]. > >[1] >https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < ilya.kasnach...@gmail.com > >wrote: >> >> Hello! >> >> I have added ignite-2.10 to Nightly build triggering. I hope we will have a >> 2.10 nightly tomorrow. Shame that I didn't do it earlier. >> >> https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < mmu...@apache.org >: >> >> > Folks, >> > >> > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm >> > trying to reproduce on a stress-testing environment. >> > [1] >> > >> > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2 >> > >> > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov < mmu...@apache.org > wrote: >> > > >> > > Folks, >> > > >> > > I'm going to cherry-pick these issues to the release branch, any >> > objections? >> > > >> > > >> > > Checkpointer thread holds write lock too long >> > > https://issues.apache.org/jira/browse/IGNITE-14140 >> > > >> > > Incorrect initialize checkpoint-runner-cpu thread pool >> > > https://issues.apache.org/jira/browse/IGNITE-14139 >> > > >> > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov < mmu...@apache.org > >> > > wrote: >> > > > >> > > > Folks, >> > > > >> > > > Do we need any other critical issues from the master branch that need >> > > > to be cherry-picked picked from the master branch? I've marked the >> > > > latest select issues with patching version 2.10. >> > > > >> > > > - benchmarks completed (I'll do another one prior to preparing rc) >> > > > - the release notes merged >> > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover) >> > > > - most of the documentation pages also merged >> > > > >> > > > Hopefully, by Friday the 12th everything will be ready for the >> > > > preparation of a release candidate. >> > > > >> > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов < >> > > > vlasovpavel2...@gmail.com > >> > wrote: >> > > > > >> > > > > Hi everyone, >> > > > > >> > > > > Below are two lists of items representing all the remaining (and >> > completed) >> > > > > documentation tasks for the Ignite 2.10 release. >> > > > > >> > > > > The "*Improvements*" part includes PRs on reworked documentation. >> > > > > The "*Finished*" part includes PRs on newly added documentation. >> > > > > >> > > > > *Improvements:* >> > > > > >> > > > > Documentation for .NET thin client service invocation >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 >> > > > > [2] https://github.com/apache/ignite/pull/8756 >> > > > > >> > > > > Documentation for cache warm-up strategy >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13385 >> > > > > [2] https://github.com/apache/ignite/pull/8703 >> > > > > >> > > > > *Finished:* >> > > > > >> > > > > Document control.(sh|bin) command to get an arbitrary SystemView >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14142 >> > > > > [2] https://github.com/apache/ignite/pull/8775 >> > > > > >> > > > > Document metric for processed keys when rebuilding indexes >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14143 >> > > > > [2] https://github.com/apache/ignite/pull/8776 >> > > > > >> > > > > Document C++ thin client transactions >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14144 >> > > > > [2] https://github.com/apache/ignite/pull/8777 >> > > > > >> > > > > Please don't hesitate to ask me if you have any questions or >> > concerns. >> > > > > >> > > > > With best regards, >> > > > > Nikita >> > > > > >> > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов < >> > vlasovpavel2...@gmail.com >: >> > > > > >> > > > > > Maxim, >> > > > > > >> > > > > > Thank you for being ready to help! >> > > > > > >> > > > > > As I mentioned before, I'm sharing the completed doc items today. >> > > > > > Below is the list of tickets with the prepared PR's: >> > > > > > >> > > > > > *- Documentation: SQL tracing.* >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 >> > > > > > [2] https://github.com/apache/ignite/pull/8762 >> > > > > > >> > > > > > *- Documentation for async API (Thin client Java API)* >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 >> > > > > > [2] https://github.com/apache/ignite/pull/8753 >> > > > > > >> > > > > > *- Documentation for .NET: Thin Client: Service invocation* >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 >> > > > > > [2] https://github.com/apache/ignite/pull/8756 >> > > > > > >> > > > > > *-
[jira] [Created] (IGNITE-14205) 2.10 branch performance drop on IgnitePutRandomValueSizeBenchmark
Stanilovsky Evgeny created IGNITE-14205: --- Summary: 2.10 branch performance drop on IgnitePutRandomValueSizeBenchmark Key: IGNITE-14205 URL: https://issues.apache.org/jira/browse/IGNITE-14205 Project: Ignite Issue Type: Improvement Components: general Reporter: Stanilovsky Evgeny Attachments: 172.25.1.17_logs.zip, 172.25.1.21_logs.zip, 172.25.1.22_logs.zip, image-2021-02-18-08-51-11-371.png Seems we have performance drop with 2.10 branch in compare with 2.9.1. This highlights the IgnitePutRandomValueSizeBenchmark. [^172.25.1.22_logs.zip] [^172.25.1.21_logs.zip] [^172.25.1.17_logs.zip] !image-2021-02-18-08-58-02-196.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Ilya, Thanks! I've added this step to the Release Process wiki page also [1]. [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev wrote: > > Hello! > > I have added ignite-2.10 to Nightly build triggering. I hope we will have a > 2.10 nightly tomorrow. Shame that I didn't do it earlier. > https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds > > Regards, > -- > Ilya Kasnacheev > > > ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov : > > > Folks, > > > > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm > > trying to reproduce on a stress-testing environment. > > [1] > > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2 > > > > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov wrote: > > > > > > Folks, > > > > > > I'm going to cherry-pick these issues to the release branch, any > > objections? > > > > > > > > > Checkpointer thread holds write lock too long > > > https://issues.apache.org/jira/browse/IGNITE-14140 > > > > > > Incorrect initialize checkpoint-runner-cpu thread pool > > > https://issues.apache.org/jira/browse/IGNITE-14139 > > > > > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov wrote: > > > > > > > > Folks, > > > > > > > > Do we need any other critical issues from the master branch that need > > > > to be cherry-picked picked from the master branch? I've marked the > > > > latest select issues with patching version 2.10. > > > > > > > > - benchmarks completed (I'll do another one prior to preparing rc) > > > > - the release notes merged > > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover) > > > > - most of the documentation pages also merged > > > > > > > > Hopefully, by Friday the 12th everything will be ready for the > > > > preparation of a release candidate. > > > > > > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов > > wrote: > > > > > > > > > > Hi everyone, > > > > > > > > > > Below are two lists of items representing all the remaining (and > > completed) > > > > > documentation tasks for the Ignite 2.10 release. > > > > > > > > > > The "*Improvements*" part includes PRs on reworked documentation. > > > > > The "*Finished*" part includes PRs on newly added documentation. > > > > > > > > > > *Improvements:* > > > > > > > > > > Documentation for .NET thin client service invocation > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > > > > > Documentation for cache warm-up strategy > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13385 > > > > > [2] https://github.com/apache/ignite/pull/8703 > > > > > > > > > > *Finished:* > > > > > > > > > > Document control.(sh|bin) command to get an arbitrary SystemView > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14142 > > > > > [2] https://github.com/apache/ignite/pull/8775 > > > > > > > > > > Document metric for processed keys when rebuilding indexes > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14143 > > > > > [2] https://github.com/apache/ignite/pull/8776 > > > > > > > > > > Document C++ thin client transactions > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14144 > > > > > [2] https://github.com/apache/ignite/pull/8777 > > > > > > > > > > Please don't hesitate to ask me if you have any questions or > > concerns. > > > > > > > > > > With best regards, > > > > > Nikita > > > > > > > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов < > > vlasovpavel2...@gmail.com>: > > > > > > > > > > > Maxim, > > > > > > > > > > > > Thank you for being ready to help! > > > > > > > > > > > > As I mentioned before, I'm sharing the completed doc items today. > > > > > > Below is the list of tickets with the prepared PR's: > > > > > > > > > > > > *- Documentation: SQL tracing.* > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 > > > > > > [2] https://github.com/apache/ignite/pull/8762 > > > > > > > > > > > > *- Documentation for async API (Thin client Java API)* > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 > > > > > > [2] https://github.com/apache/ignite/pull/8753 > > > > > > > > > > > > *- Documentation for .NET: Thin Client: Service invocation* > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > > > > > > > *- Document cluster API implementation for CPP* > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133 > > > > > > [2] https://github.com/apache/ignite/pull/8761 > > > > > > > > > > > > > > > > > > I still have some docs to finish/improve. > > > > > > I do believe that I'll provide the rest of the remaining > > documentation by > > > > > > the end of Monday. > > > > > > > > > > > > Regards, > > > > > >
[MTCGA]: new failures in builds [5871876] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testPutAsync https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-67156662371051897=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testPutStoreEnabled https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8474647424964006=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testFailsWithNoRetriesAsync https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5381720597196591559=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testPutAsyncStoreEnabled https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6540229703953098593=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testInvokeAllEvict https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2546688686944517254=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testPut https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3223235346280834532=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testFailsWithNoRetries https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2384319003972043737=%3Cdefault%3E=testDetails *Test with high flaky rate in master IgniteCachePutRetryAtomicSelfTest.testInvokeAll https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4290486693646822367=%3Cdefault%3E=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 21:21:54 17-02-2021
Re: IGNITE-12508
Hello! MTCGA will do that for 90% of tests but you may need to re-run a few suites from its interface. https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/8802/head=Latest Regards, -- Ilya Kasnacheev ср, 17 февр. 2021 г. в 18:29, Atri Sharma : > Thank you! > > Where do I figure out which tests are currently flaky? > > On Wed, Feb 17, 2021 at 8:58 PM Ilya Kasnacheev > wrote: > > > > Hello! > > > > I think these tests are flaky, I have triggered them to re-run. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 17 февр. 2021 г. в 18:19, Atri Sharma : > > > > > Hello, > > > > > > Thanks for helping with this. According to the bot's comment on JIRA, > > > the tests that are failing are: > > > JdbcThinJdbcToCacheDataTypesCoverageTest.testTimeDataType > > > IgnitePdsWithIndexingCoreTestSuite: > > > WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost3 > > > > > > I have verified that these tests pass locally for me (beasted them) > > > and also manually debugged to see if the new method was giving the > > > correct behaviour. > > > > > > Please advice. > > > > > > Atri > > > > > > On Wed, Feb 17, 2021 at 2:37 PM Ilya Kasnacheev > > > wrote: > > > > > > > > Hello! > > > > > > > > Thank you! I have started a MTCGA run since there were not any. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > ср, 17 февр. 2021 г. в 07:49, Atri Sharma : > > > > > > > > > Thank you! I have updated the PR per your comments. > > > > > > > > > > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev > > > > > wrote: > > > > > > > > > > > > Hello! > > > > > > > > > > > > I have left some comments to the PR. > > > > > > > > > > > > Regards, > > > > > > -- > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > пн, 15 февр. 2021 г. в 18:55, Atri Sharma : > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > I have raised a PR for IGNITE-12508: > > > > > > > > > > > > > > https://github.com/apache/ignite/pull/8802 > > > > > > > > > > > > > > Requesting inputs and feedback on the same, please. > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > Atri > > > > > > > > > > > > > > -- > > > > > > > Regards, > > > > > > > > > > > > > > Atri > > > > > > > Apache Concerted > > > > > > > > > > > > > > > > > -- > > > > > Regards, > > > > > > > > > > Atri > > > > > Apache Concerted > > > > > > > > > > > -- > > > Regards, > > > > > > Atri > > > Apache Concerted > > > > > -- > Regards, > > Atri > Apache Concerted >
[jira] [Created] (IGNITE-14203) IEP-54 Live schema for tables. Phase 2
Yury Gerzhedovich created IGNITE-14203: -- Summary: IEP-54 Live schema for tables. Phase 2 Key: IGNITE-14203 URL: https://issues.apache.org/jira/browse/IGNITE-14203 Project: Ignite Issue Type: Improvement Components: sql Reporter: Yury Gerzhedovich -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14202) Provide REST-based server endpoint in order to interact with Ignite cluster via CLI tool
Vyacheslav Koptilin created IGNITE-14202: Summary: Provide REST-based server endpoint in order to interact with Ignite cluster via CLI tool Key: IGNITE-14202 URL: https://issues.apache.org/jira/browse/IGNITE-14202 Project: Ignite Issue Type: New Feature Reporter: Vyacheslav Koptilin Provide REST-based server endpoint in order to interact with Ignite cluster. - need to investigate existing implementations that can be easily used (RESTEasy, CXF, Jersey, etc) - prototype REST API (schema, versioning, etc) - Documentation of API (OpenAPI/Swagger) - integrate with CLI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14201) Calcite Phase 1
Yury Gerzhedovich created IGNITE-14201: -- Summary: Calcite Phase 1 Key: IGNITE-14201 URL: https://issues.apache.org/jira/browse/IGNITE-14201 Project: Ignite Issue Type: Improvement Components: sql Reporter: Yury Gerzhedovich -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: IGNITE-12508
Thank you! Where do I figure out which tests are currently flaky? On Wed, Feb 17, 2021 at 8:58 PM Ilya Kasnacheev wrote: > > Hello! > > I think these tests are flaky, I have triggered them to re-run. > > Regards, > -- > Ilya Kasnacheev > > > ср, 17 февр. 2021 г. в 18:19, Atri Sharma : > > > Hello, > > > > Thanks for helping with this. According to the bot's comment on JIRA, > > the tests that are failing are: > > JdbcThinJdbcToCacheDataTypesCoverageTest.testTimeDataType > > IgnitePdsWithIndexingCoreTestSuite: > > WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost3 > > > > I have verified that these tests pass locally for me (beasted them) > > and also manually debugged to see if the new method was giving the > > correct behaviour. > > > > Please advice. > > > > Atri > > > > On Wed, Feb 17, 2021 at 2:37 PM Ilya Kasnacheev > > wrote: > > > > > > Hello! > > > > > > Thank you! I have started a MTCGA run since there were not any. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > ср, 17 февр. 2021 г. в 07:49, Atri Sharma : > > > > > > > Thank you! I have updated the PR per your comments. > > > > > > > > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev > > > > wrote: > > > > > > > > > > Hello! > > > > > > > > > > I have left some comments to the PR. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > пн, 15 февр. 2021 г. в 18:55, Atri Sharma : > > > > > > > > > > > Hi all, > > > > > > > > > > > > I have raised a PR for IGNITE-12508: > > > > > > > > > > > > https://github.com/apache/ignite/pull/8802 > > > > > > > > > > > > Requesting inputs and feedback on the same, please. > > > > > > > > > > > > Regards, > > > > > > > > > > > > Atri > > > > > > > > > > > > -- > > > > > > Regards, > > > > > > > > > > > > Atri > > > > > > Apache Concerted > > > > > > > > > > > > > > -- > > > > Regards, > > > > > > > > Atri > > > > Apache Concerted > > > > > > > > -- > > Regards, > > > > Atri > > Apache Concerted > > -- Regards, Atri Apache Concerted
Re: IGNITE-12508
Hello! I think these tests are flaky, I have triggered them to re-run. Regards, -- Ilya Kasnacheev ср, 17 февр. 2021 г. в 18:19, Atri Sharma : > Hello, > > Thanks for helping with this. According to the bot's comment on JIRA, > the tests that are failing are: > JdbcThinJdbcToCacheDataTypesCoverageTest.testTimeDataType > IgnitePdsWithIndexingCoreTestSuite: > WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost3 > > I have verified that these tests pass locally for me (beasted them) > and also manually debugged to see if the new method was giving the > correct behaviour. > > Please advice. > > Atri > > On Wed, Feb 17, 2021 at 2:37 PM Ilya Kasnacheev > wrote: > > > > Hello! > > > > Thank you! I have started a MTCGA run since there were not any. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 17 февр. 2021 г. в 07:49, Atri Sharma : > > > > > Thank you! I have updated the PR per your comments. > > > > > > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev > > > wrote: > > > > > > > > Hello! > > > > > > > > I have left some comments to the PR. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > пн, 15 февр. 2021 г. в 18:55, Atri Sharma : > > > > > > > > > Hi all, > > > > > > > > > > I have raised a PR for IGNITE-12508: > > > > > > > > > > https://github.com/apache/ignite/pull/8802 > > > > > > > > > > Requesting inputs and feedback on the same, please. > > > > > > > > > > Regards, > > > > > > > > > > Atri > > > > > > > > > > -- > > > > > Regards, > > > > > > > > > > Atri > > > > > Apache Concerted > > > > > > > > > > > -- > > > Regards, > > > > > > Atri > > > Apache Concerted > > > > > -- > Regards, > > Atri > Apache Concerted >
[jira] [Created] (IGNITE-14200) Ignite Spring Data - IgniteRepositoryFactory swallow cause exception
Adrian created IGNITE-14200:
---
Summary: Ignite Spring Data - IgniteRepositoryFactory swallow
cause exception
Key: IGNITE-14200
URL: https://issues.apache.org/jira/browse/IGNITE-14200
Project: Ignite
Issue Type: Bug
Components: springdata
Affects Versions: 2.9.1
Reporter: Adrian
When using Spring Data with Ignite if an exception occurs we get only:
{code:java}
throw new IgniteException("Failed to initialize Ignite repository factory.
Ignite instance or"
+ " IgniteConfiguration or a path to Ignite's spring XML "
+ "configuration must be defined in the"
+ " application configuration");
}
{code}
So in my example, I got the error when creating IgniteConfigurer and the error
I mentioned was meaningless. I couldn't get what is wrong. So I found that in:
{code:java}
IgniteRepositoryFactory.igniteForRepoConfig{code}
all parent errors are ignored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14199) Prototype a new atomic protocol
Vyacheslav Koptilin created IGNITE-14199: Summary: Prototype a new atomic protocol Key: IGNITE-14199 URL: https://issues.apache.org/jira/browse/IGNITE-14199 Project: Ignite Issue Type: New Feature Reporter: Vyacheslav Koptilin Need to provide a new atomic protocol. This includes the following topics at least: - need to provide a new atomic protocol that uses RAFT client service - need to provide a new minimal API for configuring cache/table in accordance with IEP-54 based -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: IGNITE-12508
Hello, Thanks for helping with this. According to the bot's comment on JIRA, the tests that are failing are: JdbcThinJdbcToCacheDataTypesCoverageTest.testTimeDataType IgnitePdsWithIndexingCoreTestSuite: WalRecoveryTxLogicalRecordsTest.testRecoveryNoPageLost3 I have verified that these tests pass locally for me (beasted them) and also manually debugged to see if the new method was giving the correct behaviour. Please advice. Atri On Wed, Feb 17, 2021 at 2:37 PM Ilya Kasnacheev wrote: > > Hello! > > Thank you! I have started a MTCGA run since there were not any. > > Regards, > -- > Ilya Kasnacheev > > > ср, 17 февр. 2021 г. в 07:49, Atri Sharma : > > > Thank you! I have updated the PR per your comments. > > > > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev > > wrote: > > > > > > Hello! > > > > > > I have left some comments to the PR. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > пн, 15 февр. 2021 г. в 18:55, Atri Sharma : > > > > > > > Hi all, > > > > > > > > I have raised a PR for IGNITE-12508: > > > > > > > > https://github.com/apache/ignite/pull/8802 > > > > > > > > Requesting inputs and feedback on the same, please. > > > > > > > > Regards, > > > > > > > > Atri > > > > > > > > -- > > > > Regards, > > > > > > > > Atri > > > > Apache Concerted > > > > > > > > -- > > Regards, > > > > Atri > > Apache Concerted > > -- Regards, Atri Apache Concerted
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Hello! I have added ignite-2.10 to Nightly build triggering. I hope we will have a 2.10 nightly tomorrow. Shame that I didn't do it earlier. https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10=overview=builds Regards, -- Ilya Kasnacheev ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov : > Folks, > > There is a possible issue with the performance for 2.9.1 vs 2.10. I'm > trying to reproduce on a stress-testing environment. > [1] > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2 > > On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov wrote: > > > > Folks, > > > > I'm going to cherry-pick these issues to the release branch, any > objections? > > > > > > Checkpointer thread holds write lock too long > > https://issues.apache.org/jira/browse/IGNITE-14140 > > > > Incorrect initialize checkpoint-runner-cpu thread pool > > https://issues.apache.org/jira/browse/IGNITE-14139 > > > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov wrote: > > > > > > Folks, > > > > > > Do we need any other critical issues from the master branch that need > > > to be cherry-picked picked from the master branch? I've marked the > > > latest select issues with patching version 2.10. > > > > > > - benchmarks completed (I'll do another one prior to preparing rc) > > > - the release notes merged > > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover) > > > - most of the documentation pages also merged > > > > > > Hopefully, by Friday the 12th everything will be ready for the > > > preparation of a release candidate. > > > > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов > wrote: > > > > > > > > Hi everyone, > > > > > > > > Below are two lists of items representing all the remaining (and > completed) > > > > documentation tasks for the Ignite 2.10 release. > > > > > > > > The "*Improvements*" part includes PRs on reworked documentation. > > > > The "*Finished*" part includes PRs on newly added documentation. > > > > > > > > *Improvements:* > > > > > > > > Documentation for .NET thin client service invocation > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > > > Documentation for cache warm-up strategy > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13385 > > > > [2] https://github.com/apache/ignite/pull/8703 > > > > > > > > *Finished:* > > > > > > > > Document control.(sh|bin) command to get an arbitrary SystemView > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14142 > > > > [2] https://github.com/apache/ignite/pull/8775 > > > > > > > > Document metric for processed keys when rebuilding indexes > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14143 > > > > [2] https://github.com/apache/ignite/pull/8776 > > > > > > > > Document C++ thin client transactions > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14144 > > > > [2] https://github.com/apache/ignite/pull/8777 > > > > > > > > Please don't hesitate to ask me if you have any questions or > concerns. > > > > > > > > With best regards, > > > > Nikita > > > > > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов < > vlasovpavel2...@gmail.com>: > > > > > > > > > Maxim, > > > > > > > > > > Thank you for being ready to help! > > > > > > > > > > As I mentioned before, I'm sharing the completed doc items today. > > > > > Below is the list of tickets with the prepared PR's: > > > > > > > > > > *- Documentation: SQL tracing.* > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 > > > > > [2] https://github.com/apache/ignite/pull/8762 > > > > > > > > > > *- Documentation for async API (Thin client Java API)* > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 > > > > > [2] https://github.com/apache/ignite/pull/8753 > > > > > > > > > > *- Documentation for .NET: Thin Client: Service invocation* > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > > > > > *- Document cluster API implementation for CPP* > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133 > > > > > [2] https://github.com/apache/ignite/pull/8761 > > > > > > > > > > > > > > > I still have some docs to finish/improve. > > > > > I do believe that I'll provide the rest of the remaining > documentation by > > > > > the end of Monday. > > > > > > > > > > Regards, > > > > > Nikita > > > > > > > > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov : > > > > > > > > > >> Nikita, > > > > >> > > > > >> Thank you, I will be waiting for the review. > > > > >> > > > > >> > I'll give the precise estimate tomorrow as I'm still waiting > for some > > > > >> info > > > > >> from the dev side. > > > > >> Let me know if you need any kind of help. > > > > >> > > > > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов < > vlasovpavel2...@gmail.com> > > > > >> wrote: > > > > >> > > > > > >> > Hi
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Folks, There is a possible issue with the performance for 2.9.1 vs 2.10. I'm trying to reproduce on a stress-testing environment. [1] https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jpg?api=v2 On Fri, 12 Feb 2021 at 20:46, Maxim Muzafarov wrote: > > Folks, > > I'm going to cherry-pick these issues to the release branch, any objections? > > > Checkpointer thread holds write lock too long > https://issues.apache.org/jira/browse/IGNITE-14140 > > Incorrect initialize checkpoint-runner-cpu thread pool > https://issues.apache.org/jira/browse/IGNITE-14139 > > On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov wrote: > > > > Folks, > > > > Do we need any other critical issues from the master branch that need > > to be cherry-picked picked from the master branch? I've marked the > > latest select issues with patching version 2.10. > > > > - benchmarks completed (I'll do another one prior to preparing rc) > > - the release notes merged > > - cherry-picked issue (IGNITE-14073 Fixed transactions failover) > > - most of the documentation pages also merged > > > > Hopefully, by Friday the 12th everything will be ready for the > > preparation of a release candidate. > > > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов > > wrote: > > > > > > Hi everyone, > > > > > > Below are two lists of items representing all the remaining (and > > > completed) > > > documentation tasks for the Ignite 2.10 release. > > > > > > The "*Improvements*" part includes PRs on reworked documentation. > > > The "*Finished*" part includes PRs on newly added documentation. > > > > > > *Improvements:* > > > > > > Documentation for .NET thin client service invocation > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > Documentation for cache warm-up strategy > > > [1] https://issues.apache.org/jira/browse/IGNITE-13385 > > > [2] https://github.com/apache/ignite/pull/8703 > > > > > > *Finished:* > > > > > > Document control.(sh|bin) command to get an arbitrary SystemView > > > [1] https://issues.apache.org/jira/browse/IGNITE-14142 > > > [2] https://github.com/apache/ignite/pull/8775 > > > > > > Document metric for processed keys when rebuilding indexes > > > [1] https://issues.apache.org/jira/browse/IGNITE-14143 > > > [2] https://github.com/apache/ignite/pull/8776 > > > > > > Document C++ thin client transactions > > > [1] https://issues.apache.org/jira/browse/IGNITE-14144 > > > [2] https://github.com/apache/ignite/pull/8777 > > > > > > Please don't hesitate to ask me if you have any questions or concerns. > > > > > > With best regards, > > > Nikita > > > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов : > > > > > > > Maxim, > > > > > > > > Thank you for being ready to help! > > > > > > > > As I mentioned before, I'm sharing the completed doc items today. > > > > Below is the list of tickets with the prepared PR's: > > > > > > > > *- Documentation: SQL tracing.* > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 > > > > [2] https://github.com/apache/ignite/pull/8762 > > > > > > > > *- Documentation for async API (Thin client Java API)* > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 > > > > [2] https://github.com/apache/ignite/pull/8753 > > > > > > > > *- Documentation for .NET: Thin Client: Service invocation* > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > > > *- Document cluster API implementation for CPP* > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133 > > > > [2] https://github.com/apache/ignite/pull/8761 > > > > > > > > > > > > I still have some docs to finish/improve. > > > > I do believe that I'll provide the rest of the remaining documentation > > > > by > > > > the end of Monday. > > > > > > > > Regards, > > > > Nikita > > > > > > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov : > > > > > > > >> Nikita, > > > >> > > > >> Thank you, I will be waiting for the review. > > > >> > > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > > > >> info > > > >> from the dev side. > > > >> Let me know if you need any kind of help. > > > >> > > > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов > > > >> wrote: > > > >> > > > > >> > Hi Maxim, > > > >> > > > > >> > I can take a look! > > > >> > > > > >> > Moreover, I'm finishing the work on the remaining documentation > > > >> > tickets. > > > >> > I do believe that I'll be able to provide several PR's tomorrow and > > > >> > complete the rest in a couple of days. > > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > > > >> info > > > >> > from the dev side. > > > >> > > > > >> > Regards, > > > >> > Nikita > > > >> > > > > >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov : > > > >> > > > > >> > > Folks, > > > >> > > > > > >> > > > > > >> > > I've prepared the RELEASE_NOTES. > > > >> > > Would anyone
[jira] [Created] (IGNITE-14198) Define interface for meta storage client
Andrey N. Gura created IGNITE-14198: --- Summary: Define interface for meta storage client Key: IGNITE-14198 URL: https://issues.apache.org/jira/browse/IGNITE-14198 Project: Ignite Issue Type: New Feature Reporter: Andrey N. Gura Assignee: Andrey N. Gura Fix For: 3.0.0-alpha2 Interface for meta storage client should be defined in order to unblock development and unit-testing. Interface implementation is not needed on this stage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [MEETUP] Apache Ignite at Dutch Railways. Join the talk on February 16
The video (and the slides at the same time!): https://youtu.be/wkCW8YC8eKU пн, 15 февр. 2021 г. в 12:51, Kseniya Romanova : > See you tomorrow! Join us 8 AM Pacific Standard Time / 5 PM Central > European Time > > чт, 4 февр. 2021 г. в 17:23, Kseniya Romanova : > >> Hi Igniters! >> >> Here’s the cool case of Ignite in production. Every day, millions of >> people travel by train through the Netherlands—on one of the busiest rail >> infrastructures in Europe. More than 10,000 train movements are performed >> daily. Planning for all these train rides and designing a timetable that >> avoids hazardous situations is a challenge. >> >> Pim Dorrestijn, a solution architect at JDriven, will tell us on February >> 16 how Apache Ignite is used for detecting potential hazardous situations >> in Dutch railway planning. >> >> Check your timezone start time and RSVP here [1] >> >> If you have an Ignite story to share, please contact me or submit the >> talk via the form [2] >> >> [1] https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/276125392/ >> >> [2] >> https://docs.google.com/forms/d/e/1FAIpQLSdiY7movHKvyWg3gOVedHgukJJnNiaejSO_X838vBseL9VmiQ/viewform >> >> -- >> Cheers, >> Kseniya >> >> Devrel at GridGain >> Don't miss upcoming community events, join >> https://www.meetup.com/Apache-Ignite-Virtual-Meetup/ >> >
[jira] [Created] (IGNITE-14197) Checkpoint thread can't take checkpoint write lock because it waits for parked threads to complete their work
Anton Kalashnikov created IGNITE-14197:
--
Summary: Checkpoint thread can't take checkpoint write lock
because it waits for parked threads to complete their work
Key: IGNITE-14197
URL: https://issues.apache.org/jira/browse/IGNITE-14197
Project: Ignite
Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov
In case of enabled write throttling, when, for example, node parks data
streamer thread, it still holds checkpoint read lock and it leads to the long
pauses on waiting for checkpoint lock:
[2020-07-23 07:09:21,614][INFO
][db-checkpoint-thread-#371][GridCacheDatabaseSharedManager] Checkpoint started
[checkpointId=f964c8f2-daa5-41b2-80ef-944326f26f8a, startPtr=FileWALPointer
[idx=56913, fileOff=10362905, len=41972], checkpointBeforeLockTime=1983ms,
*checkpointLockWait=812117ms*, checkpointListenersExecuteTime=90ms,
checkpointLockHoldTime=93ms, walCpRecordFsyncDuration=123ms,
writeCheckpointEntryDuration=4ms, splitAndSortCpPagesDuration=4155ms,
pages=10516815, reason='too big size of WAL without checkpoint']
All operations at this moment are blocked.
Sometimes, it can lead to a complete disaster:
Parking thread=data-streamer-stripe-47-#144 for timeout(ms)=*21278855*
{quote}“data-streamer-stripe-78-#175” #209 prio=5 os_prio=0
tid=0x7f6161d6a800 nid=0xf932 waiting on condition [0x7f5c292d1000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteSpeedBasedThrottle.doPark(PagesWriteSpeedBasedThrottle.java:244)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteSpeedBasedThrottle.onMarkDirty(PagesWriteSpeedBasedThrottle.java:227)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1730)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:491)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:483)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:394)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:369)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:296)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$11300(BPlusTree.java:98)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3864)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7100(BPlusTree.java:3544)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.onNotFound(BPlusTree.java:4103)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$5800(BPlusTree.java:3894)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:2022)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1997)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1904)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1662)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1645)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:2473)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:436)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:4306)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3441)
at
org.apache.ignite.internal.processors.cache.GridCacheEntryEx.initialValue(GridCacheEntryEx.java:770)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2278)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:139)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7104)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:966)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:559)
at
[jira] [Created] (IGNITE-14196) SQL Calcite: prepare examples for documentation
Yury Gerzhedovich created IGNITE-14196: -- Summary: SQL Calcite: prepare examples for documentation Key: IGNITE-14196 URL: https://issues.apache.org/jira/browse/IGNITE-14196 Project: Ignite Issue Type: Task Components: sql Environment: SQL Reporter: Yury Gerzhedovich Seems the first pre-alpha version of the Calcite engine will be released together with the next version of Apache Ignite (2.11). So it required to start preparing documentation. The first step is preparing examples with explanation comments. Let's do it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14195) SQL Calcite: ease of use of new Calcite engine
Yury Gerzhedovich created IGNITE-14195: -- Summary: SQL Calcite: ease of use of new Calcite engine Key: IGNITE-14195 URL: https://issues.apache.org/jira/browse/IGNITE-14195 Project: Ignite Issue Type: Task Components: sql Reporter: Yury Gerzhedovich As of now, we don't have an easy way to use the Calcite engine. The proposal is following, add some 'hint' or preffix for SQL query which will force to use the new engine. For example: /*+ CALCITE_ENGINE */ SELECT * FROM table; -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: IGNITE-12508
Hello! Thank you! I have started a MTCGA run since there were not any. Regards, -- Ilya Kasnacheev ср, 17 февр. 2021 г. в 07:49, Atri Sharma : > Thank you! I have updated the PR per your comments. > > On Tue, Feb 16, 2021 at 9:29 PM Ilya Kasnacheev > wrote: > > > > Hello! > > > > I have left some comments to the PR. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 15 февр. 2021 г. в 18:55, Atri Sharma : > > > > > Hi all, > > > > > > I have raised a PR for IGNITE-12508: > > > > > > https://github.com/apache/ignite/pull/8802 > > > > > > Requesting inputs and feedback on the same, please. > > > > > > Regards, > > > > > > Atri > > > > > > -- > > > Regards, > > > > > > Atri > > > Apache Concerted > > > > > -- > Regards, > > Atri > Apache Concerted >
[jira] [Created] (IGNITE-14194) Multiple storages support for configuration
Ivan Bessonov created IGNITE-14194: -- Summary: Multiple storages support for configuration Key: IGNITE-14194 URL: https://issues.apache.org/jira/browse/IGNITE-14194 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov Currently we have a single hardcoded storage, we should fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
