[jira] [Created] (IGNITE-14136) ServicesTest.testServiceTimeout is flaky
Aleksey Plekhanov created IGNITE-14136: -- Summary: ServicesTest.testServiceTimeout is flaky Key: IGNITE-14136 URL: https://issues.apache.org/jira/browse/IGNITE-14136 Project: Ignite Issue Type: Bug Components: thin client Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov The test is flaky because the timeout worker sometimes started after the task with the given sleep time is completed. In this case response with success returned by this task instead of timeout response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Request of TC permissions
Petr, It works. Thank you very much. On 05.02.2021 14:49, Petr Ivanov wrote: Mikhail, Check this build, please [1] This configuration by default is run agains `master` branch of Apache Ignite, but can be overridden in params with any branch you like, including PRs in apache/ignite repository. This is done for ability to test new features in extensions against non-published changes in main project. [1] https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_SpringTransactions/5857868 On 5 Feb 2021, at 12:51, Mikhail Petrov wrote: Hi, Petr. PR with new extension - https://github.com/apache/ignite-extensions/pull/33 On 05.02.2021 12:35, Petr Ivanov wrote: Hi, Mikhail. Is there a PR with you extension, so I can test TC build configuration? On 28 Jan 2021, at 19:03, Petr Ivanov wrote: It seems that we need full set of tests for extensions. I will refactor that project in couple of days and add suite for your extension too. On 28 Jan 2021, at 16:34, Mikhail Petrov wrote: Petr, I planned to copy the existing ignite-extensions build configuration and change its parameters [1] to add a new module and test-suite. It turned out that build configuration parameters can be overridden for each particular build without additional permissions or copying something. Sorry for bothering you. On 28.01.2021 16:17, Petr Ivanov wrote: Hi, Mikhail. Can you please describe what exactly do you what to achieve with the build — I will help with it. Seems that currently we have no test suites for extensions at all [1] https://ci.ignite.apache.org/project/IgniteExtensions_Tests?mode=builds On 28 Jan 2021, at 15:34, Mikhail Petrov wrote: Igniters, I am currently working on the migration of the Spring Transactions integration to a separate ignite-extensions module - [1]. I need to create a debug ignite-extensions build on TC with the migrated test suite included, making sure the new tests are ok. Can anyone help me get the required TC permissions while I work on this issue? Regards, Mikhail. [1] - https://issues.apache.org/jira/browse/IGNITE-13992
Re: Request of TC permissions
Thanks for checking this out, Mikhail. I will add other suites with the same setup later this week. > On 8 Feb 2021, at 11:42, Mikhail Petrov wrote: > > Petr, > > > It works. Thank you very much. > > On 05.02.2021 14:49, Petr Ivanov wrote: >> Mikhail, >> >> >> Check this build, please [1] >> >> This configuration by default is run agains `master` branch of Apache >> Ignite, but can be overridden in params with any branch you like, including >> PRs in apache/ignite repository. >> This is done for ability to test new features in extensions against >> non-published changes in main project. >> >> >> >> [1] >> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_SpringTransactions/5857868 >> >> >> >>> On 5 Feb 2021, at 12:51, Mikhail Petrov wrote: >>> >>> Hi, Petr. >>> >>> PR with new extension - https://github.com/apache/ignite-extensions/pull/33 >>> >>> On 05.02.2021 12:35, Petr Ivanov wrote: Hi, Mikhail. Is there a PR with you extension, so I can test TC build configuration? > On 28 Jan 2021, at 19:03, Petr Ivanov wrote: > > It seems that we need full set of tests for extensions. > > I will refactor that project in couple of days and add suite for your > extension too. > > >> On 28 Jan 2021, at 16:34, Mikhail Petrov wrote: >> >> Petr, I planned to copy the existing ignite-extensions build >> configuration and change its parameters [1] to add a new module and >> test-suite. >> >> It turned out that build configuration parameters can be overridden for >> each particular build without additional permissions or copying >> something. >> >> Sorry for bothering you. >> >> On 28.01.2021 16:17, Petr Ivanov wrote: >>> Hi, Mikhail. >>> >>> >>> Can you please describe what exactly do you what to achieve with the >>> build — I will help with it. >>> >>> Seems that currently we have no test suites for extensions at all [1] >>> >>> >>> >>> https://ci.ignite.apache.org/project/IgniteExtensions_Tests?mode=builds >>> On 28 Jan 2021, at 15:34, Mikhail Petrov wrote: Igniters, I am currently working on the migration of the Spring Transactions integration to a separate ignite-extensions module - [1]. I need to create a debug ignite-extensions build on TC with the migrated test suite included, making sure the new tests are ok. Can anyone help me get the required TC permissions while I work on this issue? Regards, Mikhail. [1] - https://issues.apache.org/jira/browse/IGNITE-13992
Re: Apache Board Report, Feb 10
Hello! In Nov 2020 we have decided that Ignite is a "distributed database": http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html I think it is worth mentioning, and also that Description section needs updating. Regards, -- Ilya Kasnacheev вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov : > Hi Igniters, > > Feb 10 is the due date for submitting the next board report. I would like > to submit it a bit earlier, by the end of the day on Feb 9. > > Here is the first version of the report (at the end of the email). Should > we add here something important? > > What do you think if it worths mentioning/requires board attention: > schema first discussions? IEP-61? Extensions release? Anything related to > the 3.0 development approach? > > Sincerely, > Dmitriy Pavlov > > > ## Description: > The mission of Ignite is the creation and maintenance of software related > to > High-performance, integrated, and distributed In-Memory Database and > Caching > Platform providing in-memory data caching, partitioning, processing, and > querying components. > > ## Issues: > There are no issues requiring board attention > > ## Membership Data: > Apache Ignite was founded 2015-08-19 (5 years ago) > There are currently 56 committers and 35 PMC members in this project. > The Committer-to-PMC ratio is 8:5. > > Community changes, past quarter: > - Alex Plehanov was added to the PMC on 2020-11-18 > - Ivan Bessonov was added as a committer on 2021-01-19 > - Nikita Amelchev was added as a committer on 2021-01-21 > > ## Project Activity: > Development > - Apache Ignite community voted to remove MVCC public API. Test and test > suites on the TeamCity are under discussion. > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very first > build made from standalone branch Ignite 3.0, such releases should help > in > early adoption and testing of 3.0 > - 2.9.1 was released on 2020-12-28 (latest stable) - this release patches > 2.9.0 and mostly contains fixes > - 2.10.0 release is being prepared > > Events and conferences > - Community members and Ignite users continue to run talks at online > meetups > > ## Community Health: > - dev@, user@ list traffic, and code contributions are almost the same as > in the past quarter > - Issues, PRs related activity have increased (from +14% to +49%) >
Re: [DISCUSS] Missed (non-suited) tests
Hello! I have created a TC suite: https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MissingTests?mode=builds + Peter Ivanov Can you please check if everything is alright? BTW, it seems that Inspections [Core] is only in Run All Basic (but not in Run All), and Check Code Style is not triggered by either one. Is it correct? Regards, -- Ilya Kasnacheev пн, 8 февр. 2021 г. в 10:22, Max Timonin : > Hi! > > Yes, now it's a part of the Travis check, and there is already a first > successful build [1]. But I think it's also required to run the check on TC > too, along with jobs for checking licenses, code style, and core > inspections. > > > [1] https://travis-ci.com/github/apache/ignite/builds/216363067 > > On Fri, Feb 5, 2021 at 7:13 PM Ilya Kasnacheev > wrote: > > > Hello! > > > > I have merged it to master! > > > > I wonder what happens next. It will run as a part of travis check? Do we > > also need to add it as a TC suite? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 3 февр. 2021 г. в 18:50, Ilya Kasnacheev >: > > > > > Hello! > > > > > > Code mostly looks good, I have added a minor request. I will check how > it > > > works and then we may commit. > > > > > > + zaleslaw@gmail.com > > > > > > Can you please check whether the new ML suites make sense? > > > math/distances/DistancesTestSuite.java > > > naivebayes/NaiveBayesTestSuite.java > > > > > > Would we need to add them to some TC runs? > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > пн, 25 янв. 2021 г. в 22:07, Max Timonin : > > > > > >> Hi, Ilya! > > >> > > >> I made a fix to the check. Now it aggregates info about tests and > suites > > >> from all modules and then validates it. Could you please review the PR > > >> [1]? > > >> > > >> I tried to move some tests between modules, but unfortunately it still > > >> looks like spaghetti. So I reverted all changes to testsuites (new and > > >> splitted suites) and reworked the check. > > >> > > >> [1] https://github.com/apache/ignite/pull/8367 > > >> > > >> On Mon, Dec 28, 2020 at 2:03 PM Ilya Kasnacheev < > > >> ilya.kasnach...@gmail.com> > > >> wrote: > > >> > > >> > Hello! > > >> > > > >> > You could try to move these tests as .java files between modules in > a > > >> > separate commit. I think I could review it. > > >> > > > >> > Regards, > > >> > -- > > >> > Ilya Kasnacheev > > >> > > > >> > > > >> > пт, 25 дек. 2020 г. в 17:19, Max Timonin : > > >> > > > >> > > Hi! > > >> > > > > >> > > Ilya thanks for the reply! I agree that it's a valid case when a > > test > > >> is > > >> > > part of multiple suites in different modules. But it is > definitely a > > >> bug > > >> > > that the test is written in a module where it can't be run at all > > and > > >> > aimed > > >> > > to run within different modules (core tests in core that require > > h2). > > >> I > > >> > > propose to fix this issue. > > >> > > > > >> > > I'm going to check all such tests and move them to the right > module. > > >> As I > > >> > > can see there are about 100 such test classes, but I hope that > most > > of > > >> > them > > >> > > follow only a few patterns. > > >> > > > > >> > > On Fri, Dec 25, 2020 at 2:58 PM Ivan Daschinsky < > > ivanda...@gmail.com> > > >> > > wrote: > > >> > > > > >> > > > Hi! > > >> > > > >> I'm not sure that we should assume every test is only run > from > > >> one > > >> > > test > > >> > > > suite. One test may be run from different test suites located in > > >> > > different > > >> > > > modules. > > >> > > > Agree. For example, if we introduce this limitation, zk suites > > will > > >> be > > >> > > > broken. > > >> > > > > > >> > > > > > >> > > > пт, 25 дек. 2020 г. в 14:48, Ilya Kasnacheev < > > >> > ilya.kasnach...@gmail.com > > >> > > >: > > >> > > > > > >> > > > > Hello! > > >> > > > > > > >> > > > > Sorry for the long wait. > > >> > > > > > > >> > > > > I'm not sure that we should assume every test is only run from > > one > > >> > test > > >> > > > > suite. One test may be run from different test suites located > in > > >> > > > different > > >> > > > > modules. > > >> > > > > > > >> > > > > I wonder if we can drop this requirement, check all the > modules > > >> > > > > transitively for used/unused tests. > > >> > > > > > > >> > > > > Regards, > > >> > > > > -- > > >> > > > > Ilya Kasnacheev > > >> > > > > > > >> > > > > > > >> > > > > ср, 2 дек. 2020 г. в 18:23, Max Timonin < > > timonin.ma...@gmail.com > > >> >: > > >> > > > > > > >> > > > > > Hi, > > >> > > > > > > > >> > > > > > I don't think so. It looks like a bug that tests fail if one > > >> runs > > >> > > them > > >> > > > > > within their module (actually, what is the goal of this > > test?). > > >> The > > >> > > > check > > >> > > > > > showed us this problem, there is no need to fix the check. > > >> > > > > > > > >> > > > > > Currently I see two ways: > > >> > > > > > 1. Find the right module for every misplaced test. There are > > 104 > > >> > > tests, > > >> > >
Re: Apache Board Report, Feb 10
Hi Ilya, that's a good point. This decision was mentioned in the previous board report, it was in Nov 2020. How description can be changed? Sincerely, Dmitriy Pavlov пн, 8 февр. 2021 г. в 12:26, Ilya Kasnacheev : > Hello! > > In Nov 2020 we have decided that Ignite is a "distributed database": > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html > > I think it is worth mentioning, and also that Description section needs > updating. > > Regards, > -- > Ilya Kasnacheev > > > вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov : > > > Hi Igniters, > > > > Feb 10 is the due date for submitting the next board report. I would like > > to submit it a bit earlier, by the end of the day on Feb 9. > > > > Here is the first version of the report (at the end of the email). Should > > we add here something important? > > > > What do you think if it worths mentioning/requires board attention: > > schema first discussions? IEP-61? Extensions release? Anything related to > > the 3.0 development approach? > > > > Sincerely, > > Dmitriy Pavlov > > > > > > ## Description: > > The mission of Ignite is the creation and maintenance of software related > > to > > High-performance, integrated, and distributed In-Memory Database and > > Caching > > Platform providing in-memory data caching, partitioning, processing, and > > querying components. > > > > ## Issues: > > There are no issues requiring board attention > > > > ## Membership Data: > > Apache Ignite was founded 2015-08-19 (5 years ago) > > There are currently 56 committers and 35 PMC members in this project. > > The Committer-to-PMC ratio is 8:5. > > > > Community changes, past quarter: > > - Alex Plehanov was added to the PMC on 2020-11-18 > > - Ivan Bessonov was added as a committer on 2021-01-19 > > - Nikita Amelchev was added as a committer on 2021-01-21 > > > > ## Project Activity: > > Development > > - Apache Ignite community voted to remove MVCC public API. Test and test > > suites on the TeamCity are under discussion. > > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very first > > build made from standalone branch Ignite 3.0, such releases should help > > in > > early adoption and testing of 3.0 > > - 2.9.1 was released on 2020-12-28 (latest stable) - this release patches > > 2.9.0 and mostly contains fixes > > - 2.10.0 release is being prepared > > > > Events and conferences > > - Community members and Ignite users continue to run talks at online > > meetups > > > > ## Community Health: > > - dev@, user@ list traffic, and code contributions are almost the same > as > > in the past quarter > > - Issues, PRs related activity have increased (from +14% to +49%) > > >
[jira] [Created] (IGNITE-14137) Detect and fix failures reasons (nightly runs fails)
Anton Vinogradov created IGNITE-14137: - Summary: Detect and fix failures reasons (nightly runs fails) Key: IGNITE-14137 URL: https://issues.apache.org/jira/browse/IGNITE-14137 Project: Ignite Issue Type: Bug Reporter: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Board Report, Feb 10
Hello! The mission of Ignite project is the creation and maintenance of software related to high-performance distributed database engine providing in-memory and persistent data caching, partitioning, processing, and querying components. WDYT? Regards, -- Ilya Kasnacheev пн, 8 февр. 2021 г. в 14:14, Dmitriy Pavlov : > Hi Ilya, > > that's a good point. This decision was mentioned in the previous board > report, it was in Nov 2020. > > How description can be changed? > > Sincerely, > Dmitriy Pavlov > > пн, 8 февр. 2021 г. в 12:26, Ilya Kasnacheev : > > > Hello! > > > > In Nov 2020 we have decided that Ignite is a "distributed database": > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html > > > > I think it is worth mentioning, and also that Description section needs > > updating. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov : > > > > > Hi Igniters, > > > > > > Feb 10 is the due date for submitting the next board report. I would > like > > > to submit it a bit earlier, by the end of the day on Feb 9. > > > > > > Here is the first version of the report (at the end of the email). > Should > > > we add here something important? > > > > > > What do you think if it worths mentioning/requires board attention: > > > schema first discussions? IEP-61? Extensions release? Anything related > to > > > the 3.0 development approach? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > > > > ## Description: > > > The mission of Ignite is the creation and maintenance of software > related > > > to > > > High-performance, integrated, and distributed In-Memory Database and > > > Caching > > > Platform providing in-memory data caching, partitioning, processing, > and > > > querying components. > > > > > > ## Issues: > > > There are no issues requiring board attention > > > > > > ## Membership Data: > > > Apache Ignite was founded 2015-08-19 (5 years ago) > > > There are currently 56 committers and 35 PMC members in this project. > > > The Committer-to-PMC ratio is 8:5. > > > > > > Community changes, past quarter: > > > - Alex Plehanov was added to the PMC on 2020-11-18 > > > - Ivan Bessonov was added as a committer on 2021-01-19 > > > - Nikita Amelchev was added as a committer on 2021-01-21 > > > > > > ## Project Activity: > > > Development > > > - Apache Ignite community voted to remove MVCC public API. Test and > test > > > suites on the TeamCity are under discussion. > > > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very > first > > > build made from standalone branch Ignite 3.0, such releases should > help > > > in > > > early adoption and testing of 3.0 > > > - 2.9.1 was released on 2020-12-28 (latest stable) - this release > patches > > > 2.9.0 and mostly contains fixes > > > - 2.10.0 release is being prepared > > > > > > Events and conferences > > > - Community members and Ignite users continue to run talks at online > > > meetups > > > > > > ## Community Health: > > > - dev@, user@ list traffic, and code contributions are almost the same > > as > > > in the past quarter > > > - Issues, PRs related activity have increased (from +14% to +49%) > > > > > >
[jira] [Created] (IGNITE-14138) Historical rebalance kills cluster
Vladislav Pyatkov created IGNITE-14138:
--
Summary: Historical rebalance kills cluster
Key: IGNITE-14138
URL: https://issues.apache.org/jira/browse/IGNITE-14138
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
{noformat}
[2021-01-12T05:11:02,142][ERROR][rebalance-#508%---%][] 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.IgniteCheckedException: Failed to continue supplying [grp=SQL_USAGES_EPE,
demander=48254935-7aa9-4ab5-b398-fdaec334fab7, topVer=AffinityTopologyVersion
[topVer=3, minorTopVer=1
org.apache.ignite.IgniteCheckedException: Failed to continue supplying
[grp=SQL_1, demander=48254935-7aa9-4ab5-b398-fdaec334fab7,
topVer=AffinityTopologyVersion [topVer=3, minorTopVer=1]]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:571)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:398)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:489)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:474)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$800(GridCacheIoManager.java:109)
[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1707)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1721)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4300(GridIoManager.java:157)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:3011)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1662)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4900(GridIoManager.java:157)
[ignite-core.jar]
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1629)
[ignite-core.jar]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: org.apache.ignite.IgniteCheckedException: Could not find start
pointer for partition [part=4, partCntrSince=1115]
at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointHistory.searchEarliestWalPointer(CheckpointHistory.java:557)
~[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.historicalIterator(GridCacheOffheapManager.java:1121)
~[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.rebalanceIterator(IgniteCacheOffheapManagerImpl.java:1195)
~[ignite-core.jar]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:322)
~[ignite-core.jar]
... 16 more
{noformat}
I believe that it should throw IgniteHistoricalIteratorException instead of
IgniteCheckedException, so it can be properly handled and rebalance can move to
the full rebalance instead of killing nodes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Apache Board Report, Feb 10
Ok, I've updated the mission statement. I guess this section is skipped by approvers since it is auto-generated. It should be there for the case when a reader is not familiar with Ignite. Btw, if anyone knows where reporter.a.o takes that data and how to update it, please let me know. пн, 8 февр. 2021 г. в 14:28, Ilya Kasnacheev : > Hello! > > The mission of Ignite project is the creation and maintenance of software > related to high-performance distributed database engine providing in-memory > and persistent data caching, partitioning, processing, and > querying components. > > WDYT? > > Regards, > -- > Ilya Kasnacheev > > > пн, 8 февр. 2021 г. в 14:14, Dmitriy Pavlov : > > > Hi Ilya, > > > > that's a good point. This decision was mentioned in the previous board > > report, it was in Nov 2020. > > > > How description can be changed? > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 8 февр. 2021 г. в 12:26, Ilya Kasnacheev >: > > > > > Hello! > > > > > > In Nov 2020 we have decided that Ignite is a "distributed database": > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Define-Apache-Ignite-as-a-Distributed-Database-td50269.html > > > > > > I think it is worth mentioning, and also that Description section needs > > > updating. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > вс, 7 февр. 2021 г. в 22:52, Dmitriy Pavlov : > > > > > > > Hi Igniters, > > > > > > > > Feb 10 is the due date for submitting the next board report. I would > > like > > > > to submit it a bit earlier, by the end of the day on Feb 9. > > > > > > > > Here is the first version of the report (at the end of the email). > > Should > > > > we add here something important? > > > > > > > > What do you think if it worths mentioning/requires board attention: > > > > schema first discussions? IEP-61? Extensions release? Anything > related > > to > > > > the 3.0 development approach? > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > > > > > ## Description: > > > > The mission of Ignite is the creation and maintenance of software > > related > > > > to > > > > High-performance, integrated, and distributed In-Memory Database and > > > > Caching > > > > Platform providing in-memory data caching, partitioning, processing, > > and > > > > querying components. > > > > > > > > ## Issues: > > > > There are no issues requiring board attention > > > > > > > > ## Membership Data: > > > > Apache Ignite was founded 2015-08-19 (5 years ago) > > > > There are currently 56 committers and 35 PMC members in this project. > > > > The Committer-to-PMC ratio is 8:5. > > > > > > > > Community changes, past quarter: > > > > - Alex Plehanov was added to the PMC on 2020-11-18 > > > > - Ivan Bessonov was added as a committer on 2021-01-19 > > > > - Nikita Amelchev was added as a committer on 2021-01-21 > > > > > > > > ## Project Activity: > > > > Development > > > > - Apache Ignite community voted to remove MVCC public API. Test and > > test > > > > suites on the TeamCity are under discussion. > > > > - 3.0.0-alpha1 was released on 2021-01-11, this release is the very > > first > > > > build made from standalone branch Ignite 3.0, such releases should > > help > > > > in > > > > early adoption and testing of 3.0 > > > > - 2.9.1 was released on 2020-12-28 (latest stable) - this release > > patches > > > > 2.9.0 and mostly contains fixes > > > > - 2.10.0 release is being prepared > > > > > > > > Events and conferences > > > > - Community members and Ignite users continue to run talks at online > > > > meetups > > > > > > > > ## Community Health: > > > > - dev@, user@ list traffic, and code contributions are almost the > same > > > as > > > > in the past quarter > > > > - Issues, PRs related activity have increased (from +14% to +49%) > > > > > > > > > >
[jira] [Created] (IGNITE-14139) Incorrect initialize checkpoint-runner-cpu thread pool
Vladislav Pyatkov created IGNITE-14139:
--
Summary: Incorrect initialize checkpoint-runner-cpu thread pool
Key: IGNITE-14139
URL: https://issues.apache.org/jira/browse/IGNITE-14139
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
Assignee: Vladislav Pyatkov
First initialization of checkpoint thread pool for CPU is incorrect.
Look at the constructor of {{CheckpointWorkflow}}:
At start, we initialize the pool:
{code:java}
this.checkpointCollectPagesInfoPool = initializeCheckpointPool();
{code}
and only after, we set a size of the pool:
{code:java}
this.checkpointCollectInfoThreads = checkpointCollectInfoThreads;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14140) Checkpointer thread holds write lock too long
Vladislav Pyatkov created IGNITE-14140:
--
Summary: Checkpointer thread holds write lock too long
Key: IGNITE-14140
URL: https://issues.apache.org/jira/browse/IGNITE-14140
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Vladislav Pyatkov
Assignee: Vladislav Pyatkov
Free lists flushing optimization can block db-checkpoint-thread when it got
Write lock. It might block all transactions for several hundreds milliseconds.
{noformat}
"db-checkpoint-thread-#334%DPL_GRID%DplGridNodeName%" #667 daemon prio=5
os_prio=0 tid=0x7e765c123800 nid=0xee0b8 runnable [0x7e767f535000]
java.lang.Thread.State: RUNNABLE at sun.misc.Unsafe.getObjectVolatile(Native
Method) at
java.util.concurrent.atomic.AtomicReferenceArray.getRaw(AtomicReferenceArray.java:130)
at
java.util.concurrent.atomic.AtomicReferenceArray.get(AtomicReferenceArray.java:125)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.getBucketCache(AbstractFreeList.java:690)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.flushBucketsCache(PagesList.java:374)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:343)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:373)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.syncMetadata(GridCacheOffheapManager.java:336)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.syncMetadata(GridCacheOffheapManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onMarkCheckpointBegin(GridCacheOffheapManager.java:247)
at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.CheckpointWorkflow.markCheckpointBegin(CheckpointWorkflow.java:281)
at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.doCheckpoint(Checkpointer.java:388)
at
org.apache.ignite.internal.processors.cache.persistence.checkpoint.Checkpointer.body(Checkpointer.java:264)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
{noformat}
We can to reduce time into Write lock if switch off optimization before the
lock will be gotten and enable it after the lock will be left off.
This image confirms that all time consume of storing the metadata cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Disable MVCC test suites
+ 2021-02-06 0:50 GMT+03:00, Maxim Muzafarov : > Folks, > > Since the vote of removing MVCC API [1] completes successfully can we > disable the MVCC suites? > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Removing-MVCC-public-API-tp50705.html > > On Mon, 7 Dec 2020 at 09:38, Ivan Pavlukhin wrote: >> >> Hi Igniters, >> >> > The feature is not production-ready, and I don't think it is used at >> > all. >> >> Unfortunately, we cannot be sure that the feature is not used at all. >> I recall some threads on user list about it. >> >> I understand concerns of those who want to get rid of MVCC. And the >> feature seems to be abandoned today and only increases development >> complexity. So, I think that cleaning up MVCC code is a good idea if >> there is no benefit for the developer community to maintain it today. >> But I suppose such decision should be properly communicated with the >> user community. >> >> 2020-12-02 18:31 GMT+03:00, Alex Plehanov : >> > -1 for disabling test without removing the code. Current tests give us >> > at >> > least "something works" status for the feature available to users, >> > without >> > these tests, we can smoothly move to "totally unusable" status. >> > Complete removal of MVCC can be resource-consuming, but if we want to >> > disable tests at least we should hide the public MVCC API or totally >> > prohibit MVCC usage. Also, it can't be done in 2.x release due to >> > backward >> > compatibility. >> > >> > ср, 2 дек. 2020 г. в 17:28, Nikolay Izhikov : >> > >> >> > Yes, it can be done. However, I don't think that we will get an >> >> agreement on that >> >> >> >> Let’s give it a try and see what happens :) >> >> >> >> >> >> > 2 дек. 2020 г., в 17:23, Вячеслав Коптилин >> >> > >> >> написал(а): >> >> > >> >> >> Can you start the vote? >> >> > Yes, it can be done. However, I don't think that we will get an >> >> > agreement >> >> > on that (I just recall the previous discussion). >> >> > And so, we will not remove the MVCC code; on the other hand, nobody >> >> > will >> >> > support it in the future. We already at this point. This is just my >> >> humble >> >> > opinion. >> >> > >> >> >> It's strange turning off here the whole MVCC tests just because >> >> something >> >> > in the master branch was broken when in the second thread >> >> > On one side, it looks weird, I agree. On the other hand, nobody >> >> > cares >> >> about >> >> > that and wants to fix tests. This is a stalemate, I think. >> >> > >> >> > Thanks, >> >> > S. >> >> > >> >> > ср, 2 дек. 2020 г. в 16:47, Maxim Muzafarov : >> >> > >> >> >> Slava, >> >> >> >> >> >> Can you start the vote? >> >> >> >> >> >> It's strange turning off here the whole MVCC tests just because >> >> >> something in the master branch was broken when in the second thread >> >> >> Community decide to continue MVCC support. Let's start the vote and >> >> >> see what happens. >> >> >> >> >> >> On Wed, 2 Dec 2020 at 16:39, Вячеслав Коптилин < >> >> slava.kopti...@gmail.com> >> >> >> wrote: >> >> >>> >> >> It will be even worse if our users will face NPE or things like >> >> that >> >> >> in >> >> >>> the basic MVCC scenarios just because we don’t tests it. >> >> >>> The feature is not production-ready, and I don't think it is used >> >> >>> at >> >> all. >> >> >>> Moreover, MVCC Cache 7, 8, 8, MVCC PDS 1, 2, 4 are already broken >> >> >>> (execution timeouts, flaky test, etc) and I haven't seen anyone >> >> >>> who >> >> would >> >> >>> like to fix this. >> >> >>> Why should we waste every contributor's time? IMHO, MVCC suites >> >> >>> are >> >> >> useless >> >> >>> and everyone just pushes "re-run possible blockers" button and >> >> >>> doesn't >> >> >> care >> >> >>> about MVCC tests at all. >> >> >>> >> >> >>> Thanks, >> >> >>> S. >> >> >>> >> >> >>> ср, 2 дек. 2020 г. в 16:01, Nikolay Izhikov : >> >> >>> >> >> > I think test suites can be disabled even today >> >> >> >> I’m -1 to disable tests without complete removal. >> >> It will be even worse if our users will face NPE or things like >> >> that >> >> in >> >> the basic MVCC scenarios just because we don’t tests it. >> >> >> >> >> >> > 2 дек. 2020 г., в 15:50, Вячеслав Коптилин >> >> > > >> >>> >> >> написал(а): >> >> > >> >> > Hi Nikolay, >> >> > >> >> >> Why do we need feature in the project that not even tested >> >> >> regularly? >> >> > Fair enough. However, I am not an expert in this area (MVCC and >> >> >> SQL), so >> >> I >> >> > cannot say how much effort it will take. >> >> > I would say that the opinion of the rest of the community is >> >> > needed >> >> >> here. >> >> > >> >> > Anyway, I think test suites can be disabled even today, while >> >> > the >> >> >> fate of >> >> > the MVCC feature can be (and should be) discussed separately. >> >> > What do you think? >> >> > >> >> > Thanks, >> >> > S. >> >> > >> >> >>
[jira] [Created] (IGNITE-14141) Remove unnecessary storage configuration from PageStore
Maxim Muzafarov created IGNITE-14141:
Summary: Remove unnecessary storage configuration from PageStore
Key: IGNITE-14141
URL: https://issues.apache.org/jira/browse/IGNITE-14141
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
The {{DataStorageConfiguration}} is used only for getting the {{pageSize}} in
the {{FilePageStore}} implementation and can be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[MTCGA]: new failures in builds [5861882] 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-nightly GridCacheDhtPreloadWaitForBackupsWithPersistenceTest.testThatExcludedNodeListWithinMetastoreCleanedUpAfterUpdatingFullMap https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-1068404371517622637&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 01:59:49 09-02-2021
[jira] [Created] (IGNITE-14142) Document control.(sh|bin) command to get an arbitrary SystemView
Nikita Safonov created IGNITE-14142: --- Summary: Document control.(sh|bin) command to get an arbitrary SystemView Key: IGNITE-14142 URL: https://issues.apache.org/jira/browse/IGNITE-14142 Project: Ignite Issue Type: Sub-task Components: documentation Affects Versions: 2.10 Reporter: Nikita Safonov Assignee: Nikita Safonov We need to document the new "get an arbitrary SystemView" control.(sh|bin) command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14143) Document metric for processed keys when rebuilding indexes.
Nikita Safonov created IGNITE-14143: --- Summary: Document metric for processed keys when rebuilding indexes. Key: IGNITE-14143 URL: https://issues.apache.org/jira/browse/IGNITE-14143 Project: Ignite Issue Type: Sub-task Components: documentation Affects Versions: 2.10 Reporter: Nikita Safonov Assignee: Nikita Safonov We need to document a new metric for processed keys when rebuilding indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14144) Document C++ thin client transactions
Nikita Safonov created IGNITE-14144: --- Summary: Document C++ thin client transactions Key: IGNITE-14144 URL: https://issues.apache.org/jira/browse/IGNITE-14144 Project: Ignite Issue Type: Sub-task Components: documentation Affects Versions: 2.10 Reporter: Nikita Safonov Assignee: Nikita Safonov We need to document the C++ thin client transactions functionality. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
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 take a look at the PR [2] [1]? >> > > >> > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069 >> > > [2] https://github.com/apache/ignite/pull/8748/files >> > > >> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov >> wrote: >> > > > >> > > > Folks, >> > > > >> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1]. >> > > > Everything looks good at the first glance. >> > > > >> > > > >> > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Benchmarks(2.9.1vs2.10) >> > > > >> > > > On Fri, 29 Jan 2021 at 18:32, Никита Сафонов < >> vlasovpavel2...@gmail.com> >> > > wrote: >> > > > > >> > > > > Hi Maxim, >> > > > > >> > > > > terrific! >> > > > > >> > > > > Then, I'll continue with the tasks on the list. >> > > > > >> > > > > Thank you, >> > > > > Nikita >> > > > > >> > > > > чт, 28 янв. 2021 г. в 22:44, Maxim Muzafarov : >> > > > > >> > > > > > Hello Nikita, >> > > > > > >> > > > > > Thank you for sharing the state. >> > > > > > >> > > > > > I think we can move on to the next stages of the release. There >> are a >> > > > > > few important steps left to do: release_notes, stress testing. >> This >> > > > > > may take some time, so we still have time to complete the rest >> of the >> > > > > > documentation tasks. >> > > > > > >> > > > > > On Thu, 28 Jan 2021 at 02:51, Никита Сафонов < >> > > vlasovpavel2...@gmail.com> >> > > > > > wrote: >> > > > > > > >> > > > > > > Hi Maxim et al, >> > > > > > > >> > > > > > > thank you! >> > > > > > > >> > > > > > > The rest of the documentation tasks for important features >> are also >> > > > > > > completed. >> > > > > > > >> > > > > > > Nevertheless, there are still some items (the ones on my list >> that >> > > do not >> > > > > > > have any doc tasks) that can be done for the 2.10 release. >> > > > > > > If you want them to be included, I will try to provide patches >> > > ASAP. If >> > > > > > > not, I
