[jira] [Commented] (IGNITE-8911) While cache is restarting it's possible to start new cache with this name
[ https://issues.apache.org/jira/browse/IGNITE-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730706#comment-16730706 ] ASF GitHub Bot commented on IGNITE-8911: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5717 > While cache is restarting it's possible to start new cache with this name > - > > Key: IGNITE-8911 > URL: https://issues.apache.org/jira/browse/IGNITE-8911 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.8 > > > We have the state "restarting" for caches when we certainly now that these > caches would start at some moment in future. But we could start new cache > with the same name. > Plus, NPE is throwing when we try to get proxy for such caches (in > "restarting" state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10307) SQL: Extract partition info from JOINs
[ https://issues.apache.org/jira/browse/IGNITE-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730683#comment-16730683 ] ASF GitHub Bot commented on IGNITE-10307: - GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5774 IGNITE-10307 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10307 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5774.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5774 commit 967a4b3d5237ebd1e3d72af497a7d8e8bb8cb129 Author: devozerov Date: 2018-12-10T12:25:27Z Experimenting. commit 1420cf54e81b6450b7fa5929d96f75093b9652e9 Author: devozerov Date: 2018-12-11T12:18:51Z Initial modelling. commit bffb5888ec7cf99d52b0319cd887b4d03ccafde8 Author: devozerov Date: 2018-12-11T13:36:44Z WIP. commit 6d51a1813539f5a030ae97f1340e363ecf944ba9 Author: devozerov Date: 2018-12-11T13:37:16Z Merge branch 'master' into prune-joins commit a510d5efdb1a87014359ed71d72300b7d01c6781 Author: devozerov Date: 2018-12-11T13:39:45Z Merge branch 'query-rewrite' into prune-joins commit 0b016d2054364d0fc254fbe6f9390851339610bc Author: devozerov Date: 2018-12-11T15:03:10Z WIP. commit dfcf0fff4c8e1818203cddf124d9a3fd04f4 Author: devozerov Date: 2018-12-12T09:50:59Z Merge branch 'master' into ignite-10307 commit ddb32af91b3eb9dfa9b3d1e12f270c7f2313d98a Author: devozerov Date: 2018-12-12T13:09:21Z Merge branch 'master' into ignite-10307 commit e4f769a4f43da05123ca6ad1ca003a64dbb10ace Author: devozerov Date: 2018-12-18T08:11:21Z Merge branch 'master' into ignite-10307 # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/affinity/PartitionExtractor.java commit e78ed0c5ce24220874bed476d5613da1057f077f Author: devozerov Date: 2018-12-18T08:12:12Z Merged with master. commit 456f3440ab3de251ff912533f6c3f1734d392b64 Author: devozerov Date: 2018-12-18T09:06:46Z Implemented strict and non-strict partition extraction logic. commit ca318d4e6f28fa121705fc8289e263a3a5ac2472 Author: devozerov Date: 2018-12-18T09:16:33Z Affinity column name resolution for model. commit 2fa20fb1c876ecfaf6059ffd292a912db5c69b71 Author: devozerov Date: 2018-12-18T10:30:17Z Affinity descriptor. commit e1ccb5af84f938f9f609724a7c7131f0a2f24e77 Author: devozerov Date: 2018-12-18T12:02:29Z Join model for single table. commit 0945c74fe71bea5cefb8678fce1ee2b59c575250 Author: devozerov Date: 2018-12-18T12:39:40Z WIP. commit 6b630f25bda2a1e1c6317a65a73d3666d7d15476 Author: devozerov Date: 2018-12-18T14:55:26Z WIP. commit 5a2c38b69e832ebf4175a36c6b7c5af9d97c5ddf Author: devozerov Date: 2018-12-20T05:00:52Z Merge branch 'master' into ignite-10307 commit babf609f0c2f0205fca83a0abe79dc2385b30782 Author: devozerov Date: 2018-12-20T05:26:07Z Table model class. commit 608ae1b6f75cae8ed8402c6e0c1755d3b3abf573 Author: devozerov Date: 2018-12-20T06:03:04Z Preparing table model. commit 6e40856de0dd4124b6b6a04395df901ebaa96fba Author: devozerov Date: 2018-12-20T09:06:46Z WIP. commit 04a5f5eaabda51ba53f6495090709a945b532a33 Author: devozerov Date: 2018-12-20T09:08:26Z WIP. commit 276b4afd153307a7940ef4947fd7eb0aa2ed1914 Author: devozerov Date: 2018-12-20T16:31:37Z Recursive disjunction. commit 0172b894dd6e16b66fce1ea74149a4b4a35b57e5 Author: devozerov Date: 2018-12-20T16:36:37Z Pass table model recursively. commit 7a4ce2b9b21c6fafd40eac1805ee39cca8f3d5b3 Author: devozerov Date: 2018-12-20T16:44:52Z Add join conditions to the model. commit 24ea3232c44cf6f733fd8e9574203028b0400c32 Author: devozerov Date: 2018-12-20T17:47:40Z Added join groups to nodes. commit 9f489363aad5118bdcc53cbae924fba27f300139 Author: devozerov Date: 2018-12-20T17:50:03Z Minors. commit c5b7a5c8ee2ec7c637e9d929f70e07c260f70c72 Author: devozerov Date: 2018-12-20T18:02:28Z Group processing. commit 3571bdb03f4492f762f32fd26298976f4f2b8a89 Author: devozerov Date: 2018-12-20T18:10:43Z Removed table descriptor. commit afff3fdfdf95687f243d3984a3d0df85906b2350 Author: devozerov Date: 2018-12-20T18:11:34Z Removing unnecessary code. commit bb2287dd5a0c4e0adbd1838470759572015a6e57 Author: devozerov Date: 2018-12-20T18:14:06Z Removing unnecessary code (PartitionResult). > SQL: Extract partition info from JOINs > -- > > Key: IGNITE-10307 > URL: https://issues.apache.org/jira/browse/IGNITE-10307 > Project: Ignite >
[jira] [Commented] (IGNITE-2) Need to implement Queries using QueryPredicate API
[ https://issues.apache.org/jira/browse/IGNITE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730671#comment-16730671 ] ASF GitHub Bot commented on IGNITE-2: - GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/5773 IGNITE-2.4.14.b1 Created for testing. **Do not merge!** You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.14.b1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5773.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5773 commit 8b21e0b36d7d035ff52bcff067f002140f4b8b97 Author: Alexey Kuznetsov Date: 2018-03-23T10:53:15Z IGNITE-7119 Web Agent: Implemented support for comma-separated list of node URIs. (cherry picked from commit ee0f4c0) commit a9f63143059fc489342cadc0c89d7d8fd389fdff Author: Denis Mekhanikov Date: 2018-04-20T14:11:36Z ignite-8205 Clear list of local services in GridServiceProcessor#onKernalStop Signed-off-by: Andrey Gura (cherry picked from commit fbe24f8e3b0d9016a69670ca2bc50766865adf38) commit 2aa4d60df18e57f28814675cf37298ba952035b7 Author: Denis Mekhanikov Date: 2018-04-20T15:41:06Z IGNITE-8134 Subscribe to system cache events on nodes outside BLT Signed-off-by: Andrey Gura (cherry picked from commit c82277eb4e48f95dfec8cb0206c019820a765432) commit ef140ce1102c37295fe9c52d4fcc52b7bdd2bb09 Author: Alexey Kuznetsov Date: 2018-04-23T08:44:09Z IGNITE-8298 Web Console: Fixed tables UI issues. commit 561950f4afc37a078eefc54664f56bdff6d2dcfd Author: Anton Kurbanov Date: 2018-04-21T18:23:21Z IGNITE-8154 - Add an ability to provide ExceptionListener to JmsStreamer - Fixes #3828 Signed-off-by: Valentin Kulichenko commit 1dbd6970fd2ce611c0cbbfa9256b08a934fc8666 Author: Anton Kurbanov Date: 2018-04-23T09:24:50Z Merge branch 'ignite-2.4-master' of https://github.com/gridgain/apache-ignite into ignite-2.4-master commit cafbff336761c5464cb60b68b0f7193d5c998d9f Author: Andrey V. Mashenkov Date: 2018-04-16T17:43:36Z IGNITE-7972 Fixed NPE in TTL manager on unwindEvicts. - Fixes #3810. Signed-off-by: dpavlov (cherry picked from commit 737933e) commit 16fa0132be0cce8e2af2566fd7ad06a741b5fee0 Author: Andrey V. Mashenkov Date: 2018-02-07T15:25:25Z IGNITE-7508: Fix contention on system property access in GridKernalContextImpl::isDaemon(). This closes #3468. (cherry picked from commit d2b41a0) commit 996e3f5b39746777eecad73bc303838fe76121c2 Author: tledkov-gridgain Date: 2018-04-23T15:20:21Z IGNITE-8355 Fixed NPE on concurrent nodes start - Fixes #3899. Signed-off-by: Alexey Goncharuk (cherry picked from commit 5a981c9) commit b9bcc8d6bbcbe3d78e171d55ebedb14d21b28c26 Author: tledkov-gridgain Date: 2018-04-23T15:20:21Z IGNITE-8355 Fixed NPE on concurrent nodes start - Fixes #3899. Signed-off-by: Alexey Goncharuk (cherry picked from commit 5a981c9) commit d253282c6c1976f2279b2a7b4e887fbd46ef3e3a Author: Alexey Goncharuk Date: 2018-04-23T16:39:01Z IGNITE-6083 Null value may be passed to the entry processor on existing key commit d85c922f6c3bd11f3bd192af6ac5ce10d14534c5 Author: Ivan Daschinskiy Date: 2018-04-23T17:37:09Z IGNITE-7786 Added ping timeout and ping interval to control.sh Signed-off-by: Andrey Gura (cherry picked from commit eadc591) commit 2d268ce0c24e7e10cf8e6f41757496129e3aa0d3 Author: Stanislav Lukyanov Date: 2018-04-24T13:29:04Z Merge branch 'ignite-2.4.4' into ignite-2.4-master # Conflicts: # modules/core/src/test/java/org/apache/ignite/util/GridCommandHandlerTest.java commit 568c8718fd3f02392936bbd35b2730996942ad56 Author: Pavel Kovalenko Date: 2018-04-24T16:06:37Z IGNITE-8313 Add trace logs on exchange phases and affinity calculation. - Fixes #3881. Signed-off-by: dpavlov (cherry picked from commit f4646e44fe347711801ba48f318b00337a8a2780) commit 92d10bc9eb58f3018f5d095c17a4ffb8f5201d19 Author: Andrey V. Mashenkov Date: 2017-12-18T15:06:44Z Sanity test suite added. (cherry picked from commit 57202b7) commit 053fc7cdebdc62b735bffb7e294d2d89e04bfe94 Author: Igor Sapego Date: 2018-04-26T16:36:25Z IGNITE-8394: ODBC: Fixed async establishing of SSL connection (cherry picked from commit 1840f75) commit c1251849e2423056eac330749536401894f0b594 Author: Alexey Goncharuk Date: 2018-04-26T16:38:03Z IGNITE-8404 Fixed NPE in MappedFileMemoryProvider commit f9c7f02404e68fa92815e00869908dceca0e1938 Author: Evgeny Stanilovskiy Date: 2018-04-17T15:03:13Z GG-13718: Error
[jira] [Commented] (IGNITE-5438) JDBC thin: support query timeout
[ https://issues.apache.org/jira/browse/IGNITE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730664#comment-16730664 ] ASF GitHub Bot commented on IGNITE-5438: GitHub user sanpwc opened a pull request: https://github.com/apache/ignite/pull/5772 IGNITE-5438 JDBC thin: support query timeout implemented. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5438 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5772.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5772 commit 25c6a1d742ec7ed8bd87e828479069be45ec1bf7 Author: sanpwc Date: 2018-11-12T08:31:10Z IGNITE-5439: Initial implementation. commit 359d2c9b60730b4a9c6cc9e053d022e1f36548d9 Author: alapin Date: 2018-11-12T09:59:01Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5439 commit 423a1b2d2143fe82dd6a0c07b8541bc2a42a1c4b Author: sanpwc Date: 2018-11-13T11:07:13Z IGNITE-5439: Work in progress; commit 99dc0798d1b8a55b402e9dcd248c35320cfa3ee6 Author: sanpwc Date: 2018-11-15T15:12:06Z IGNITE-5439: Request Id addedboth to JdbcRequest and JdbcResponse, cancellation thread-safety added, minor changes; commit a2e3a010df6fad1ce2902a4c641911d44ffe2b32 Author: alapin Date: 2018-11-15T15:13:45Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5439 commit 6d12f3648aa3a7254ec42be40e9a965cc9ed9bf4 Author: sanpwc Date: 2018-11-16T12:03:12Z IGNITE-5439: Support for canceling file uploads added, few more tests added; commit 67f5f91b1f5e650943edf6c0e1e2efe7db020305 Author: alapin Date: 2018-11-16T12:04:01Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5439 commit fb7f3c7db2a04b9c89f212b3ae9e8d865404fd91 Author: sanpwc Date: 2018-11-16T12:52:22Z IGNITE-5439: bug in tests fixed; commit cfb918d672824cced7a852cb6e164e2a17ce8860 Author: sanpwc Date: 2018-11-16T12:53:15Z IGNITE-5439: warning suppresed in tests; commit 440795fa04143e35c7b09c04e2fa2fcbc9406969 Author: sanpwc Date: 2018-11-16T14:25:40Z IGNITE-5439: more tests added: multistatement and batch canceling; commit 95966c89f25d790d3b4241efce4972a630cd18fd Author: sanpwc Date: 2018-11-19T10:59:21Z IGNITE-5439: Issues fixed after review; commit 4c1ecfd0261f0a779e8aade6dd8ea5433ff570d1 Author: tledkov Date: 2018-11-19T11:15:58Z IGNITE-5439: minors commit b592040147d803d8b7acdd6534e104efc7cfe3e4 Author: tledkov Date: 2018-11-19T12:20:28Z IGNITE-5439: minors commit c7cf72c5540493f0510fa6f06ddfa6efe056a95f Author: alapin Date: 2018-11-19T13:37:06Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5439 commit ec7f979034f22498849d4f94608f3fb84686a0cd Author: alapin Date: 2018-11-19T13:42:25Z Merge branch 'ignite-5439' of https://github.com/gridgain/apache-ignite into ignite-5439 commit 33d396007c350057c6c8c9f0cb53167ffdfb6cb7 Author: sanpwc Date: 2018-11-19T13:45:20Z IGNITE-5439: Error handling, logging and security handling added within GridNioPriorityQueryFilter; commit 3ae5b07f161401607a7c71f9da02394c2e85cb30 Author: sanpwc Date: 2018-11-19T14:12:13Z IGNITE-5439: Error handling within JdbcRequestHandler#cancelQuery added; commit cdb7ab9ccc65fb2929cba1fc49de086852410d53 Author: sanpwc Date: 2018-11-19T15:00:54Z IGNITE-5439: More methods of JdbcThinStatement now throws SQLException(Query was cancelled). commit ac7635d25421bf0d7bb0d6cf85f6c1342a0ad6b6 Author: sanpwc Date: 2018-11-19T15:50:15Z IGNITE-5439: RequestToCursorsMapping cleanup implemented. commit 7615488361c13db65675ea7e06abb759d4ec46ad Author: sanpwc Date: 2018-11-19T16:07:56Z IGNITE-5439: ensureAlive() restored in several cases; commit 6254a5f91569066f902dc20e9d0c86c60709998a Author: sanpwc Date: 2018-11-20T08:55:33Z IGNITE-5439: synchronizedToCAS optimizations; commit c3e4115a4b9f47759440640820f63ba09f61a31d Author: alapin Date: 2018-11-20T08:56:13Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-5439 commit 91df0d6505b59220e7293bc95b3b5e30575be040 Author: sanpwc Date: 2018-11-20T10:06:32Z IGNITE-5439: failing testExpectSQLExceptionAndAFAPControlRetrievalAfterCancelingLongRunningFileUpload because of IGNITE-10340s; commit 4dfcf5713e70a417ad44e67231bfc2bd44514202 Author: tledkov Date: 2018-11-20T14:00:10Z Merge branch '_master' into ignite-5439 commit c8d956274453e451b39642765559a64a141fb1a9 Author: sanpwc Date: 2018-11-20T14:51:29Z IGNITE-5439: changes based on review; commit 8e13019c1e01539c0dfa
[jira] [Commented] (IGNITE-10808) Discovery message queue may build up with TcpDiscoveryMetricsUpdateMessage
[ https://issues.apache.org/jira/browse/IGNITE-10808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730647#comment-16730647 ] ASF GitHub Bot commented on IGNITE-10808: - GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/5771 IGNITE-10808 Ensure RingMessageWorker's progress. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10808 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5771.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5771 commit 8ccbec84568dc4058ea27dbfbbab0fa2e34477d9 Author: Denis Mekhanikov Date: 2018-12-26T15:37:45Z IGNITE-10808 Add a metrics overflow test. commit b4ee4478f5e9819957ca52b962af42ab3d17452a Author: Denis Mekhanikov Date: 2018-12-28T16:03:20Z IGNITE-10808 Drop stale TcpDiscoveryMetricsUpdateMessage upon arrival of fresh ones. commit 1faec4bc05834dbe1ed7eaf2b5a3265ad503c385 Author: Denis Mekhanikov Date: 2018-12-29T10:39:05Z IGNITE-10808 Modify test. commit 632dad49954247e1e16f6781a0be88b7e075c399 Author: Denis Mekhanikov Date: 2018-12-29T11:26:52Z IGNITE-10808 Track RingMessageWorker's progress. > Discovery message queue may build up with TcpDiscoveryMetricsUpdateMessage > -- > > Key: IGNITE-10808 > URL: https://issues.apache.org/jira/browse/IGNITE-10808 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Stanislav Lukyanov >Assignee: Denis Mekhanikov >Priority: Major > Labels: discovery > Fix For: 2.8 > > Attachments: IgniteMetricsOverflowTest.java > > > A node receives a new metrics update message every `metricsUpdateFrequency` > milliseconds, and the message will be put at the top of the queue (because it > is a high priority message). > If processing one message takes more than `metricsUpdateFrequency` then > multiple `TcpDiscoveryMetricsUpdateMessage` will be in the queue. A long > enough delay (e.g. caused by a network glitch or GC) may lead to the queue > building up tens of metrics update messages which are essentially useless to > be processed. Finally, if processing a message on average takes a little more > than `metricsUpdateFrequency` (even for a relatively short period of time, > say, for a minute due to network issues) then the message worker will end up > processing only the metrics updates and the cluster will essentially hang. > Reproducer is attached. In the test, the queue first builds up and then very > slowly being teared down, causing "Failed to wait for PME" messages. > Need to change ServerImpl's SocketReader not to put another metrics update > message to the top of the queue if it already has one (or replace the one at > the top with new one). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10763) MVCC: Transaction already completed error in some tests
[
https://issues.apache.org/jira/browse/IGNITE-10763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730630#comment-16730630
]
ASF GitHub Bot commented on IGNITE-10763:
-
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5770
IGNITE-10763: Call tm().resetContext() after each DML and SFU operation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10763
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5770.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5770
commit 93f9d21ab2b38eb1b720711e68236b23e1185ad5
Author: ipavlukhin
Date: 2018-12-27T08:36:22Z
some cosmetics related checking if MVCC tx is active
commit ac86097ece9235ef3f0342bc3576afd0ce2ab859
Author: ipavlukhin
Date: 2018-12-29T10:07:44Z
call tm().resetContext() after each DML and SFU operation
> MVCC: Transaction already completed error in some tests
> ---
>
> Key: IGNITE-10763
> URL: https://issues.apache.org/jira/browse/IGNITE-10763
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1,
> transactions
> Fix For: 2.8
>
>
> "Transaction is already completed" error occurs time to time in some tests.
> Reproducer:
> {{CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction}}
> {{CacheMvccPartitionedSqlTxQueriesWithReducerTest.testQueryReducerDeadlockInsertWithTxTimeout}}
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:832)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:813)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:796)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1131)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:1990)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1636)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1526)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2167)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2162)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2670)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$1(GridQueryProcessor.java:2176)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2196)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2157)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2118)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2091)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.runSql(CacheMvccReplicatedSqlTxQueriesTest.java:234)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction(CacheMvccReplicatedSqlTxQueriesTest.java:202)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>
[jira] [Commented] (IGNITE-10820) Clean up static Ignite instances in tests
[ https://issues.apache.org/jira/browse/IGNITE-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730599#comment-16730599 ] ASF GitHub Bot commented on IGNITE-10820: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5752 > Clean up static Ignite instances in tests > - > > Key: IGNITE-10820 > URL: https://issues.apache.org/jira/browse/IGNITE-10820 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > > From the recent TC OOME it can be seen that some tests contain static Ignite > instances that are not cleaned up on test end, which leads to memory leak. As > a first phase, we need to nullify them. Ultimately, we need to get rid of > static fields in tests after migration to JUnit5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10385) NPE in CachePartitionPartialCountersMap.toString
[
https://issues.apache.org/jira/browse/IGNITE-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730281#comment-16730281
]
ASF GitHub Bot commented on IGNITE-10385:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5487
> NPE in CachePartitionPartialCountersMap.toString
>
>
> Key: IGNITE-10385
> URL: https://issues.apache.org/jira/browse/IGNITE-10385
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Blocker
> Fix For: 2.8
>
>
> {noformat}
> Failed to reinitialize local partitions (preloading will be stopped)
> org.apache.ignite.IgniteException: null
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:868)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.toString(GridIoMessage.java:358)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at java.lang.StringBuilder.append(StringBuilder.java:131) ~[?:1.8.0_171]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2653)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2586)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1642)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1714)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1160)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendLocalPartitions(GridDhtPartitionsExchangeFuture.java:1399)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendPartitions(GridDhtPartitionsExchangeFuture.java:1506)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1139)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:703)
> [ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2379)
> [ignite-core-2.4.10.jar:2.4.10]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.10.jar:2.4.10]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> Caused by: org.apache.ignite.IgniteException
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1032)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:830)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:787)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:889)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage.toString(GridDhtPartitionsSingleMessage.java:551)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at java.lang.String.valueOf(String.java:2994) ~[?:1.8.0_171]
> at
> org.apache.ignite.internal.util.GridStringBuilder.a(GridStringBuilder.java:101)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.SBLimitedLength.a(SBLimitedLength.java:88)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:943)
> ~[ignite-core-2.4.10.jar:2.4.10]
> at
> org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1009)
> ~[ignite-core-2.4.10.jar:2.4.10]
> ... 16 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CachePartit
[jira] [Commented] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick
[
https://issues.apache.org/jira/browse/IGNITE-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730251#comment-16730251
]
ASF GitHub Bot commented on IGNITE-10346:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5632
> Improve TcpDiscoveryVmIpFinder usability in Yardstick
> -
>
> Key: IGNITE-10346
> URL: https://issues.apache.org/jira/browse/IGNITE-10346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
>
> Currently we have to set IP address list in both property file and Ignite XML
> config. However using
> cfg.customProperties().get("SERVER_HOSTS")
> before starting the node we can get that list, set it to
> TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick
> usability a little bit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10800) Add wal_mode parameter to yardstick properties file
[ https://issues.apache.org/jira/browse/IGNITE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730247#comment-16730247 ] ASF GitHub Bot commented on IGNITE-10800: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5734 > Add wal_mode parameter to yardstick properties file > --- > > Key: IGNITE-10800 > URL: https://issues.apache.org/jira/browse/IGNITE-10800 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Oleg Ostanin >Priority: Major > Attachments: wal_mode.zip > > > As I understand we can enable persistence with properties file parameter. I > guess we need to add a parameter for WAL mode. > Expected behavior: > * When we have in configuration region with persistence should be used this > configuration and wal_mode value from properties should be ignored. Also > should be added warnings in all nodes logs with configuration details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5439) JDBC thin: support query cancel
[
https://issues.apache.org/jira/browse/IGNITE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730233#comment-16730233
]
ASF GitHub Bot commented on IGNITE-5439:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5441
> JDBC thin: support query cancel
> ---
>
> Key: IGNITE-5439
> URL: https://issues.apache.org/jira/browse/IGNITE-5439
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Alexander Lapin
>Priority: Major
> Fix For: 2.8
>
>
> The JDBC {{Statement.cancel}} method must be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10830) Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid possible serialization issues
[
https://issues.apache.org/jira/browse/IGNITE-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730225#comment-16730225
]
ASF GitHub Bot commented on IGNITE-10830:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5760
> Return back semantic of GridServiceProcessor$ServiceTopologyCallable to avoid
> possible serialization issues
> ---
>
> Key: IGNITE-10830
> URL: https://issues.apache.org/jira/browse/IGNITE-10830
> Project: Ignite
> Issue Type: Task
> Components: managed services
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> It's necessary to revert changes of
> {{GridServiceProcessor$ServiceTopologyCallable}} introduced within
> IGNITE-9607.
> This may lead to serialization issues in some cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10823) Close all open cursors for running queries on Ignite stop
[ https://issues.apache.org/jira/browse/IGNITE-10823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730213#comment-16730213 ] ASF GitHub Bot commented on IGNITE-10823: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5754 > Close all open cursors for running queries on Ignite stop > - > > Key: IGNITE-10823 > URL: https://issues.apache.org/jira/browse/IGNITE-10823 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > Currently we can have situation when user doesn't close a cursors after use > it or don't full read it. In this case we have potential memory leak with > opened cursors. Need to close and set as null for all such running queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730200#comment-16730200
]
ASF GitHub Bot commented on IGNITE-10434:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5569
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10727) [ML] InfModel and Model merging
[ https://issues.apache.org/jira/browse/IGNITE-10727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730183#comment-16730183 ] ASF GitHub Bot commented on IGNITE-10727: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5723 > [ML] InfModel and Model merging > > > Key: IGNITE-10727 > URL: https://issues.apache.org/jira/browse/IGNITE-10727 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Platonov >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > Currently "InfModel" and "Model" provide parallel architecture in terms of > using of "InfModels" in after-learning steps like compositions, estimations > etc. I propose to move "InfModel" to top of models hierarchy and rename it to > just "Model" and current "Model" rename to > "LearnedModel/LocalModel/Your_ad_may_be_here". So in this way "InfModel" will > be just model with apply-function for generic I-O values and "Model" will be > serializable thing on Vector-Double. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10655) .NET client should have peerClassLoading property in IgniteConfiguration class
[ https://issues.apache.org/jira/browse/IGNITE-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730149#comment-16730149 ] ASF GitHub Bot commented on IGNITE-10655: - GitHub user DirectXceriD opened a pull request: https://github.com/apache/ignite/pull/5769 IGNITE-10655 add p2pEnabled to .NET You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10655 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5769.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5769 commit b78b1a9630eb0c258812ace098b975139b3f4813 Author: Vladimir Pligin Date: 2018-12-27T10:01:11Z IGNITE-10655 add p2pEnabled to .NET client > .NET client should have peerClassLoading property in IgniteConfiguration class > -- > > Key: IGNITE-10655 > URL: https://issues.apache.org/jira/browse/IGNITE-10655 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Assignee: Vladimir Pligin >Priority: Major > Fix For: 2.8 > > > In case if java server nodes in a cluster were set up with peerClassLoading > set to true then there is no way to start node via .NET client using > IgniteConfiguration (because the default value is false). > The only way to do it is using of the XML configuration. > Possibility to set this property from .Net client programmatically should be > added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730145#comment-16730145 ] ASF GitHub Bot commented on IGNITE-10811: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5759 > Add new TC build-config to test Service Grid new and old implementations > > > Key: IGNITE-10811 > URL: https://issues.apache.org/jira/browse/IGNITE-10811 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to add new build configuration on TeamCity (after merge > IGNITE-9607) to have ability testing new and old implementations of the > service processor. > In general, new build plan should contain 2 test suites: > 1) To place Service Grid related tests which *do not depend on* service > processor's implementation (like classic unit tests) and *should be executed > once*; > 2) To place Service Grid related tests which *depend* *on* service > processor's implementation and *should be executed twice* in the new mode and > old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10573) [ML] Consistent API for Ensemble training
[ https://issues.apache.org/jira/browse/IGNITE-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729910#comment-16729910 ] ASF GitHub Bot commented on IGNITE-10573: - GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/5767 [ML] IGNITE-10573: Consistent API for Ensemble training You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10573 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5767.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5767 commit 765c4400588398695c954a183887149dfd72cb6e Author: Artem Malykh Date: 2018-11-15T20:00:06Z First version commit 78857ec45c527ef07517f3a66d85843554851433 Author: Artem Malykh Date: 2018-11-16T12:49:21Z LearningEnvironmentBuilder is now interface commit 762568c28eb9f7d0ca044d7c4a3a4e4173dfdb34 Author: Artem Malykh Date: 2018-11-19T14:38:17Z Started integrating learning environment into transformers commit 74f9b09602a435c04127218f05e601e1876dee8a Author: Artem Malykh Date: 2018-11-20T11:13:25Z Learning environment included in bagging commit eeefda2107e60dc47a9229c01f50303fbb0d877e Author: Artem Malykh Date: 2018-11-22T15:22:43Z Insterted learning environment into compute commit 2ce75e07bc531092a9388688f67125463bdd7ea6 Author: Artem Malykh Date: 2018-11-22T15:48:58Z Fixed javadocs commit 13bfc70d4b9c39eaec8f4c37ba6b341ba1f7401a Author: Artem Malykh Date: 2018-11-22T16:03:03Z Javadocs commit 8454f2dbfe105fedb28025359a9414a2d7666090 Author: Artem Malykh Date: 2018-11-22T16:06:22Z Merge branch 'master-apache' into ignite-10272 commit a143a0edd6873611354298301dc253f8c03f92ad Author: Artem Malykh Date: 2018-11-22T16:21:54Z Added javadocs commit 0093271b3609eca9f214d79acad4a7c3fee293e4 Author: Artem Malykh Date: 2018-11-22T16:38:13Z Removing environment on close commit b337daa6e59bab2f13db96e3f8872e2e96d6ba74 Author: Artem Malykh Date: 2018-11-23T10:32:38Z Javadocs commit 80d67bae4f627d56e770c3180ceff7392f292c50 Author: Artem Malykh Date: 2018-11-23T12:46:32Z Fixes in javadocs commit c83545542da475d9899899832baffe66bfeb4657 Author: Artem Malykh Date: 2018-11-23T13:21:39Z Dependency on partition in LearningEnvironmentBuilder API commit 9ec0896e85a5eb6f50898e2df6d8b2f9a75e8fa4 Author: Artem Malykh Date: 2018-11-23T13:23:02Z LEB is Serializable commit 6d034d2b85b4aedf2d205fa061ba2d97d99c0350 Author: Artem Malykh Date: 2018-11-23T15:34:27Z Removed UpstreamTransformerBuildersChain commit 4a63f57716716b9655c470af6cc61b7011149002 Author: Artem Malykh Date: 2018-11-23T16:30:27Z IGNITE-10272: Fixes in functional interfaces. commit 28b49312da50825d18c80af6abd156c37b451a7f Author: Artem Malykh Date: 2018-11-26T13:24:31Z Some fixes commit 7d3219affe0db8fcfb845edbd4af8a11e22f8cfc Author: Artem Malykh Date: 2018-11-26T15:29:39Z Some fixes commit 2184eb467a9533cac7e7f15e7c328e8b692f76c5 Author: Artem Malykh Date: 2018-11-27T14:00:59Z IGNITE-10272: Fixes. commit cac69950579a07a48ce49502760e61eead19fda5 Author: Artem Malykh Date: 2018-11-27T14:12:19Z IGNITE-10272: Fixes. commit 8bfc27455bf9950d61773154b12c7fcd627e5770 Author: Artem Malykh Date: 2018-11-28T12:11:48Z IGNITE-10272: Fixes. commit f6236cb10d9f82045de0fdc8a19a1b6637aa4fd1 Author: Artem Malykh Date: 2018-11-28T12:28:40Z IGNITE-10272: Added toto about fluent API. commit 58c985f2e1d5da51a0f3cc1d1f519839b8ff7ae2 Author: Artem Malykh Date: 2018-11-28T15:04:04Z IGNITE-10272: Fixed examples, added shortcuts for DatasetFactory. commit 84a0d8ba278e598872bf0fa28aba081916f4dfa4 Author: Artem Malykh Date: 2018-11-30T12:53:38Z Draft commit 4e160d818a19a52d056cb946c88dadee11ee1ee2 Author: Artem Malykh Date: 2018-11-30T13:24:49Z Merge branch 'master-apache' into ignite-10272 # Conflicts: # modules/ml/src/main/java/org/apache/ignite/ml/dataset/PartitionDataBuilder.java # modules/ml/src/main/java/org/apache/ignite/ml/dataset/UpstreamTransformerChain.java # modules/ml/src/main/java/org/apache/ignite/ml/dataset/impl/local/LocalDatasetBuilder.java commit 1c2c2dd40c698a0f3b3467a5eba23135bdafe5f8 Author: Artem Malykh Date: 2018-11-30T13:33:32Z Merge branch 'master-apache' into ignite-10272 # Conflicts: # modules/ml/src/main/java/org/apache/ignite/ml/dataset/PartitionDataBuilder.java # modules/ml/src/main/java/org/apache/ignite/ml/dataset/UpstreamTransformerChain.java # modules/ml/src/main/java/org/apache/ignite/ml/dataset/impl/local/LocalDatasetBuilder.java commit dd7f555
[jira] [Commented] (IGNITE-10821) Caching affinity with affinity similarity key is broken
[ https://issues.apache.org/jira/browse/IGNITE-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729758#comment-16729758 ] ASF GitHub Bot commented on IGNITE-10821: - GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5766 IGNITE-10821 Affinity recalculation optimizations You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10821 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5766.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5766 commit a74768fdcb80d68370c504da225a8dfb9db9f7ec Author: Pavel Kovalenko Date: 2018-12-27T17:52:54Z IGNITE-10821 Optimize reassignment enforce on coordinator. Signed-off-by: Pavel Kovalenko > Caching affinity with affinity similarity key is broken > --- > > Key: IGNITE-10821 > URL: https://issues.apache.org/jira/browse/IGNITE-10821 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > When some cache groups have the same affinity function, number of partitions, > backups and the same node filter they can use the same affinity distribution > without needs for explicit recalculating. These parameters are called as > "Affinity similarity key". > In case of affinity recalculation caching affinity using this key may > speed-up the process. > However, after https://issues.apache.org/jira/browse/IGNITE-9561 merge this > mechanishm become broken, because parallell execution of affinity > recalculation for the similar affinity groups leads to caching affinity > misses. > To fix it we should couple together similar affinity groups and run affinity > recalculation for them in one thread, caching previous results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10774) Migrate test suites that are fixed lists of test classes from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729719#comment-16729719
]
ASF GitHub Bot commented on IGNITE-10774:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5732
> Migrate test suites that are fixed lists of test classes from Junit 3 to 4
> --
>
> Key: IGNITE-10774
> URL: https://issues.apache.org/jira/browse/IGNITE-10774
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> This task is to migrate test suites that are fixed lists of test classes from
> Junit 3 to 4 that can be handled by {{@SuiteClasses}} API.
> If needed, find more details in the comments of the parent task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10828) GridAbstractTest calculates test count incorrectly
[ https://issues.apache.org/jira/browse/IGNITE-10828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729723#comment-16729723 ] ASF GitHub Bot commented on IGNITE-10828: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5756 > GridAbstractTest calculates test count incorrectly > -- > > Key: IGNITE-10828 > URL: https://issues.apache.org/jira/browse/IGNITE-10828 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.8 > > > I have found that our naive approach doesn't work. In my case, it counted > while 112 while IDEA 113, what cause wrong isLastTest result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10773) Migrate examples testsuites from Junit 3 to 4
[ https://issues.apache.org/jira/browse/IGNITE-10773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729721#comment-16729721 ] ASF GitHub Bot commented on IGNITE-10773: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5726 > Migrate examples testsuites from Junit 3 to 4 > - > > Key: IGNITE-10773 > URL: https://issues.apache.org/jira/browse/IGNITE-10773 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.8 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > This taks is to migrate examples testsuites from Junit 3 to 4. If needed, > find more details in comments of parent task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7021) IgniteOOM is not propogated to client in case of implicit transaction
[ https://issues.apache.org/jira/browse/IGNITE-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729714#comment-16729714 ] ASF GitHub Bot commented on IGNITE-7021: Github user mcherkasov closed the pull request at: https://github.com/apache/ignite/pull/3227 > IgniteOOM is not propogated to client in case of implicit transaction > -- > > Key: IGNITE-7021 > URL: https://issues.apache.org/jira/browse/IGNITE-7021 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Critical > Fix For: 2.4 > > > it's related to https://issues.apache.org/jira/browse/IGNITE-7019 > when transaction fails due IgniteOOM, ignite tries to rollback transaction > and it fails too, because can't add free pages to free list due a new > IgniteOOM: > [2017-11-27 > 12:47:37,539][ERROR][sys-stripe-2-#4%cache.IgniteOutOfMemoryPropagationTest0%][GridNearTxLocal] > Heuristic transaction failure. > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:835) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:774) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:555) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:441) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:489) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitAsync(GridDhtTxLocal.java:498) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onDone(GridDhtTxPrepareFuture.java:727) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onDone(GridDhtTxPrepareFuture.java:104) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451) > at > org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285) > at > org.apache.ignite.internal.util.future.GridCompoundFuture.markInitialized(GridCompoundFuture.java:276) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1246) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:666) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1040) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:398) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:519) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:150) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:135) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:97) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:177) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:175) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1060) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99) > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293) > at > org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555) > at > org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183) > at > org.apache.ignite.internal.managers.communication.GridI
[jira] [Commented] (IGNITE-10078) Node failure during concurrent partition updates may cause partition desync between primary and backup.
[ https://issues.apache.org/jira/browse/IGNITE-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729693#comment-16729693 ] ASF GitHub Bot commented on IGNITE-10078: - GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/5765 IGNITE-10078 Node failure during concurrent partition updates may cause partition desync between primary and backup. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10078 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5765.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5765 commit 253df1059b0ad0f003a711e63007df7b2e1b77c0 Author: Aleksei Scherbakov Date: 2018-10-31T15:38:07Z IGNITE-10078 wip. commit beb579c83782ef4d2be91a29c43b99410e4f8d6d Author: Aleksei Scherbakov Date: 2018-11-01T09:51:24Z Merge branch 'master' of https://github.com/apache/ignite into ignite-10078 commit a43e5876cb81bb00fdbccc004d28e9c4ceda475a Author: Aleksei Scherbakov Date: 2018-11-06T07:31:38Z IGNITE-10078 wip. commit defbcc167aaf358991c2874b2b0d600b6248f921 Author: ascherbakoff Date: 2018-11-12T19:41:57Z IGNITE-10078 wip. commit 64d7e2d2a235fb822b68ca21f02d85f43f88b019 Author: ascherbakoff Date: 2018-11-12T19:42:43Z Merge branch 'master' of https://github.com/apache/ignite into ignite-10078 commit 2317758268879c647d80367f44c121645713de78 Author: Aleksei Scherbakov Date: 2018-11-14T14:45:49Z IGNITE-10078 wip. commit 63d7ab771d664eafc1e5f18f7a2f51500113316b Author: Aleksei Scherbakov Date: 2018-11-16T15:51:59Z IGNITE-10078 wip. commit e210e1cb26e774625252b1a2f11d295f80f48351 Author: ascherbakoff Date: 2018-11-18T14:06:45Z IGNITE-10078 wip. commit 2efba0a10b64490ac435e0157a5eeca8c2712ecc Author: ascherbakoff Date: 2018-11-18T14:12:14Z IGNITE-10078 wip. commit e721aba13512433caf9b6420e00dfef76dce3c47 Author: ascherbakoff Date: 2018-11-18T14:31:20Z IGNITE-10078 wip. commit ef7a7857fc00bebe9fc9289ecdb687c43973e947 Author: ascherbakoff Date: 2018-11-18T14:43:15Z IGNITE-10078 wip. commit 22436a83dc0993461c08155b9e68b612dda3360a Author: ascherbakoff Date: 2018-11-18T15:37:16Z IGNITE-10078 wip. commit d176c8b30c303f19b5beeff640e7ed5b961f81c3 Author: Aleksei Scherbakov Date: 2018-11-19T10:34:39Z IGNITE-10078 wip. commit 30a8f30eef9d76d5aa72f2bc43882c7e47f5d221 Author: Aleksei Scherbakov Date: 2018-11-19T13:20:16Z IGNITE-10078 wip. commit 97aba597a95ea4dc5e2684dfb7bc68c23e3a98d0 Author: Aleksei Scherbakov Date: 2018-11-19T13:49:39Z IGNITE-10078 wip. commit aacff35491a07f93ea844e360f774a0708b155c8 Author: Aleksei Scherbakov Date: 2018-11-19T13:55:38Z IGNITE-10078 wip. commit 29eee5c2c2790ff474957760973dd617a0584a61 Author: Aleksei Scherbakov Date: 2018-11-19T14:02:32Z IGNITE-10078 wip. commit 0b28c3d6da4285724116213d0b433160f62324cd Author: Aleksei Scherbakov Date: 2018-11-19T14:05:32Z IGNITE-10078 wip. commit 06aba801780def39cb00c23a3467a534f44b0b84 Author: ascherbakoff Date: 2018-11-20T22:31:03Z IGNITE-10078 wip. commit a666157dc488c96fb5758daee24101c579e57b19 Author: Aleksei Scherbakov Date: 2018-11-21T16:10:03Z IGNITE-10078 wip. commit e9d52f94e9cb76f620bd9700aa1e7925f0a95842 Author: Aleksei Scherbakov Date: 2018-11-22T10:14:10Z Merge branch 'master' of https://github.com/apache/ignite into ignite-10078 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheGroupContext.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheDatabaseSharedManager.java commit 7a42fdbd821c2e57c3edff16cca719e17505b68d Author: Aleksei Scherbakov Date: 2018-11-22T10:21:36Z Merge branch 'master' of https://github.com/apache/ignite into ignite-10078 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/CacheGroupContext.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/PartitionUpdateCounter.java #
[jira] [Commented] (IGNITE-10087) IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master
[ https://issues.apache.org/jira/browse/IGNITE-10087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729690#comment-16729690 ] ASF GitHub Bot commented on IGNITE-10087: - GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/5764 IGNITE-10087 IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-10087 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5764.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5764 commit 56767196ff5e34d4489525b3b06c4680e1711756 Author: NSAmelchev Date: 2018-12-27T16:00:19Z Fix for the test > IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky > in master > --- > > Key: IGNITE-10087 > URL: https://issues.apache.org/jira/browse/IGNITE-10087 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > The IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 test > is flaky in master. Sometimes the test fails on test timeout (5 min). > [Test > history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-6728945354254258306&branch=&tab=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9893) add hibernate-5.3 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729664#comment-16729664 ] ASF GitHub Bot commented on IGNITE-9893: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5763 > add hibernate-5.3 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > Fix For: 2.8 > > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9893) add hibernate-5.3 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729661#comment-16729661 ] ASF GitHub Bot commented on IGNITE-9893: GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/5763 IGNITE-9893 Assembly LGPL dependencies for hibernate_5.3 module. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9893-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5763.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5763 commit c16f5bb54312decac394f0a5429a947a710184e0 Author: Ilya Kasnacheev Date: 2018-12-27T15:12:05Z IGNITE-9893 Assembly LGPL dependencies for hibernate_5.3 module. > add hibernate-5.3 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > Fix For: 2.8 > > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10403) Yardstick does not work without Guava 20 in the classpath
[
https://issues.apache.org/jira/browse/IGNITE-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729651#comment-16729651
]
ASF GitHub Bot commented on IGNITE-10403:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5498
> Yardstick does not work without Guava 20 in the classpath
> -
>
> Key: IGNITE-10403
> URL: https://issues.apache.org/jira/browse/IGNITE-10403
> Project: Ignite
> Issue Type: Bug
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> Exception in thread "main" java.lang.NoSuchMethodError:
> com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
> at org.reflections.Reflections.expandSuperTypes(Reflections.java:380) at
> org.reflections.Reflections.(Reflections.java:126) at
> org.reflections.Reflections.(Reflections.java:168) at
> org.yardstickframework.impl.BenchmarkLoader.initialize(BenchmarkLoader.java:99)
> at
> org.yardstickframework.BenchmarkServerStartUp.main(BenchmarkServerStartUp.java:40)
> {noformat}
>
> Explanation from this link:
> [https://github.com/confluentinc/kafka-connect-elasticsearch/issues/143]
> 'This error means that you are bringing an older version of guava earlier in
> your classpath. Connect worker requires guava >= 20 for org.reflections to
> work correctly.'
> Indeed adding guava 20 to Yardstick ./lib folder helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10606) [ML] Add new tests for BinaryClassificationMetrics and Evaluator
[ https://issues.apache.org/jira/browse/IGNITE-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729598#comment-16729598 ] ASF GitHub Bot commented on IGNITE-10606: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5751 > [ML] Add new tests for BinaryClassificationMetrics and Evaluator > > > Key: IGNITE-10606 > URL: https://issues.apache.org/jira/browse/IGNITE-10606 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Cover the Evaluator static methods by tests. > It should be simple tests smaller than Evaluator example > Cover next items: > 1) incorrect metrics > 2) unexisting labels in a part of metrics > 3) repeatable metrics > 4) repeatable metrics with repeatable class labels (check count of final > results) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10580) H2 connection and statements are reused invalid for local sql queries
[
https://issues.apache.org/jira/browse/IGNITE-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729591#comment-16729591
]
ASF GitHub Bot commented on IGNITE-10580:
-
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5762
IGNITE-10580 H2 connection and statements are reused invalid for local sql
queries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10580
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5762.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5762
commit 1ebdf5ae5b59a8780003db8a6deac0e2d259bab9
Author: tledkov
Date: 2018-12-06T15:41:50Z
IGNITE-10580: add test to reproduce
commit 614d1b194bdb97d83e87893aa3a5462c970bb2c4
Author: tledkov
Date: 2018-12-06T15:43:27Z
IGNITE-10580: test cleanup
commit 035e4b0c874a103227b0f3874decbd5dd383f19c
Author: tledkov
Date: 2018-12-07T09:32:48Z
IGNITE-10580: modify test
commit 54708047eef6d6364273637d3be3f239b5d8e148
Author: tledkov
Date: 2018-12-14T10:30:31Z
Merge branch '_master' into ignite-10580
commit 174f50640fce72388d7efe013eb26f1bc4aba471
Author: tledkov
Date: 2018-12-14T10:51:23Z
IGNITE-10580: save the progress
commit a00a8ff7969b84b9b57c098fe8035272c2b955ac
Author: tledkov
Date: 2018-12-24T09:52:34Z
Merge branch '_master' into ignite-10580
commit 8be520299c5a5de2f55018a8b2cfa262905c89af
Author: tledkov
Date: 2018-12-24T09:55:28Z
Merge master into ignite-10580
commit 6c7cebe9426c494f9841f05ffdeb443d2fa4a4a6
Author: tledkov
Date: 2018-12-24T10:23:01Z
IGNITE-10580: cleanup
commit 349d74ff9ebacfa279fbfb5d97e090a0c2fd0816
Author: tledkov
Date: 2018-12-27T13:16:28Z
Merge master into ignite-10580
> H2 connection and statements are reused invalid for local sql queries
> -
>
> Key: IGNITE-10580
> URL: https://issues.apache.org/jira/browse/IGNITE-10580
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
>
> The threadlocal connection & statement cache is used invalid for local
> queries.
> Steps to reproduce:
> # Open iterator for local query {{Query0}};
> # In the same thread open one more iterator for {{Query1}} (SQl statement
> must be equals to {{Query0}} and doesn't contains query parameters);
> # Fetch from the first iterator.
> The exception {{The object is already closed [90007-197]}} will be thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10803) [ML] Add prototype LogReg loading from PMML format
[ https://issues.apache.org/jira/browse/IGNITE-10803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729593#comment-16729593 ] ASF GitHub Bot commented on IGNITE-10803: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5744 > [ML] Add prototype LogReg loading from PMML format > -- > > Key: IGNITE-10803 > URL: https://issues.apache.org/jira/browse/IGNITE-10803 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Generate or get existing PMML model for known dataset to load and predict new > data in Ignite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1260) S3 IP finder should have an option to use a subfolder instead of bucket root
[ https://issues.apache.org/jira/browse/IGNITE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729582#comment-16729582 ] ASF GitHub Bot commented on IGNITE-1260: Github user udaykale closed the pull request at: https://github.com/apache/ignite/pull/4153 > S3 IP finder should have an option to use a subfolder instead of bucket root > > > Key: IGNITE-1260 > URL: https://issues.apache.org/jira/browse/IGNITE-1260 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.1.4 >Reporter: Valentin Kulichenko >Assignee: Uday Kale >Priority: Minor > Labels: newbie, usability, user-request > Fix For: 2.7 > > > Current implementation forces user to use the bucket root which is not always > possible. Need to provide a configuration parameter that allows to provide a > path in addition to the bucket name. > Corresponding user@ thread: > http://apache-ignite-users.70518.x6.nabble.com/AWS-Integration-td495.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10353) Spring Add Update/Delete support for Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729520#comment-16729520 ] ASF GitHub Bot commented on IGNITE-10353: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5532 > Spring Add Update/Delete support for Spring Data > > > Key: IGNITE-10353 > URL: https://issues.apache.org/jira/browse/IGNITE-10353 > Project: Ignite > Issue Type: New Feature > Components: spring >Affects Versions: 2.7 >Reporter: Jonathan Camargo >Assignee: Jonathan Camargo >Priority: Minor > Labels: spring > Fix For: 2.8 > > > In Spring Data 2.0 module, add the update/delete functionalities to work with > the cache, this should be possible even using the method name in the > IgniteRepository interface or by a @Query notation writing the SQL query > following the ignite docs for it. > The specification for the remaining methods for the Repository interface are > mentioned on the Spring documentation. > https://docs.spring.io/spring-data/jpa/docs/current/reference/html/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10830) Return back semantic of GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization issues
[
https://issues.apache.org/jira/browse/IGNITE-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729517#comment-16729517
]
ASF GitHub Bot commented on IGNITE-10830:
-
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/5760
IGNITE-10830 Return back semantic of
GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization
issues
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-10830
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5760.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5760
commit 33cb0575d2e38dc32771c55fc9a0aa7dffb1778d
Author: Vyacheslav Daradur
Date: 2018-12-27T10:39:13Z
Fixed.
> Return back semantic of GridServiceProcessor#ServiceTopologyCallable to avoid
> possible serialization issues
> ---
>
> Key: IGNITE-10830
> URL: https://issues.apache.org/jira/browse/IGNITE-10830
> Project: Ignite
> Issue Type: Task
> Components: managed services
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> It's necessary to revert changes of
> {{GridServiceProcessor#ServiceTopologyCallable}} introduced within
> IGNITE-9607.
> This may lead to serialization issues in some cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729500#comment-16729500 ] ASF GitHub Bot commented on IGNITE-10811: - GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5759 IGNITE-10811 Add new TC build-config to test Service Grid new and old implementations You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-10811 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5759.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5759 commit 70b30d4be62fa8c11f073ef8ec8ff00f6c41f6b3 Author: Vyacheslav Daradur Date: 2018-12-26T12:49:19Z Added IgniteServiceGridTestSuite commit f68822601f3a234017ac92d21b29a0e7cc4099a5 Author: Vyacheslav Daradur Date: 2018-12-27T10:05:44Z Merge branch 'master' into ignite-10811 # Conflicts: # modules/core/src/test/java/org/apache/ignite/testsuites/IgniteKernalSelfTestSuite.java commit 8f69d128b7b0b3b3383232664a23c8815e9a2479 Author: Vyacheslav Daradur Date: 2018-12-27T10:06:11Z Added new tests from master > Add new TC build-config to test Service Grid new and old implementations > > > Key: IGNITE-10811 > URL: https://issues.apache.org/jira/browse/IGNITE-10811 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to add new build configuration on TeamCity (after merge > IGNITE-9607) to have ability testing new and old implementations of the > service processor. > In general, new build plan should contain 2 test suites: > 1) To place Service Grid related tests which *do not depend on* service > processor's implementation (like classic unit tests) and *should be executed > once*; > 2) To place Service Grid related tests which *depend* *on* service > processor's implementation and *should be executed twice* in the new mode and > old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9845) Web Console: Add support of two way ssl authentication in Web Console agent
[
https://issues.apache.org/jira/browse/IGNITE-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729478#comment-16729478
]
ASF GitHub Bot commented on IGNITE-9845:
Github user akuznetsov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/5022
> Web Console: Add support of two way ssl authentication in Web Console agent
> ---
>
> Key: IGNITE-9845
> URL: https://issues.apache.org/jira/browse/IGNITE-9845
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Affects Versions: 2.6
>Reporter: Andrey Novikov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.8
>
> Attachments: Selection_274.png
>
>
> RestExecutor should not be shared between different users requests in case of
> two way ssl authentication:
> * For each token with ssl we need create separated RestExecutor and set up
> socketFactory and trustManager.
> * RestExecutor should be removed if token expired.
> Add program arguments for passing client certificate, client password, trust
> store, trust store password for ignite node connection and web console
> backend.
> Example on okhttp:
> [https://github.com/square/okhttp/blob/cd872fd83824512c128dcd80c04d445c8a2fc8eb/okhttp-tests/src/test/java/okhttp3/internal/tls/ClientAuthTest.java]
> Upgrade socket-io from 1.x to 2.x.
> Add support for SSL cipher suites
> Add tests.
> ---
> *How to do local testing:*
> On Windows
> # Download Open SSL: Download Open SSL for Windows from
> [https://wiki.openssl.org/index.php/Binaries]
> # Unpack it.
> On Linux - it is usually built-in.
> Generate keys with provided script (see attached generate.bat, it could be
> easily adapted for Linux).
>
> Add to etc/hosts:
> 127.0.0.1 localhost console.test.local
>
> After that configure SSL for:
> # Web Console back-end.
> # Web Agent.
> # Cluster.
> *Configure Web Console back-end settings:*
> "ssl": true,
> "key": "some_path/server.key",
> "cert": "some_path/server.crt",
> "ca": "some_path/ca.crt",
> "keyPassphrase": "p123456",
> *Configure Web Agent parameters (see parameters descriptions):*
> -t your_token
> -s [https://console.test.local:3000|https://console.test.local:3000/] -n
> [https://console.test.local:11443|https://console.test.local:11443/]
> -nks client.jks -nkp p123456
> -nts ca.jks -ntp p123456
> -sks client.jks -skp p123456
> -sts ca.jks -stp p123456
> *Configure cluster JETTY config:*
>
> https
> default="11443"/>
> true
> true
> class="org.eclipse.jetty.server.SecureRequestCustomizer"/>
>
> class="org.eclipse.jetty.util.ssl.SslContextFactory">
> some_path/server.jks
> p123456
> some_path/ca.jks
> p123456
> true
>
> *How to start secure web console in direct install edition in Ubuntu:*
> # Download ignite web console direct install for linux ZIP archive .
> # Unpack downloaded archive to goal folder.
> # Generate SSL certificates.
> # Copy generated certificates to folder with unpacked web console direct
> install.
> # Open terminal and navigate to folder with unpacked web console direct
> install.
> # Run web console with the next command:
> {code:java}
> ignite-web-console-linux --server:port 11443 --server:ssl true
> --server:requestCert true --server:key "server.key" --server:cert
> "server.crt" --server:ca "ca.crt" --server:passphrase "p123456"{code}
> 7. Import client.p12 certificate into your browser. See attached
> screenstot in Chrome browser.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10827) auto close iterator for query cursor when all data has been read
[ https://issues.apache.org/jira/browse/IGNITE-10827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729463#comment-16729463 ] ASF GitHub Bot commented on IGNITE-10827: - GitHub user ygerzhedovich opened a pull request: https://github.com/apache/ignite/pull/5758 IGNITE-10827 …been read You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10827 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5758.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5758 commit a06abb2c80b883fc0c94027dcee8c74748584883 Author: Yury Gerzhedovich Date: 2018-12-27T09:13:28Z IGNITE-10827: auto close iterator for query cursor when all data has been read > auto close iterator for query cursor when all data has been read > > > Key: IGNITE-10827 > URL: https://issues.apache.org/jira/browse/IGNITE-10827 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: sql > > There is QueryCursorImpl class which we use as main realization of cursor for > H2 iterators. As of now we call close method explicit when we suppose that > all data already read. Will be better call close() method when iterator > hasNext() method return false or when next() method of iterator throw any > Exception. Such realization will be more safely and simple to use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10505) Flag IGNITE_DISABLE_WAL_DURING_REBALANCING should be turned on by default
[ https://issues.apache.org/jira/browse/IGNITE-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729450#comment-16729450 ] ASF GitHub Bot commented on IGNITE-10505: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5578 > Flag IGNITE_DISABLE_WAL_DURING_REBALANCING should be turned on by default > - > > Key: IGNITE-10505 > URL: https://issues.apache.org/jira/browse/IGNITE-10505 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.8 > > > Before file-based rebalancing is implemented and rigorously tested Ignite > still relies on key-based rebalancing and flag > IGNITE_DISABLE_WAL_DURING_REBALANCING speeds it up significantly. > By default it is turned off, but as it brings noticeable boost we need to > turn it on by default in the next minor release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10815) NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
[
https://issues.apache.org/jira/browse/IGNITE-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729443#comment-16729443
]
ASF GitHub Bot commented on IGNITE-10815:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5746
> NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
> -
>
> Key: IGNITE-10815
> URL: https://issues.apache.org/jira/browse/IGNITE-10815
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Possible scenario to reproduce:
> 1. Force few consecutive exchange merges and finish.
> 2. Trigger exchange.
> 3. Shutdown coordinator node before sending/receiving full partitions message.
>
> Stacktrace:
> {code:java}
> 2018-12-24 15:54:02,664 sys-#48%gg% ERROR
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
> - Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_171]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6564) Incorrect calculation size and keySize for cluster cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729284#comment-16729284 ] ASF GitHub Bot commented on IGNITE-6564: GitHub user a-polyakov opened a pull request: https://github.com/apache/ignite/pull/5757 IGNITE-6564 Incorrect calculation size and keySize for cluster cache metrics Signed-off-by: a-polyakov You can merge this pull request into a Git repository by running: $ git pull https://github.com/a-polyakov/ignite ignite-6564 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5757.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5757 commit ca9a9cd8dd1165c88a96b627704fc16f4c3951c4 Author: a-polyakov Date: 2018-12-27T03:04:47Z IGNITE-6564 Incorrect calculation size and keySize for cluster cache metrics Signed-off-by: a-polyakov > Incorrect calculation size and keySize for cluster cache metrics > > > Key: IGNITE-6564 > URL: https://issues.apache.org/jira/browse/IGNITE-6564 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Ilya Kasnacheev >Assignee: Alexand Polyakov >Priority: Minor > Labels: iep-6 > > They are currently not passed by ring and therefore only taken from current > node, which returns incorrect (local) value. > See CacheMetricsSnapshot class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10828) GridAbstractTest calculates test count incorrectly
[ https://issues.apache.org/jira/browse/IGNITE-10828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729239#comment-16729239 ] ASF GitHub Bot commented on IGNITE-10828: - GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/5756 IGNITE-10828 GridAbstractTest calculates test count incorrectly You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10828 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5756.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5756 commit 6f7600966758d93be3b8d811b8c915577194e54b Author: Eduard Shangareev Date: 2018-12-27T00:56:01Z IGNITE-10828 GridAbstractTest calculates test count incorrectly > GridAbstractTest calculates test count incorrectly > -- > > Key: IGNITE-10828 > URL: https://issues.apache.org/jira/browse/IGNITE-10828 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > > I have found that our naive approach doesn't work. In my case, it counted > while 112 while IDEA 113, what cause wrong isLastTest result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7054) S3 IP finder: support client side encryption
[
https://issues.apache.org/jira/browse/IGNITE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729228#comment-16729228
]
ASF GitHub Bot commented on IGNITE-7054:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4555
> S3 IP finder: support client side encryption
>
>
> Key: IGNITE-7054
> URL: https://issues.apache.org/jira/browse/IGNITE-7054
> Project: Ignite
> Issue Type: Improvement
> Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
>
> In case client side encryption [1] is used, it may be required to use
> {{AmazonS3EncryptionClient}} instead of regular {{AmazonS3Client}}. We need
> to add this option to the S3 IP finder, along with any applicable
> configuration parameters.
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9607) Service Grid redesign - phase 1
[ https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729190#comment-16729190 ] ASF GitHub Bot commented on IGNITE-9607: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4434 > Service Grid redesign - phase 1 > --- > > Key: IGNITE-9607 > URL: https://issues.apache.org/jira/browse/IGNITE-9607 > Project: Ignite > Issue Type: Improvement > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > This is an umbrella ticket for tasks which should be implemented atomically > in phase #1 of Service Grid redesign. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729076#comment-16729076
]
ASF GitHub Bot commented on IGNITE-10779:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5721
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2808794487465215609&tab=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10813) Run CheckpointReadLockFailureTest with JUnit4 runner
[ https://issues.apache.org/jira/browse/IGNITE-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729083#comment-16729083 ] ASF GitHub Bot commented on IGNITE-10813: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5743 > Run CheckpointReadLockFailureTest with JUnit4 runner > > > Key: IGNITE-10813 > URL: https://issues.apache.org/jira/browse/IGNITE-10813 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Trivial > Fix For: 2.8 > > > The test fails on TeamCity. Should be run in JUnit4 manner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8178) ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729073#comment-16729073
]
ASF GitHub Bot commented on IGNITE-8178:
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/5755
IGNITE-8178 ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests
fail on TC
- Fix client reconnect after cluster restarts.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-8178
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5755.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5755
commit 22cf95fcd8c1465c0b7464610b08ef121ff0af61
Author: NSAmelchev
Date: 2018-12-25T14:59:27Z
Fix
> ZookeeperDiscoverySpiTest#testReconnectServersRestart* tests fail on TC
> ---
>
> Key: IGNITE-8178
> URL: https://issues.apache.org/jira/browse/IGNITE-8178
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> The following stack trace appears in logs:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectServersRestart(ZookeeperDiscoverySpiTest.java:3513)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testReconnectServersRestart_1(ZookeeperDiscoverySpiTest.java:3498)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:46237,127.0.0.1:38364,127.0.0.1:45674,
> joinTimeout=0, sesTimeout=1, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 24 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apa
[jira] [Commented] (IGNITE-10812) SQL: split classes responsible for distributed joins
[ https://issues.apache.org/jira/browse/IGNITE-10812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729066#comment-16729066 ] ASF GitHub Bot commented on IGNITE-10812: - Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/5742 > SQL: split classes responsible for distributed joins > > > Key: IGNITE-10812 > URL: https://issues.apache.org/jira/browse/IGNITE-10812 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > This is just a refactoring task to create more precise hierarchy of classes > responsible for distributed joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10823) Close all open cursors for running queries on Ignite stop
[ https://issues.apache.org/jira/browse/IGNITE-10823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729042#comment-16729042 ] ASF GitHub Bot commented on IGNITE-10823: - GitHub user ygerzhedovich opened a pull request: https://github.com/apache/ignite/pull/5754 IGNITE-10823 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-10823 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5754.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5754 commit 6555cb174b7eb194b0006f6139f3b7df3f1b900e Author: Yury Gerzhedovich Date: 2018-12-26T13:42:03Z IGNITE-10823: Close all open cursors for running queries on Ignite stop commit d53ba3f8b645c54d2bccabf3b2d4290f420f69bc Author: Yury Gerzhedovich Date: 2018-12-26T13:43:23Z IGNITE-10823: minor > Close all open cursors for running queries on Ignite stop > - > > Key: IGNITE-10823 > URL: https://issues.apache.org/jira/browse/IGNITE-10823 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > Currently we can have situation when user doesn't close a cursors after use > it or don't full read it. In this case we have potential memory leak with > opened cursors. Need to close and set as null for all such running queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests
[ https://issues.apache.org/jira/browse/IGNITE-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729034#comment-16729034 ] ASF GitHub Bot commented on IGNITE-10715: - Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/5739 > Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests > > > Key: IGNITE-10715 > URL: https://issues.apache.org/jira/browse/IGNITE-10715 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > It's necessary to remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in > tests since this is default IP finder in tests after IGNITE-10555. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10810) [ML] Import models from MLeap
[ https://issues.apache.org/jira/browse/IGNITE-10810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729015#comment-16729015 ] ASF GitHub Bot commented on IGNITE-10810: - GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/5753 IGNITE-10810: Import models from MLeap You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10810 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5753.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5753 commit 1991fea7d9f83f78f4accb62aacfc8f81406febe Author: dmitrievanthony Date: 2018-11-29T13:38:18Z IGNITE-10289: First version of XGBoost model parser. commit e23241ee42146b98140f8071f300fd37c6ce7c01 Author: dmitrievanthony Date: 2018-11-29T15:51:38Z IGNITE-10289: Add licence header into XGBoostModel.g4. commit 4b004fc6b8400f70d7b4665c488602abf524f827 Author: dmitrievanthony Date: 2018-11-29T16:11:28Z IGNITE-10289: Add example for XGBoostModelParser. commit ec4efd2e736f4fcad5db553cb3eee47e74656295 Author: dmitrievanthony Date: 2018-11-30T09:45:12Z IGNITE-10289: Fix queue issue in IgniteDistributedInfModelBuilder. commit b95dee0029ffa60565bd8068c8e2bd610025461a Author: dmitrievanthony Date: 2018-11-30T09:55:13Z IGNITE-10289: Exclude model files from licence check scope. commit a36537d3ba0ee733a5c678f5dc9adf8334e1d577 Author: dmitrievanthony Date: 2018-11-30T15:49:25Z IGNITE-10289: Update TensorFlow examples after move models into models directory. commit b2822c861066e36b5c3e620f9ffa601190cdaed6 Author: dmitrievanthony Date: 2018-12-17T09:17:38Z IGNITE-10289: Move XGBoost lexer/parser generated by ANTLR into source tree. commit db03e38f398729c3efa9c12cb5e9537c3d2dc50c Author: dmitrievanthony Date: 2018-12-17T09:21:15Z Merge branch 'master' into ignite-10289 commit 10dea555a7edaa8e4af53c81c9b7a9838d2361b6 Author: dmitrievanthony Date: 2018-12-17T09:28:43Z IGNITE-10289: Add test suite into xgboost-model-parser module. commit fcbe24710eb0b432dd563b6267c74ae40dbdc502 Author: dmitrievanthony Date: 2018-12-17T09:31:19Z IGNITE-10289: Revert changes in example-default.xml. commit 4c7d5e2c7ddf8709b8465f4db53737f40e33e416 Author: dmitrievanthony Date: 2018-12-17T11:37:01Z IGNITE-10289: Fix TC errors. commit a8a07dac6ea6ea2379990ac3f6b2614d22b7b3b3 Author: dmitrievanthony Date: 2018-12-17T12:26:52Z IGNITE-10289: Fix TC errors and add ANTLR grammar into javadoc commit 8adbb6d90f0d47cd27a2bc4bd1539f8fada15676 Author: dmitrievanthony Date: 2018-12-17T14:18:33Z IGNITE-10289: Add todo, merge XGBoost and Ignite ML trees together. commit d7da5b4c43e43b890de358bea40c73378a01c40f Author: dmitrievanthony Date: 2018-12-17T16:13:54Z Merge remote-tracking branch 'origin/master' into ignite-10289 commit 33fa5b010dc60719b4adaa363eb56b62fb0ce373 Author: dmitrievanthony Date: 2018-12-18T13:04:55Z IGNITE-10718: Replace XGBoost trees by Ignite ML trees, initial version. commit e585f5f98179ba8d771cc07e352904f2ae082145 Author: dmitrievanthony Date: 2018-12-18T15:38:16Z Merge branch 'master' into ignite-10718 # Conflicts: # examples/src/main/java/org/apache/ignite/examples/ml/xgboost/XGBoostModelParserExample.java # modules/ml/xgboost-model-parser/src/main/java/org/apache/ignite/ml/xgboost/parser/XGModelParser.java # modules/ml/xgboost-model-parser/src/main/java/org/apache/ignite/ml/xgboost/parser/visitor/XGModelVisitor.java # modules/ml/xgboost-model-parser/src/main/java/org/apache/ignite/ml/xgboost/parser/visitor/XGTreeVisitor.java # modules/ml/xgboost-model-parser/src/test/java/org/apache/ignite/ml/xgboost/parser/XGBoostModelParserTest.java commit 3c3258a835b3c4ee6b2924bcb01e0299d3bdbabc Author: dmitrievanthony Date: 2018-12-18T15:53:35Z IGNITE-10718: Fixes after merge. commit 9fbbf2642024246ad79464eeedeb0ba4fced134f Author: dmitrievanthony Date: 2018-12-19T09:41:02Z IGNITE-10718: Fix min max scaler. commit d80c80cfb70e2f71c63f22ed926bb1652728e7b3 Author: dmitrievanthony Date: 2018-12-19T10:12:32Z IGNITE-10718: Fix ML model hierarchy. commit cbd7f995bf9da894e0ef02501d5b2271811ae060 Author: dmitrievanthony Date: 2018-12-19T13:32:55Z IGNITE-10718: Fix exception in Step_1_Read_and_Learn. commit 21b70ac09264dac5bcd434e32096d8b1a1dbc26b Author: dmitrievanthony Date: 2018-12-19T13:52:44Z IGNITE-10718: Fix exception in Step_1_Read_and_Learn. commit 177255400b2796f5c6dfd6c4d452406d7295a6fb Author: dmitrievanthony Date: 2018-12-20T12:12:25Z IGNITE-10718: Fixes after review. commit af89
[jira] [Commented] (IGNITE-10820) Clean up static Ignite instances in tests
[ https://issues.apache.org/jira/browse/IGNITE-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728963#comment-16728963 ] ASF GitHub Bot commented on IGNITE-10820: - GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5752 IGNITE-10820 Nullify static Ignite fields in tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10820 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5752.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5752 commit 26b15e874bbc73d4986034dd378214f6774accb8 Author: Alexey Goncharuk Date: 2018-12-26T09:57:43Z IGNITE-10820 Nullify static Ignite fields in tests > Clean up static Ignite instances in tests > - > > Key: IGNITE-10820 > URL: https://issues.apache.org/jira/browse/IGNITE-10820 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > > From the recent TC OOME it can be seen that some tests contain static Ignite > instances that are not cleaned up on test end, which leads to memory leak. As > a first phase, we need to nullify them. Ultimately, we need to get rid of > static fields in tests after migration to JUnit5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10606) [ML] Add new tests for BinaryClassificationMetrics and Evaluator
[ https://issues.apache.org/jira/browse/IGNITE-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728934#comment-16728934 ] ASF GitHub Bot commented on IGNITE-10606: - GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/5751 IGNITE-10606: [ML] Add new tests for BinaryClassificationMetrics and Evaluator You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10606 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5751.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5751 commit 3e4c8002870a25501bfd8508cb9073d27b9af33d Author: Zinoviev Alexey Date: 2018-12-12T15:50:25Z IGNITE-10528: Fix incorrect comparing of double values in ML examples commit 234adaa1c186fffd2c884e8f67be9f1295516540 Author: Zinoviev Alexey Date: 2018-12-14T15:19:39Z Merge branch 'master' of https://github.com/apache/ignite commit d946ef5d13596d5a799e585ca3a7b0895508a575 Author: Zinoviev Alexey Date: 2018-12-18T12:28:30Z Merge branch 'master' of https://github.com/apache/ignite commit 222bf65b73f05a48507ee4596ec2f4f0a9e2c077 Author: Zinoviev Alexey Date: 2018-12-20T12:32:21Z Merge branch 'master' of https://github.com/apache/ignite commit 659fdfb115fa8e0ced2ed34ca9f3057db4471af2 Author: Zinoviev Alexey Date: 2018-12-21T12:29:48Z Merge branch 'master' of https://github.com/apache/ignite commit 214e6c61aac4f0797dd6c0a7dbaa55f4bf87ebe4 Author: Zinoviev Alexey Date: 2018-12-21T15:28:42Z IGNITE-10606: Added tests for BinaryEvaluator commit 920904a37a8997999bd896523be6dafb5b58bed4 Author: Zinoviev Alexey Date: 2018-12-26T08:42:51Z Merge branch 'master' into ignite-10606 # Conflicts: # modules/ml/src/test/java/org/apache/ignite/ml/selection/SelectionTestSuite.java commit b9f38ea4125502a78213af9d704c8ab87a6c74d0 Author: Zinoviev Alexey Date: 2018-12-26T08:44:53Z Fixed TestSuite for JUnit 4 > [ML] Add new tests for BinaryClassificationMetrics and Evaluator > > > Key: IGNITE-10606 > URL: https://issues.apache.org/jira/browse/IGNITE-10606 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Cover the Evaluator static methods by tests. > It should be simple tests smaller than Evaluator example > Cover next items: > 1) incorrect metrics > 2) unexisting labels in a part of metrics > 3) repeatable metrics > 4) repeatable metrics with repeatable class labels (check count of final > results) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10809) IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 fails in master
[ https://issues.apache.org/jira/browse/IGNITE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728908#comment-16728908 ] ASF GitHub Bot commented on IGNITE-10809: - GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/5750 IGNITE-10809 testActiveFailover3 modified for persistent mode You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10809 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5750.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5750 commit 1fc88375e9eaee7439b2951c096bdc43f9108277 Author: Sergey Chugunov Date: 2018-12-25T11:01:50Z IGNITE-10809 testActiveFailover3 modified for persistent mode > IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 > fails in master > > > Key: IGNITE-10809 > URL: https://issues.apache.org/jira/browse/IGNITE-10809 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Test logic involves independent activation two sets of nodes and then their > join into a single cluster. > After introducing BaselineTopology concept in 2.4 version this action became > prohibited to enforce data integrity. > Test should be refactored to take this into account. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10784) SQL: Create a view with list of existing tables
[
https://issues.apache.org/jira/browse/IGNITE-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728808#comment-16728808
]
ASF GitHub Bot commented on IGNITE-10784:
-
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5749
IGNITE-10784: added TABLES view
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10784
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5749.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5749
commit 8aa0e1a89ad5ccd081aa863b3f68d8b7d768e01c
Author: Pavel Kuznetsov
Date: 2018-12-24T17:19:25Z
ignite-10784: wip
commit ea4dd42b4497bd561a308d8ff0c6fba9d5d71f24
Author: Pavel Kuznetsov
Date: 2018-12-24T23:33:56Z
ignite-10784: Implemented minimal view IGNITE.TABLES.
commit a80e224f45d0624217258f23e281f9dc6569fa14
Author: Pavel Kuznetsov
Date: 2018-12-25T10:09:33Z
ignite-10784: Tests wip.
commit 354d0c152952cc039ba7c6a8859c4639d3237826
Author: Pavel Kuznetsov
Date: 2018-12-25T12:34:29Z
ignite-10784: Fixed bug with filter. Updated code and tests;
commit 0bad909b65ccf5cdf8ee38fae9c442d3d8940164
Author: Pavel Kuznetsov
Date: 2018-12-25T12:47:50Z
ignite-10784: Rename column name;
Renamed column name of the view according to ISO standard.
commit f367f97215033a7e7f4f7d702bcf6cffd39d93dd
Author: Pavel Kuznetsov
Date: 2018-12-25T14:11:25Z
ignite-10784: added Affinity column.
commit 526cb3eb98623bbe50c694859a9ea898dbc4401a
Author: Pavel Kuznetsov
Date: 2018-12-25T15:00:27Z
ignite-10784: reverted affinity mode info in the view.
AffinityMapper should be handled during IGNITE-10310
commit ca14ca844c484e437aef323082839143daa52bf7
Author: Pavel Kuznetsov
Date: 2018-12-25T18:52:31Z
ignite-10784: Added key and field alias columns.
commit 3af040ba1d439228b5e00a615bdb8a97c6aee053
Author: Pavel Kuznetsov
Date: 2018-12-25T19:19:18Z
ignite-10784: fixed duplicates.
commit 795486fea87b762f58bbde11f0ec6e242217000c
Author: Pavel Kuznetsov
Date: 2018-12-25T19:23:17Z
ignite-10784: Got rid of unnecessary arrays allocations.
commit 6512c06e6bab6bbdcc3162d5a2be02a485806d2a
Author: Pavel Kuznetsov
Date: 2018-12-25T19:40:27Z
ignite-10784: Added key/value type name columns to the TABLES view.
> SQL: Create a view with list of existing tables
> ---
>
> Key: IGNITE-10784
> URL: https://issues.apache.org/jira/browse/IGNITE-10784
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> We need to create a system view of currently available SQL tables.
> Minimal required information:
> 1) Schema name
> 2) Table name
> 3) Owning cache name
> 4) Owning cache ID
> Other info to consider:
> 1) Affinity column name
> 2) Key/value aliases
> 3) Key/value type names
> 4) Analyse other vendors (e.g. MySQL, Postgresql) and see if any other useful
> information could be exposed (taking in count that a lot of engine properties
> are already exposed through {{CACHES}} view)
> Starting point: {{SqlSystemView}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10815) NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
[
https://issues.apache.org/jira/browse/IGNITE-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728796#comment-16728796
]
ASF GitHub Bot commented on IGNITE-10815:
-
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5746
IGNITE-10815 Fixed coordinator failover in case of exchanges merge and
non-affinity nodes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10815
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5746.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5746
commit 97d4d22f12f0a24060ea1cd7253758065cf77023
Author: Pavel Kovalenko
Date: 2018-12-25T17:25:57Z
IGNITE-10815 WIP
Signed-off-by: Pavel Kovalenko
commit 141f40b8742d12681b3f41f7ee3dbc3ae2702380
Author: Pavel Kovalenko
Date: 2018-12-25T18:51:11Z
IGNITE-10815 Fix and test.
Signed-off-by: Pavel Kovalenko
commit 84b3fc09cca1f7133883bd44c64a1466d32d5b53
Author: Pavel Kovalenko
Date: 2018-12-25T18:52:08Z
IGNITE-10815 Cleanup
Signed-off-by: Pavel Kovalenko
> NullPointerException in InitNewCoordinatorFuture.init() leads to cluster hang
> -
>
> Key: IGNITE-10815
> URL: https://issues.apache.org/jira/browse/IGNITE-10815
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Anton Kurbanov
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Possible scenario to reproduce:
> 1. Force few consecutive exchange merges and finish.
> 2. Trigger exchange.
> 3. Shutdown coordinator node before sending/receiving full partitions message.
>
> Stacktrace:
> {code:java}
> 2018-12-24 15:54:02,664 sys-#48%gg% ERROR
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
> - Failed to init new coordinator future: bd74f7ed-6984-4f78-9941-480df673ab77
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.events(GridDhtPartitionsExchangeFuture.java:534)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1790)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$18.applyx(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllRegisteredCacheGroups(CacheAffinitySharedManager.java:1107)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initCoordinatorCaches(CacheAffinitySharedManager.java:1738)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.InitNewCoordinatorFuture.init(InitNewCoordinatorFuture.java:104)
> ~[ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3439)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$8$1.call(GridDhtPartitionsExchangeFuture.java:3435)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6720)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.4.13.b4.jar:2.4.13.b4]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_171]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10178) change tests that fail("Ignite JIRA ticket URL") to @Ignore("Ignite JIRA ticket URL")
[
https://issues.apache.org/jira/browse/IGNITE-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728789#comment-16728789
]
ASF GitHub Bot commented on IGNITE-10178:
-
GitHub user ololo3000 opened a pull request:
https://github.com/apache/ignite/pull/5745
IGNITE-10178 Ignore annotations added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ololo3000/ignite IGNITE-10178
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5745.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5745
commit aa2c91f0de000323e1ab8246ae5a1d55429f16d1
Author: Petrov
Date: 2018-12-25T15:05:58Z
IGNITE-10178 Ignore annotations added
commit 8b859ace05cbe0e20a5f7a13be32fa0179591728
Author: Petrov
Date: 2018-12-25T15:12:18Z
Merge branch 'master' into IGNITE-10178
commit 1a8cc8fe1251b1ced6e278816c7ad4ac1c4ecbe7
Author: Petrov
Date: 2018-12-25T16:56:58Z
IGNITE-10178 minor fixes
> change tests that fail("Ignite JIRA ticket URL") to @Ignore("Ignite JIRA
> ticket URL")
> -
>
> Key: IGNITE-10178
> URL: https://issues.apache.org/jira/browse/IGNITE-10178
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: PetrovMikhail
>Priority: Major
>
> Change tests that use {{fail("Ignite JIRA ticket URL")}} to {{@Ignore("Ignite
> JIRA ticket URL")}}. Do the same change for tests that fail by
> {{@IgniteIgnore("Ignite JIRA ticket URL")}}, like for example
> [S3CheckpointSpiStartStopSelfTest.testStartStop|https://github.com/apache/ignite/blob/master/modules/aws/src/test/java/org/apache/ignite/spi/checkpoint/s3/S3CheckpointSpiStartStopSelfTest.java].
> Also, use
> [Ignore|http://junit.sourceforge.net/javadoc/org/junit/Ignore.html] to
> annotate empty test classes in examples that were discovered and re-muted per
> IGNITE-10174.
> If needed, refer parent task for more details.
> Note this step would better be coordinated with Teamcity and TC bot
> maintainers because it may substantially impact them.
> -
> Note that tests that are expected to be ignored depending on runtime
> conditions should be rewritten to use {{Assume}} instead of {{fail}}. So that
> old code...
> {code}if (someRuntimeCondition())
> fail("Ignite JIRA ticket URL");{code}
> ...will change to
> {code}Assume.assumeFalse("Ignite JIRA ticket URL",
> someRuntimeCondition());{code}
> (this change can be "extracted" into separate JIRA task if it is more
> convenient). Readers interested to find more details about how {{Assume}}
> works can find more details and code snippet [in comments
> here|https://issues.apache.org/jira/browse/IGNITE-10178?focusedCommentId=16723863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16723863].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728768#comment-16728768 ] ASF GitHub Bot commented on IGNITE-3303: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5020 > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra >Priority: Major > Fix For: 2.8 > > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10543) [ML] Test/train sample generator
[ https://issues.apache.org/jira/browse/IGNITE-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728754#comment-16728754 ] ASF GitHub Bot commented on IGNITE-10543: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5727 > [ML] Test/train sample generator > > > Key: IGNITE-10543 > URL: https://issues.apache.org/jira/browse/IGNITE-10543 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > Fix For: 2.8 > > > Need to design and implement sample generators for standard distributions and > user defined functions/points. It is useful for test regressions and > statistic package examples. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10718) [ML] Merge XGBoost and Ignite ML trees together
[ https://issues.apache.org/jira/browse/IGNITE-10718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728752#comment-16728752 ] ASF GitHub Bot commented on IGNITE-10718: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5691 > [ML] Merge XGBoost and Ignite ML trees together > --- > > Key: IGNITE-10718 > URL: https://issues.apache.org/jira/browse/IGNITE-10718 > Project: Ignite > Issue Type: Improvement > Components: ml >Affects Versions: 2.8 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > Currently we have two similar hierarchy of trees: XGBoost trees and Ignite ML > trees. Would be great to merge them together. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10558) MVCC: IgniteWalReader test failed.
[ https://issues.apache.org/jira/browse/IGNITE-10558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728746#comment-16728746 ] ASF GitHub Bot commented on IGNITE-10558: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5583 > MVCC: IgniteWalReader test failed. > -- > > Key: IGNITE-10558 > URL: https://issues.apache.org/jira/browse/IGNITE-10558 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: WAL, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > Wal iterator doesn't handle Mvcc wal records. > This causes IgniteWalReader tests failures in Mvcc Pds2 suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10580) H2 connection and statements are reused invalid for local sql queries
[
https://issues.apache.org/jira/browse/IGNITE-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728738#comment-16728738
]
ASF GitHub Bot commented on IGNITE-10580:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5592
> H2 connection and statements are reused invalid for local sql queries
> -
>
> Key: IGNITE-10580
> URL: https://issues.apache.org/jira/browse/IGNITE-10580
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
>
> The threadlocal connection & statement cache is used invalid for local
> queries.
> Steps to reproduce:
> # Open iterator for local query {{Query0}};
> # In the same thread open one more iterator for {{Query1}} (SQl statement
> must be equals to {{Query0}} and doesn't contains query parameters);
> # Fetch from the first iterator.
> The exception {{The object is already closed [90007-197]}} will be thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10474) MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails.
[ https://issues.apache.org/jira/browse/IGNITE-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728734#comment-16728734 ] ASF GitHub Bot commented on IGNITE-10474: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5698 > MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery > fails. > -- > > Key: IGNITE-10474 > URL: https://issues.apache.org/jira/browse/IGNITE-10474 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Roman Kondakov >Priority: Major > Labels: Hanging, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails > due to hanging. > We have to investigate and fix this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10785) MVCC: Grid can hang if transaction is failed to rollback
[
https://issues.apache.org/jira/browse/IGNITE-10785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728727#comment-16728727
]
ASF GitHub Bot commented on IGNITE-10785:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5735
> MVCC: Grid can hang if transaction is failed to rollback
>
>
> Key: IGNITE-10785
> URL: https://issues.apache.org/jira/browse/IGNITE-10785
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Sometimes grid can hang if transactions is failed to rollback. Reproducer:
>
> {noformat}
> [2018-12-14 08:48:13,890][WARN
> ][sys-stripe-9-#12552%transactions.TxRollbackAsyncWithPersistenceTest2%][GridDhtColocatedCache]
> Failed to acquire lock (transaction has been completed):
> GridCacheVersion [topVer=156257270, order=1544777270268, nodeOrder=4]
> [2018-12-14
> 08:48:13,893][ERROR][sys-stripe-9-#12552%transactions.TxRollbackAsyncWithPersistenceTest2%][GridDhtColocatedCache]
> Failed to rollback the transaction: GridDhtTxLocal
> [nearNodeId=b4ff2bcc-dc6a-49c2-a2ab-f26bae6b68c1,
> nearFutId=282d09ca761-8ff10d65-a1d6-4f40-9fd7-afb7afa0b25c, nearMiniId=1,
> nearFinFutId=382d09ca761-8ff10d65-a1d6-4f40-9fd7-afb7afa0b25c,
> nearFinMiniId=1, nearXidVer=GridCacheVersion [topVer=156257270,
> order=1544777270268, nodeOrder=4], lb=null, super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView
> [], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null,
> sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl
> [activeCacheIds=[], recovery=null, mvccEnabled=null, txMap=HashSet []],
> mvccWaitTxs=null, qryEnlisted=false, forceSkipCompletedVers=false,
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=156257270,
> order=1544777270269, nodeOrder=3], writeVer=null, implicit=false, loc=true,
> threadId=13949, startTime=1544777293884,
> nodeId=cb0ed489-aa1c-4e7a-a196-3bea9e52, startVer=GridCacheVersion
> [topVer=156257270, order=1544777270269, nodeOrder=3], endVer=null,
> isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0,
> sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion
> [topVer=156257270, order=1544777270269, nodeOrder=3], finalizing=NONE,
> invalidParts=null, state=ROLLED_BACK, timedOut=false,
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0],
> mvccSnapshot=MvccSnapshotResponse [futId=82, crdVer=1544777266400, cntr=848,
> opCntr=1, txs=[640, 769, 706, 387, 707, 708, 582, 646, 583, 586, 847, 596,
> 660, 724, 661, 598, 599, 603, 667, 731, 685, 494, 686, 688, 561, 629, 570,
> 766, 639], cleanupVer=263, tracking=0], parentTx=null, duration=0ms,
> onePhaseCommit=false], size=0]]]
> class org.apache.ignite.IgniteCheckedException: Failed to finish transaction
> [commit=false,
> tx=GridDhtTxLocal[xid=df386eba761--0950-4bf6--0003,
> xidVersion=GridCacheVersion [topVer=156257270, order=1544777270269,
> nodeOrder=3], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=ROLLED_BACK, invalidate=false, rollbackOnly=true,
> nodeId=cb0ed489-aa1c-4e7a-a196-3bea9e52, timeout=0, duration=0]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:482)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.rollbackDhtLocalAsync(GridDhtTxLocal.java:588)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.rollbackDhtLocal(GridDhtTxLocal.java:563)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.initTxTopologyVersion(GridDhtTransactionalCacheAdapter.java:2178)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxEnlistRequest(GridDhtTransactionalCacheAdapter.java:2016)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$900(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:229)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:227)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
> at
> org.apache.ignite.internal.processors.cache.GridCache
[jira] [Commented] (IGNITE-10743) MVCC: Mute flaky mvcc tests
[ https://issues.apache.org/jira/browse/IGNITE-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728716#comment-16728716 ] ASF GitHub Bot commented on IGNITE-10743: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5724 > MVCC: Mute flaky mvcc tests > --- > > Key: IGNITE-10743 > URL: https://issues.apache.org/jira/browse/IGNITE-10743 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Roman Kondakov >Assignee: Roman Kondakov >Priority: Major > Labels: mvcc_stabilization_stage_1 > Fix For: 2.8 > > > We should mute all flaky MVCC tests on TC with appropriate tickets links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10621) Track all running queries on initial query node
[ https://issues.apache.org/jira/browse/IGNITE-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728695#comment-16728695 ] ASF GitHub Bot commented on IGNITE-10621: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5620 > Track all running queries on initial query node > --- > > Key: IGNITE-10621 > URL: https://issues.apache.org/jira/browse/IGNITE-10621 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > As of now Ignite track running queries in few places and use > GridRunningQueryInfo to keep information about each of running query. > Unfortunately we track not all running queries. Need to track all DML and > Select queries. It should be single point to track all running queries. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10621) Track all running queries on initial query node
[ https://issues.apache.org/jira/browse/IGNITE-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728696#comment-16728696 ] ASF GitHub Bot commented on IGNITE-10621: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5663 > Track all running queries on initial query node > --- > > Key: IGNITE-10621 > URL: https://issues.apache.org/jira/browse/IGNITE-10621 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > As of now Ignite track running queries in few places and use > GridRunningQueryInfo to keep information about each of running query. > Unfortunately we track not all running queries. Need to track all DML and > Select queries. It should be single point to track all running queries. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10813) Run CheckpointReadLockFailureTest with JUnit4 runner
[ https://issues.apache.org/jira/browse/IGNITE-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728686#comment-16728686 ] ASF GitHub Bot commented on IGNITE-10813: - GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5743 IGNITE-10813 Run CheckpointReadLockFailureTest with JUnit4 runner You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-10813 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5743.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5743 commit d6f17ce28ebaae85f00be188319e9833d306f80d Author: Andrey Kuznetsov Date: 2018-12-25T11:57:44Z IGNITE-10813 Changed test runner to JUnit4. > Run CheckpointReadLockFailureTest with JUnit4 runner > > > Key: IGNITE-10813 > URL: https://issues.apache.org/jira/browse/IGNITE-10813 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Kuznetsov >Assignee: Andrey Kuznetsov >Priority: Trivial > > The test fails on TeamCity. Should be run in JUnit4 manner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected
[
https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728684#comment-16728684
]
ASF GitHub Bot commented on IGNITE-10003:
-
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/5084
> Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read
> lock timeout detected
>
>
> Key: IGNITE-10003
> URL: https://issues.apache.org/jira/browse/IGNITE-10003
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Trivial
> Fix For: 2.8
>
>
> {{GridCacheDatabaseSharedManager#failCheckpointReadLock}} should report
> {{SYSTEM_WORKER_BLOCKED}} to failure handler: it is closer to the truth and
> default consequenses are not so severe as opposed to {{CRITICAL_ERROR}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10329) Create JDBC "query" and "query join" benchmarks and compare them with Postgres and MySQL
[
https://issues.apache.org/jira/browse/IGNITE-10329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728680#comment-16728680
]
ASF GitHub Bot commented on IGNITE-10329:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5479
> Create JDBC "query" and "query join" benchmarks and compare them with
> Postgres and MySQL
>
>
> Key: IGNITE-10329
> URL: https://issues.apache.org/jira/browse/IGNITE-10329
> Project: Ignite
> Issue Type: Task
> Components: sql, yardstick
>Reporter: Vladimir Ozerov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> Currently we have {{IgniteSqlQueryBenchmark}} and
> {{IgniteSqlQueryJoinBenchmark}} benchmarks which query data over salary range
> and optionally joins it with second table. Let's create a set of similar
> benchmarks which will use JDBC to load and query data, and execute them
> against one-node Ignite cluster, MySQL and Postgres.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10579) IgniteCacheContinuousQueryReconnectTest.testReconnectServer is flaky in master.
[
https://issues.apache.org/jira/browse/IGNITE-10579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728665#comment-16728665
]
ASF GitHub Bot commented on IGNITE-10579:
-
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/5591
> IgniteCacheContinuousQueryReconnectTest.testReconnectServer is flaky in
> master.
> ---
>
> Key: IGNITE-10579
> URL: https://issues.apache.org/jira/browse/IGNITE-10579
> Project: Ignite
> Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Next tests are flaky in master:
> IgniteCacheContinuousQueryReconnectTest.testReconnectServer
> IgniteCacheContinuousQueryReconnectTest.testReconnectClient
> Test exception:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<1>
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.putAndCheck(IgniteCacheContinuousQueryReconnectTest.java:111)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnect(IgniteCacheContinuousQueryReconnectTest.java:179)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnectServer(IgniteCacheContinuousQueryReconnectTest.java:93)
> {noformat}
> [Test
> history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-4837559557126450615&branch=%3Cdefault%3E&tab=testDetails]
> By logs I found that possible reason is that started node doesn't see
> cluster:
> {noformat}
> startGrid(0);
> Topology snapshot [ver=1, locNode=0b292f90, servers=1, clients=0
> startGrid(1); //client
> Topology snapshot [ver=2, locNode=0b292f90, servers=1, clients=1
> Topology snapshot [ver=2, locNode=693848f6, servers=1, clients=1
> startGrid(2);
> Topology snapshot [ver=3, locNode=0b292f90, servers=2, clients=1
> Topology snapshot [ver=3, locNode=693848f6, servers=2, clients=1
> Topology snapshot [ver=3, locNode=99a406a5, servers=2, clients=1
> stopGrid(0);
> Topology snapshot [ver=4, locNode=99a406a5, servers=1, clients=1
> Topology snapshot [ver=4, locNode=693848f6, servers=1, clients=1
> startGrid(3);
> Topology snapshot [ver=1, locNode=8d9ef192, servers=1, clients=0
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10812) SQL: split classes responsible for distributed joins
[ https://issues.apache.org/jira/browse/IGNITE-10812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728660#comment-16728660 ] ASF GitHub Bot commented on IGNITE-10812: - GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5742 IGNITE-10812 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10812 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5742.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5742 commit 35586e3955de133bfd1315e30eb60166c53bfa70 Author: devozerov Date: 2018-12-21T13:04:33Z Splitting. commit 7358f5a59c6041593db6e00c597399fcbc58f623 Author: devozerov Date: 2018-12-21T13:07:58Z WIP. commit 2460b95336e37dc54e3675ef0b2a78eb0c5e442e Author: devozerov Date: 2018-12-21T13:28:24Z WIP. commit fb29fc805bf637d11867e28b5f9ab6aa1b87adfe Author: devozerov Date: 2018-12-21T13:42:29Z WIP. commit 8c62ca73509f66058c0f097982440bbd6141241c Author: devozerov Date: 2018-12-21T13:44:24Z Moving classes. commit bc01350bd5c4f3c032d6242cdc40cd83cede824a Author: devozerov Date: 2018-12-21T13:52:48Z RangeStream. commit f8aab8effbfaa9e67748a5c7e7b6b9e176b41228 Author: devozerov Date: 2018-12-21T13:53:27Z UnicastCursor. commit cd577ac8fe2986c0ab95ab50db1562af84f32f53 Author: devozerov Date: 2018-12-21T13:55:44Z BroadcastCursor. commit 432b723bff73b37023581c80ed415864751c42e9 Author: devozerov Date: 2018-12-21T14:11:44Z WIP. commit 5e738904f36031ebfb17294cf0e96a04b45e8781 Author: devozerov Date: 2018-12-21T14:16:52Z WIP. commit 9fa48e5024453d4595f143d0040b7c030488d22d Author: devozerov Date: 2018-12-21T14:31:06Z Initial split done. commit 8dc78d795b03a97b93a829cac3b83eac2e5eb821 Author: devozerov Date: 2018-12-21T14:32:50Z WIP. commit 5c2085c91b893379e0104cdc9a8febda4a89fa3a Author: devozerov Date: 2018-12-21T14:53:33Z Minors. commit 3b90898b1da2633c48a0ac02c42c6618dca192f4 Author: devozerov Date: 2018-12-21T14:53:54Z Minors. commit 7027ef26e281ab93afe826ca8c309eb6500b2a94 Author: devozerov Date: 2018-12-21T14:57:38Z More refactoring. commit 0860542a2d33cb5b20c463cc7308a1fb84d5b946 Author: devozerov Date: 2018-12-21T14:57:57Z WIP. commit 192eb94f8becc21277d0e44833ac0dcd7328aa9f Author: devozerov Date: 2018-12-21T15:07:25Z More refactoring. commit de664052d17a652d816d0dda1369ab0108a4d2a6 Author: devozerov Date: 2018-12-21T15:08:26Z WIP. commit 26ae7895b889d91788be03d9c457e69905cb96ee Author: devozerov Date: 2018-12-25T08:19:46Z Minors. > SQL: split classes responsible for distributed joins > > > Key: IGNITE-10812 > URL: https://issues.apache.org/jira/browse/IGNITE-10812 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > > This is just a refactoring task to create more precise hierarchy of classes > responsible for distributed joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10671) Double initialization of segmentAware and FileArchiver lead to race breaking file compression.
[ https://issues.apache.org/jira/browse/IGNITE-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728640#comment-16728640 ] ASF GitHub Bot commented on IGNITE-10671: - Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/5737 > Double initialization of segmentAware and FileArchiver lead to race breaking > file compression. > -- > > Key: IGNITE-10671 > URL: https://issues.apache.org/jira/browse/IGNITE-10671 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Critical > Fix For: 2.8 > > Attachments: WalCompactionSwitchOverTest.java > > > Race is painful when you switch your cluster from walCompaction=false to > walCompaction=true. > The same FileCompressor instance will use different segmentAwares due to > start0() is called twice which leads to inconsistent behaviour and errors > during compaction, basically we will try to archive files twice concurrently. > See reproducer in attachment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10739) get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest
[
https://issues.apache.org/jira/browse/IGNITE-10739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728632#comment-16728632
]
ASF GitHub Bot commented on IGNITE-10739:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5715
> get rid of using JUnit 3 API in IgniteConfigVariationsAbstractTest
> --
>
> Key: IGNITE-10739
> URL: https://issues.apache.org/jira/browse/IGNITE-10739
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain, technical_debt
> Fix For: 2.8
>
>
> {{IgniteConfigVariationsAbstractTest}} and part of test framework that uses
> this class very heavily rely on JUnit 3 specific features.
> The task is to get rid of these and use newer versions instead - preferably
> JUnit 4, although JUnit 5 is also an option
> This will allow consistent JUnit framework version across Ignite tests which
> in turn is expected to simplify maintenance and development of the tests
> (including ignoring tests, workiing on Teamcity related things etc).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling
[
https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728619#comment-16728619
]
ASF GitHub Bot commented on IGNITE-9303:
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5741
IGNITE-9303: Fix wrong page tag usage.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9303-minor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5741.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5741
commit db978fa392229acc7db370b92f9086aee9a90b25
Author: Andrey V. Mashenkov
Date: 2018-12-25T08:33:09Z
IGNITE-9303: Fix wrong page tag usage.
> PageSnapshot can contain wrong pageId tag when not dirty page is recycling
> --
>
> Key: IGNITE-9303
> URL: https://issues.apache.org/jira/browse/IGNITE-9303
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.8
>
>
> When page is recycling (for example in {{BPlusTree.Remove#freePage()}} ->
> {{DataStructure#recyclePage()}}) tag of {{pageId}} is modified, but original
> {{pageId}} is passed to {{writeUnlock()}} method and this passed {{pageId}}
> is stored to PageSnapshot WAL record.
> This bug may lead to errors in WAL applying during crash recovery.
> Reproducer (ignite-indexing module must be in classpath):
> {code:java}
> public class WalFailReproducer extends AbstractWalDeltaConsistencyTest {
> @Override protected boolean checkPagesOnCheckpoint() {
> return true;
> }
> public final void testPutRemoveCacheDestroy() throws Exception {
> CacheConfiguration ccfg = new
> CacheConfiguration<>("cache0");
> ccfg.setIndexedTypes(Integer.class, Integer.class);
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> IgniteCache cache0 = ignite.getOrCreateCache(ccfg);
> for (int i = 0; i < 5_000; i++)
> cache0.put(i, i);
> forceCheckpoint();
> for (int i = 1_000; i < 4_000; i++)
> cache0.remove(i);
> forceCheckpoint();
> stopAllGrids();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10778) MVCC: Invoke request may hang sometimes
[
https://issues.apache.org/jira/browse/IGNITE-10778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728617#comment-16728617
]
ASF GitHub Bot commented on IGNITE-10778:
-
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5740
IGNITE-10778: Test stability improved by reducing iterations number in the
MVCC case
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10778
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5740.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5740
commit aa5a6c97ed37b7ebe281e6b1715b569b895f8ebd
Author: rkondakov
Date: 2018-12-25T08:09:33Z
IGNITE-10778: Test stability improved by reducing iterations number in the
MVCC case.
> MVCC: Invoke request may hang sometimes
> ---
>
> Key: IGNITE-10778
> URL: https://issues.apache.org/jira/browse/IGNITE-10778
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> Invoke request may hang sometimes. Reproducer:
> {{GridCacheMultinodeUpdateSelfTest.testInvoke}} with enabled MVCC.
> Stacktrace:
> {noformat}
> Thread [name="invoke-3", id=447, state=WAITING, blockCnt=0, waitCnt=1745]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.rollback(GridNearTxLocal.java:3792)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4256)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.invoke0(GridCacheAdapter.java:2608)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.invoke(GridCacheAdapter.java:2586)
> at
> o.a.i.i.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1437)
> at
> o.a.i.i.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1204)
> at
> o.a.i.i.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest$1.call(GridCacheMultinodeUpdateAbstractSelfTest.java:111)
> at
> o.a.i.i.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest$1.call(GridCacheMultinodeUpdateAbstractSelfTest.java:100)
> at o.a.i.testframework.GridTestThread.run(GridTestThread.java:84)
> Thread [name="invoke-2", id=446, state=WAITING, blockCnt=0, waitCnt=1738]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> o.a.i.i.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:841)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:723)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:578)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.invokeAsync(GridNearTxLocal.java:467)
> at
> o.a.i.i.processors.cache.GridCacheAdapter$25.op(GridCacheAdapter.java:2620)
> at
> o.a.i.i.processors.cache.GridCacheAdapter$25.op(GridCacheAdapter.java:2608)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4244)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.invoke0(GridCacheAdapter.java:2608)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.invoke(GridCacheAdapter.java:2586)
> at
> o.a.i.i.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1437)
> at
> o.a.i.i.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1204)
> at
> o.a.i.i.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest$1.call(GridCacheMultinodeUpdateAbstractSelfTest.java:111)
> at
> o.a.i.i.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest$1.call(GridCacheMultinodeUpdateAbstractSelfTest.java:100)
> at o.a.i.testframework.GridTestThread.run(GridTestThread.java:84)
> Thread [name="invoke-1", id=445, state=WAITING, blockCnt=0, waitCnt=1916]
> at sun.misc.Unsafe.park(Native Method)
>
[jira] [Commented] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests
[ https://issues.apache.org/jira/browse/IGNITE-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728613#comment-16728613 ] ASF GitHub Bot commented on IGNITE-10715: - GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5739 IGNITE-10715 Hotfix for IgniteClientConnectTest#testClientConnectToBigTopology You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-10715-hotfix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5739.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5739 commit d31e99cf0807a7dfffcb8b67f9856ce52a89369e Author: Vyacheslav Daradur Date: 2018-12-25T07:55:50Z Fixed > Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests > > > Key: IGNITE-10715 > URL: https://issues.apache.org/jira/browse/IGNITE-10715 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > It's necessary to remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in > tests since this is default IP finder in tests after IGNITE-10555. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10775) migrate from JUnit 3 to 4 test suites of simple dynamic lists that use addTestIfNeeded API
[
https://issues.apache.org/jira/browse/IGNITE-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728602#comment-16728602
]
ASF GitHub Bot commented on IGNITE-10775:
-
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/5738
IGNITE-10775 migrate from JUnit 3 to 4 test suites of simple dynamic lists
…lists that use addTestIfNeeded API
- wip
-- verified with diffs overview and rebuild
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10775
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5738.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5738
commit 6f2a025038d4c5bf7738a8fdd41828ae3bc90a14
Author: Oleg Ignatenko
Date: 2018-12-25T06:52:58Z
IGNITE-10775 migrate from JUnit 3 to 4 test suites of simple dynamic lists
that use addTestIfNeeded API
- wip
-- verified with diffs overview and rebuild
> migrate from JUnit 3 to 4 test suites of simple dynamic lists that use
> addTestIfNeeded API
> --
>
> Key: IGNITE-10775
> URL: https://issues.apache.org/jira/browse/IGNITE-10775
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> This task is to migrate from JUnit 3 to 4 test suites of simple dynamic lists
> that use {{GridTestUtils.addTestIfNeeded}} API.
> If needed, refer parent task comments for more details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10440) Analyse test suites for possible acceleration
[ https://issues.apache.org/jira/browse/IGNITE-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728525#comment-16728525 ] ASF GitHub Bot commented on IGNITE-10440: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5566 > Analyse test suites for possible acceleration > - > > Key: IGNITE-10440 > URL: https://issues.apache.org/jira/browse/IGNITE-10440 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5115) Investigation of failing tests of coordinator node failure
[
https://issues.apache.org/jira/browse/IGNITE-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728520#comment-16728520
]
ASF GitHub Bot commented on IGNITE-5115:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5391
> Investigation of failing tests of coordinator node failure
> ---
>
> Key: IGNITE-5115
> URL: https://issues.apache.org/jira/browse/IGNITE-5115
> Project: Ignite
> Issue Type: Bug
> Components: messaging
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Tests *customEventCoordinatorFailure1/2* from *TcpDiscoverySelfTest* are
> flaky on TC and sometimes hang with the following assertion in logs:
> {code}
> Exception in thread "tcp-disco-msg-worker-#5245%tcp.TcpDiscoverySelfTest0%"
> java.lang.AssertionError
> at
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing.removeNode(TcpDiscoveryNodesRing.java:353)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeFailedMessage(ServerImpl.java:4670)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2567)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2366)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6485)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2456)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> It seems that this happens because tests' implementation drops connections of
> *TcpCommunicatonSpi* on coordinator node with *simulateNodeFailure* method.
> At the same time tests leave *TcpDiscoverySpi* operational; it receives
> subsequent NodeFailed message and throws the assertion error shown above.
> The whole situation looks legitimate as it is possible to imagine a situation
> when CommSPI connections on coordinator fail for some reason while DiscoSPI
> connections are healthy.
> It is needed to investigate the situation deeper, figure out whether the root
> cause is using of *simulateNodeFailure* or not and propose a solution if the
> error may happen in the real life.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728515#comment-16728515
]
ASF GitHub Bot commented on IGNITE-9149:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4635
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
> Fix For: 2.8
>
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10671) Double initialization of segmentAware and FileArchiver lead to race breaking file compression.
[ https://issues.apache.org/jira/browse/IGNITE-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728512#comment-16728512 ] ASF GitHub Bot commented on IGNITE-10671: - GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5737 IGNITE-10671 Messed @Test annotation You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-10671 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5737.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5737 commit 966e8291dfa522ecbbad30eafc7cb4b0989866f0 Author: Vyacheslav Daradur Date: 2018-12-24T19:54:16Z Fixed > Double initialization of segmentAware and FileArchiver lead to race breaking > file compression. > -- > > Key: IGNITE-10671 > URL: https://issues.apache.org/jira/browse/IGNITE-10671 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Critical > Fix For: 2.8 > > Attachments: WalCompactionSwitchOverTest.java > > > Race is painful when you switch your cluster from walCompaction=false to > walCompaction=true. > The same FileCompressor instance will use different segmentAwares due to > start0() is called twice which leads to inconsistent behaviour and errors > during compaction, basically we will try to archive files twice concurrently. > See reproducer in attachment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10448) MVCC: NPE on data page eviction.
[
https://issues.apache.org/jira/browse/IGNITE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728436#comment-16728436
]
ASF GitHub Bot commented on IGNITE-10448:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5704
> MVCC: NPE on data page eviction.
>
>
> Key: IGNITE-10448
> URL: https://issues.apache.org/jira/browse/IGNITE-10448
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
> Fix For: 2.8
>
>
> NPE occurred during page eviction process.
> Reproducer: {{PageEvictionMultinodeMixedRegionsTest}}.
> StackTrace:
>
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.createCacheAndTestEvcition(PageEvictionMultinodeAbstractTest.java:101)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.testPageEviction(PageEvictionMultinodeAbstractTest.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.transactions.TransactionRollbackException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:923)
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:921)
> ... 15 more
> Caused by: class
> org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4299)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2520)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2501)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2478)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> backup node: [localNodeId=0d817370-17fe-46f1-85ef-ea74b6f1,
> remoteNodeId=ebab34f3-abbc-47e9-90fa-a48a8260]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2340)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
>
[jira] [Commented] (IGNITE-10238) Intermittent Client Nodes suite hang
[
https://issues.apache.org/jira/browse/IGNITE-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728408#comment-16728408
]
ASF GitHub Bot commented on IGNITE-10238:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5439
> Intermittent Client Nodes suite hang
>
>
> Key: IGNITE-10238
> URL: https://issues.apache.org/jira/browse/IGNITE-10238
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Amelchev Nikita
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> There are occasional hangs of Client Nodes suite in master. A quick peek at
> the thread dumps reveals an interesting deadlock (only relevant parts of the
> thread dump are left):
> {code}
> "disco-notifier-worker-#634%internal.IgniteClientReconnectApiExceptionTest0%"
> #791 prio=5 os_prio=0 tid=0x7f990c12d800 nid=0x11b9 waiting on condition
> [0x7f991a0eb000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:656)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$1.metadata(CacheObjectBinaryProcessorImpl.java:206)
> at
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1293)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:101)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:81)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10131)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10160)
> at
> org.apache.ignite.internal.GridEventConsumeHandler.p2pUnmarshal(GridEventConsumeHandler.java:390)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1362)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:111)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:203)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:194)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:725)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(Gr
[jira] [Commented] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728361#comment-16728361 ] ASF GitHub Bot commented on IGNITE-10594: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5605 > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728362#comment-16728362 ] ASF GitHub Bot commented on IGNITE-10594: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5736 > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728360#comment-16728360 ] ASF GitHub Bot commented on IGNITE-10594: - GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/5736 IGNITE-10594 Remove specific JSR310 handling, add java.time test to r… …egular suite. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10594bis Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5736.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5736 commit 15632b37c2bff2713134f92b196d28220cecfdc8 Author: Ilya Kasnacheev Date: 2018-12-07T14:16:40Z IGNITE-10594 Remove specific JSR310 handling, add java.time test to regular suite. > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests
[ https://issues.apache.org/jira/browse/IGNITE-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728356#comment-16728356 ] ASF GitHub Bot commented on IGNITE-10715: - Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/5699 > Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests > > > Key: IGNITE-10715 > URL: https://issues.apache.org/jira/browse/IGNITE-10715 > Project: Ignite > Issue Type: Task >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > It's necessary to remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in > tests since this is default IP finder in tests after IGNITE-10555. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10130) Add option for disable triggering cache interceptor in case of conflicts.
[ https://issues.apache.org/jira/browse/IGNITE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728355#comment-16728355 ] ASF GitHub Bot commented on IGNITE-10130: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5251 > Add option for disable triggering cache interceptor in case of conflicts. > - > > Key: IGNITE-10130 > URL: https://issues.apache.org/jira/browse/IGNITE-10130 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > Interceptor semantic for Dr updates looks broken. > For now, Ignite call post-update interceptor methods for Dr updates and there > is no way to disable interceptor calls at all. > This force user to call onGet before sending entry to remote DR that may be > inefficient. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10785) MVCC: Grid can hang if transaction is failed to rollback
[
https://issues.apache.org/jira/browse/IGNITE-10785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728343#comment-16728343
]
ASF GitHub Bot commented on IGNITE-10785:
-
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5735
IGNITE-10785: Test was reworked to prevent hanging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10785
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5735.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5735
commit 8d569f123e3767049319ee02f0b3fae8fd013948
Author: rkondakov
Date: 2018-12-24T11:38:43Z
IGNITE-10785: Test was reworked to prevent hanging.
> MVCC: Grid can hang if transaction is failed to rollback
>
>
> Key: IGNITE-10785
> URL: https://issues.apache.org/jira/browse/IGNITE-10785
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: Hanging, mvcc_stabilization_stage_1, transactions
>
> Sometimes grid can hang if transactions is failed to rollback. Reproducer:
>
> {noformat}
> [2018-12-14 08:48:13,890][WARN
> ][sys-stripe-9-#12552%transactions.TxRollbackAsyncWithPersistenceTest2%][GridDhtColocatedCache]
> Failed to acquire lock (transaction has been completed):
> GridCacheVersion [topVer=156257270, order=1544777270268, nodeOrder=4]
> [2018-12-14
> 08:48:13,893][ERROR][sys-stripe-9-#12552%transactions.TxRollbackAsyncWithPersistenceTest2%][GridDhtColocatedCache]
> Failed to rollback the transaction: GridDhtTxLocal
> [nearNodeId=b4ff2bcc-dc6a-49c2-a2ab-f26bae6b68c1,
> nearFutId=282d09ca761-8ff10d65-a1d6-4f40-9fd7-afb7afa0b25c, nearMiniId=1,
> nearFinFutId=382d09ca761-8ff10d65-a1d6-4f40-9fd7-afb7afa0b25c,
> nearFinMiniId=1, nearXidVer=GridCacheVersion [topVer=156257270,
> order=1544777270268, nodeOrder=4], lb=null, super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView
> [], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null,
> sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl
> [activeCacheIds=[], recovery=null, mvccEnabled=null, txMap=HashSet []],
> mvccWaitTxs=null, qryEnlisted=false, forceSkipCompletedVers=false,
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=156257270,
> order=1544777270269, nodeOrder=3], writeVer=null, implicit=false, loc=true,
> threadId=13949, startTime=1544777293884,
> nodeId=cb0ed489-aa1c-4e7a-a196-3bea9e52, startVer=GridCacheVersion
> [topVer=156257270, order=1544777270269, nodeOrder=3], endVer=null,
> isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0,
> sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion
> [topVer=156257270, order=1544777270269, nodeOrder=3], finalizing=NONE,
> invalidParts=null, state=ROLLED_BACK, timedOut=false,
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0],
> mvccSnapshot=MvccSnapshotResponse [futId=82, crdVer=1544777266400, cntr=848,
> opCntr=1, txs=[640, 769, 706, 387, 707, 708, 582, 646, 583, 586, 847, 596,
> 660, 724, 661, 598, 599, 603, 667, 731, 685, 494, 686, 688, 561, 629, 570,
> 766, 639], cleanupVer=263, tracking=0], parentTx=null, duration=0ms,
> onePhaseCommit=false], size=0]]]
> class org.apache.ignite.IgniteCheckedException: Failed to finish transaction
> [commit=false,
> tx=GridDhtTxLocal[xid=df386eba761--0950-4bf6--0003,
> xidVersion=GridCacheVersion [topVer=156257270, order=1544777270269,
> nodeOrder=3], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=ROLLED_BACK, invalidate=false, rollbackOnly=true,
> nodeId=cb0ed489-aa1c-4e7a-a196-3bea9e52, timeout=0, duration=0]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:482)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.rollbackDhtLocalAsync(GridDhtTxLocal.java:588)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.rollbackDhtLocal(GridDhtTxLocal.java:563)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.initTxTopologyVersion(GridDhtTransactionalCacheAdapter.java:2178)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxEnlistRequest(GridDhtTransactionalCacheAdapter.java:2016)
> at
> org.apache.ignite.internal.processors.cache
[jira] [Commented] (IGNITE-10800) Add wal_mode parameter to yardstick properties file
[ https://issues.apache.org/jira/browse/IGNITE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728321#comment-16728321 ] ASF GitHub Bot commented on IGNITE-10800: - GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/5734 IGNITE-10800 added WAL mode parameter and warning message You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10800 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5734.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5734 commit 6d298d99410bb9e4fdadbb2979a51cb1e292484d Author: oleg-ostanin Date: 2018-12-24T10:33:06Z IGNITE-10800 added WAL mode parameter and warning message > Add wal_mode parameter to yardstick properties file > --- > > Key: IGNITE-10800 > URL: https://issues.apache.org/jira/browse/IGNITE-10800 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Affects Versions: 2.7 >Reporter: Ilya Suntsov >Assignee: Oleg Ostanin >Priority: Major > > As I understand we can enable persistence with properties file parameter. I > guess we need to add a parameter for WAL mode. > Expected behavior: > * When we have in configuration region with persistence should be used this > configuration and wal_mode value from properties should be ignored. Also > should be added warnings in all nodes logs with configuration details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10671) Double initialization of segmentAware and FileArchiver lead to race breaking file compression.
[ https://issues.apache.org/jira/browse/IGNITE-10671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728313#comment-16728313 ] ASF GitHub Bot commented on IGNITE-10671: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5665 > Double initialization of segmentAware and FileArchiver lead to race breaking > file compression. > -- > > Key: IGNITE-10671 > URL: https://issues.apache.org/jira/browse/IGNITE-10671 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Critical > Fix For: 2.8 > > Attachments: WalCompactionSwitchOverTest.java > > > Race is painful when you switch your cluster from walCompaction=false to > walCompaction=true. > The same FileCompressor instance will use different segmentAwares due to > start0() is called twice which leads to inconsistent behaviour and errors > during compaction, basically we will try to archive files twice concurrently. > See reproducer in attachment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10779) PagesWriteThrottleSmokeTest.testThrottle is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728257#comment-16728257
]
ASF GitHub Bot commented on IGNITE-10779:
-
Github user zzzadruga closed the pull request at:
https://github.com/apache/ignite/pull/5722
> PagesWriteThrottleSmokeTest.testThrottle is flaky
> -
>
> Key: IGNITE-10779
> URL: https://issues.apache.org/jira/browse/IGNITE-10779
> Project: Ignite
> Issue Type: Task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Sometimes, at poor checkpoint write speed, put rate degrated to zero for at
> least 10 seconds with write throttling enabled. Success rate on TC = 87%.
> [Test
> details|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2808794487465215609&tab=testDetails]
> {code:java}
> junit.framework.AssertionFailedError: Put rate degraded to zero for at least
> 10 seconds
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PagesWriteThrottleSmokeTest.testThrottle(PagesWriteThrottleSmokeTest.java:217)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2209)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Test became flaky after IGNITE-10028.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10279) Control.sh utility unify options naming format
[
https://issues.apache.org/jira/browse/IGNITE-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728239#comment-16728239
]
ASF GitHub Bot commented on IGNITE-10279:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5672
> Control.sh utility unify options naming format
> --
>
> Key: IGNITE-10279
> URL: https://issues.apache.org/jira/browse/IGNITE-10279
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> Now we have options in several styles:
> {noformat}
> --ping-interval
> {noformat}
> {noformat}
> --skipZeros
> {noformat}
> I think, we must unify options naming format and we should use linux like
> format, i.e. {{--word1-word2}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10774) migrate test suites that are fixed lists of test classes from Junit 3 to 4
[ https://issues.apache.org/jira/browse/IGNITE-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727573#comment-16727573 ] ASF GitHub Bot commented on IGNITE-10774: - GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5732 IGNITE-10774 migrate test suites that are fixed lists of test classes from Junit 3 to 4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10774 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5732.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5732 commit ff4699bebf2571cbd648cbf8bccf1e957c7547e5 Author: Oleg Ignatenko Date: 2018-12-02T23:35:51Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - added @Test -- verified with diffs overview commit a72e24ea010fd7333b7425c349e3de1373aed0fc Author: Oleg Ignatenko Date: 2018-12-03T00:24:34Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit eeeba1cc2f9d9dc02065c19c7c1079008bf73e00 Author: Oleg Ignatenko Date: 2018-12-03T00:26:13Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 9304b5f31ef712708be7d04b68a963d8bf4b050d Author: Oleg Ignatenko Date: 2018-12-03T00:29:51Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 7eaf7a0252fb347f19d192859c410c3c29f7c4b6 Author: Oleg Ignatenko Date: 2018-12-03T00:39:54Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit eaee42ebf611c1617993177d6466e81399c3ebdc Author: Oleg Ignatenko Date: 2018-12-03T00:48:56Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 62738a3820d4057a9c34ad8b2c6e85959ebfc67e Author: Oleg Ignatenko Date: 2018-12-03T00:57:00Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit afb495f9e97e6e15b0c4c29f6d57dd2bbd569f1c Author: Oleg Ignatenko Date: 2018-12-03T08:39:38Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3b56b742b52a516a4244d2a07635a99d9abeba18 Author: Oleg Ignatenko Date: 2018-12-03T09:06:45Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3835772a72a99882f9d6cd2557001c9db94ed416 Author: Oleg Ignatenko Date: 2018-12-03T09:31:45Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit ac6be2c4e07748f34da5d83ce3e9f20786ead2fc Author: Oleg Ignatenko Date: 2018-12-03T10:46:59Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 9f663a9c857f76fcb0e56c194cc2d6ec10f6888b Author: Oleg Ignatenko Date: 2018-12-03T11:13:26Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit e2eae3201a88c3d9800b9964ce9ca4096ed3d85f Author: Oleg Ignatenko Date: 2018-12-03T11:31:35Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit f9ccc80de28fb2fc64c96d695f5f906a8cd9a946 Author: Oleg Ignatenko Date: 2018-12-03T12:40:21Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 3eadd0abf6f58a0a3d8fe8464bb08879d412bca1 Author: Oleg Ignatenko Date: 2018-12-03T13:33:00Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 28d9f854993cb99867803cfe0126cf723e071cc5 Author: Oleg Ignatenko Date: 2018-12-03T13:54:52Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit ed54719377f694d0111740c0bbd92dcf5294e6c6 Author: Oleg Ignatenko Date: 2018-12-03T14:10:26Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit fb97a8c23881d1d1c50423dcea6ac519a36c195a Author: Oleg Ignatenko Date: 2018-12-03T14:26:19Z IGNITE-10175 migrate core module tests from Junit 3 to 4 - wip - migrating -- verified with diffs overview commit 063f7ae0164924a775b4235ebd0f704017bc2c73 Author: Oleg Ignatenko Date: 2018-12-03T14:45:00Z IGNITE-10175 migra
[jira] [Commented] (IGNITE-10177) cleanup Junit 3 from the project
[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727349#comment-16727349
]
ASF GitHub Bot commented on IGNITE-10177:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5615
> cleanup Junit 3 from the project
>
>
> Key: IGNITE-10177
> URL: https://issues.apache.org/jira/browse/IGNITE-10177
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps for various reasons:
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> ## find out why {{IgniteTwitterStreamerTest}} runs fine under JUnit 3 but
> starts failing after move to JUnit 4
> ## IgniteCachePartitionedQuerySelfTest,
> IgniteCacheReplicatedQueryP2PDisabledSelfTest, ComputeUtilsTest,
> CacheBasedDatasetBuilderTest, CacheBasedDatasetTest,
> GridPartitionedCacheJtaLookupClassNameSelfTest,
> GridReplicatedCacheJtaLookupClassNameSelfTest (there were problems migrating
> these at IGNITE-10176)
> ## find out why tests in logging suite failed on teamcity (not locally) when
> setup method was annotated {{@Before}}
> ## (!) note part of this work related to
> {{IgniteConfigVariationsAbstractTest}} is expected to be done separately per
> IGNITE-10739
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (i) per discussion with [~EdShangGG] plan to to do this in a separate
> ticket for smoother merges - IGNITE-10758
> Side note if for some reason it turns out critically important to keep test
> suites names (by default Junit 4 will use suite class names instead),
> approach with custom description annotation [described
> here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
> can be used to address that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10316) control.sh --baseline remove outputs wrong error message when trying to remove node from baseline when cluster is inactive.
[
https://issues.apache.org/jira/browse/IGNITE-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727020#comment-16727020
]
ASF GitHub Bot commented on IGNITE-10316:
-
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5730
IGNITE-10316 control.sh --baseline remove outputs wrong error message…
… when trying to remove node from baseline when cluster is inactive.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10316
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5730.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5730
commit 03f14959ef6d951656a40ef7eb3d034120f6a182
Author: vd_pyatkov
Date: 2018-12-21T20:02:19Z
IGNITE-10316 control.sh --baseline remove outputs wrong error message when
trying to remove node from baseline when cluster is inactive.
> control.sh --baseline remove outputs wrong error message when trying to
> remove node from baseline when cluster is inactive.
> ---
>
> Key: IGNITE-10316
> URL: https://issues.apache.org/jira/browse/IGNITE-10316
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Priority: Major
>
> 1. start 2 nodes from clean lfs
> 2. grep node consistent ids
> {noformat}
> $ grep "Consistent ID" work/log/*.log
> work/log/ignite-15958745.0.log:[16:59:13,190][INFO][main][PdsFoldersResolver]
> Consistent ID used for local node is [7ee8018b-3f5f-4c58-b6dd-f53ed7af2679]
> according to persistence data storage folders
> work/log/ignite-300c7412.0.log:[16:59:15,678][INFO][main][PdsFoldersResolver]
> Consistent ID used for local node is [5adcf3a1-7ad9-40fa-88ac-40b488dc6b34]
> according to persistence data storage folders
> {noformat}
> 3. try to remove node from baseline
> expected: error message about cluster inactive state
> actual: error message about node id not found, BUG
> {noformat}
> Caused by: java.lang.IllegalStateException: Node not found for consistent ID:
> 7ee8018b-3f5f-4c58-b6dd-f53ed7af2679
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.remove(VisorBaselineTask.java:178)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:208)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:52)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> ... 19 more
> {noformat}
> however, when trying to add node to baseline, error message is correct:
> {noformat}
> Caused by: class org.apache.ignite.IgniteException: Changing BaselineTopology
> on inactive cluster is not allowed.
> at
> org.apache.ignite.internal.cluster.IgniteClusterImpl.validateBeforeBaselineChange(IgniteClusterImpl.java:406)
> at
> org.apache.ignite.internal.cluster.IgniteClusterImpl.setBaselineTopology(IgniteClusterImpl.java:356)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.set0(VisorBaselineTask.java:87)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.add(VisorBaselineTask.java:162)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:205)
> at
> org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:52)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1407)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTask
[jira] [Commented] (IGNITE-10599) Add test for Scheduler Example to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726867#comment-16726867 ] ASF GitHub Bot commented on IGNITE-10599: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5610 > Add test for Scheduler Example to LGPL Examples suite > - > > Key: IGNITE-10599 > URL: https://issues.apache.org/jira/browse/IGNITE-10599 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Fix For: 2.8 > > > Currently we in LGPL Examples suite we have Hibernate example test and > Geospatial example test but no Scheduler test. We need to add it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10658) Rebalance status in Visor stays on 99.99%.
[ https://issues.apache.org/jira/browse/IGNITE-10658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726842#comment-16726842 ] ASF GitHub Bot commented on IGNITE-10658: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5706 > Rebalance status in Visor stays on 99.99%. > -- > > Key: IGNITE-10658 > URL: https://issues.apache.org/jira/browse/IGNITE-10658 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > > There are log messages about finishing rebalance: > 2018-07-06 02:25:53.976[INFO > ][sys-#1365%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#1365%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > [REB]Fin reb part CACHEGROUP_PARTICLE_union-module_ru.sbt.pprb.unif > .formats.UnifDictionary, p=GridDhtLocalPartition [rmvQueueMaxSize=32, > rmvdEntryTtl=1, id=10698, delayedRenting=false, clear=false, > updateSeqOnDestroy=false, grp=CACHEGROUP_PART > ICLE_union-module_ru.sbt.pprb.unif.formats.UnifDictionary, state=MOVING, > reservations=1, empty=true, createTime=07/05/2018 23:30:40], > dir=[topVer=(351, 0), idx=6, sup=10.126.12.142 > :47500] > 2018-07-06 02:25:53.976[INFO > ][sys-#1365%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#1365%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander]Completed > (final) rebalancing [fromNode=d38ca303-91a3-4805-b2bc-8231 > 721924e2, > cacheOrGroup=CACHEGROUP_PARTICLE_union-module_ru.sbt.pprb.unif.formats.UnifDictionary, > topology=AffinityTopologyVersion [topVer=351, minorTopVer=0], time=20 ms] > 2018-07-06 02:25:53.976[INFO > ][sys-#1365%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#1365%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander]Completed > rebalance future: RebalanceFuture [grp=CacheGroupContext [ > grp=CACHEGROUP_PARTICLE_union-module_ru.sbt.pprb.unif.formats.UnifDictionary], > topVer=AffinityTopologyVersion [topVer=351, minorTopVer=0], rebalanceId=2018] > 2018-07-06 02:25:53.977[INFO > ][sys-#1365%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#1365%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]WAL > enabled for [grp=CACHEGROUP_PARTICLE_union-module_ru.sbt.pprb. > unif.formats.UnifDictionary] > But Visor still showed 99,99% status on that node. > Later on when a client node left topology Visor status has changed to > Rebalnce completed > See log messages: > 2018-07-06 02:57:46.629[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time]Started > exchange init [topVer=AffinityTopologyVersion [topVer=352, > minorTopVer=0], crd=false, evt=NODE_LEFT, > evtNode=1d2dcbc7-f143-42cd-9130-145e4c199c0e, customEvt=null, allowMerge=true] > 2018-07-06 02:57:47.376[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq BGP_BGPConfigurationImpl_gbk-main -> 243 [A > FTER_EXCHANGE] > 2018-07-06 02:57:47.376[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq BGP_ExpiryEntryImpl_BGP -> 243 [AFTER_EXCHA > NGE] > 2018-07-06 02:57:47.376[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq CACHEGROUP_PARTICLE_union-module_com.sbt.ca > rd.cdm.api.dictionaries.sys.PartitioningCriteriaTen -> 1158 [AFTER_EXCHANGE] > 2018-07-06 02:57:47.383[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq CACHEGROUP_PARTICLE_union-module_ru.sbrf.au > totransact.model.keys.DateKey -> 1157 [AFTER_EXCHANGE] > 2018-07-06 02:57:47.390[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq CACHEGROUP_PARTICLE_union-module_com.sbt.tw > .data.dpl.entity.ServiceZone -> 1159 [AFTER_EXCHANGE] > 2018-07-06 02:57:47.397[INFO > ][exchange-worker-#152%DPL_GRID%DplGridNodeName%|https://ggsystems.atlassian.net/browse/GG-13983#152%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] > Top upd seq CACHEGROUP_PARTICLE_union-module_com.sbt.ac > quiring.proces
[jira] [Commented] (IGNITE-9303) PageSnapshot can contain wrong pageId tag when not dirty page is recycling
[
https://issues.apache.org/jira/browse/IGNITE-9303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726831#comment-16726831
]
ASF GitHub Bot commented on IGNITE-9303:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5580
> PageSnapshot can contain wrong pageId tag when not dirty page is recycling
> --
>
> Key: IGNITE-9303
> URL: https://issues.apache.org/jira/browse/IGNITE-9303
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Aleksey Plekhanov
>Assignee: Ilya Lantukh
>Priority: Major
> Fix For: 2.8
>
>
> When page is recycling (for example in {{BPlusTree.Remove#freePage()}} ->
> {{DataStructure#recyclePage()}}) tag of {{pageId}} is modified, but original
> {{pageId}} is passed to {{writeUnlock()}} method and this passed {{pageId}}
> is stored to PageSnapshot WAL record.
> This bug may lead to errors in WAL applying during crash recovery.
> Reproducer (ignite-indexing module must be in classpath):
> {code:java}
> public class WalFailReproducer extends AbstractWalDeltaConsistencyTest {
> @Override protected boolean checkPagesOnCheckpoint() {
> return true;
> }
> public final void testPutRemoveCacheDestroy() throws Exception {
> CacheConfiguration ccfg = new
> CacheConfiguration<>("cache0");
> ccfg.setIndexedTypes(Integer.class, Integer.class);
> IgniteEx ignite = startGrid(0);
> ignite.cluster().active(true);
> IgniteCache cache0 = ignite.getOrCreateCache(ccfg);
> for (int i = 0; i < 5_000; i++)
> cache0.put(i, i);
> forceCheckpoint();
> for (int i = 1_000; i < 4_000; i++)
> cache0.remove(i);
> forceCheckpoint();
> stopAllGrids();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10543) [ML] Test/train sample generator
[ https://issues.apache.org/jira/browse/IGNITE-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726817#comment-16726817 ] ASF GitHub Bot commented on IGNITE-10543: - GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/5727 IGNITE-10543: Test/train sample generator You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10543 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5727.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5727 commit 89adcac542003dd5f82fc34355700ab044be6d91 Author: Alexey Platonov Date: 2018-12-07T16:27:10Z init commit commit 7d5e8f170e79c07b5e67b778c371db0b69c978e7 Author: Alexey Platonov Date: 2018-12-13T16:50:15Z add gaussian datastream refactoring bug fix in circles datastream commit cbf1b8975e60fcd11797bede29d6e7d935e3951a Author: Alexey Platonov Date: 2018-12-14T15:05:22Z refactoring add primitives commit 38e15c44fef846224e4db00b374e434593974ff8 Author: Alexey Platonov Date: 2018-12-14T20:36:27Z refactoring commit 7ae3ebbca7081bba34d5dfb6624cce79a77ac78d Author: Alexey Platonov Date: 2018-12-14T20:38:08Z refactoring commit 52d08457a4d9dd23a2d0afbce2ae82e29cdb34ef Author: Alexey Platonov Date: 2018-12-14T21:00:57Z refactoring commit 7a094e6b6f899f09906e0009d140bf1f20ad6363 Author: Alexey Platonov Date: 2018-12-15T09:21:50Z add regression commit d49331a5002cce39622929eccae291d5238d5b26 Author: Alexey Platonov Date: 2018-12-17T08:24:51Z WIP commit 3c446fb6ef0e1debc59c5078308c31519eef6549 Author: Alexey Platonov Date: 2018-12-17T12:54:10Z add dataset builder adapter commit d596d89b65614eec43647c8bbf774c7b7b0117c8 Author: Alexey Platonov Date: 2018-12-18T08:02:13Z add vectorize method to RandomProducer-s commit f0358554df1e759f39ba181c38d5568f2e4501b6 Author: Alexey Platonov Date: 2018-12-18T13:56:08Z yet another refactoring commit 8840c3f6be07fe8f6552b63e8f7694e546d91858 Author: Alexey Platonov Date: 2018-12-19T10:03:06Z add generators combinators commit 3efd87190b20244b451011f43398d1011e502dd6 Author: Alexey Platonov Date: 2018-12-19T13:09:29Z add generators combinators commit 607a9758fb447e7b3d24912b4f13d4506d6ee432 Author: Alexey Platonov Date: 2018-12-19T14:24:15Z add assertions commit ca5ba410fb82729c10cf97ceebec69f394047afd Author: Alexey Platonov Date: 2018-12-20T11:37:34Z add mapper of family commit 69c04ddf67045ae9d54ef8b836074029d6e080c2 Author: Alexey Platonov Date: 2018-12-20T13:53:02Z add primitives refactoring bug fix of uniform random commit 01fb913e6b6af8b307e788377ef94d35df379ef0 Author: Alexey Platonov Date: 2018-12-20T17:04:09Z tests for random producers commit 918d887ac791fa1257f852580009da12f17ae6c6 Author: Alexey Platonov Date: 2018-12-20T17:49:23Z tests for VectorGenerator manipulators commit e7521b93c968b3a7552434dbf3f9831b05944ae8 Author: Alexey Platonov Date: 2018-12-20T18:07:19Z tests for primitives commit d160a1780223ccd3cf2e44700f6746eb70da3049 Author: Alexey Platonov Date: 2018-12-20T18:09:44Z remove redundant code commit 448a75eadbbac4de57417c13c7ff55b0ec1f6718 Author: Alexey Platonov Date: 2018-12-21T07:55:05Z add tests commit 0c5d1848f1fa7568dedcbc8f1b4507ca76bb6f6c Author: Alexey Platonov Date: 2018-12-21T08:38:37Z use primitives in standart DataStreams commit eb49d81a69f7f3b42d7f380f8819b14ada963512 Author: Alexey Platonov Date: 2018-12-21T08:46:31Z Merge branch 'master' of https://github.com/apache/ignite into ignite-10543 # Conflicts: # modules/ml/src/main/java/org/apache/ignite/ml/math/primitives/vector/VectorUtils.java commit ceecc3ca36f94558f555c4af7ba63b51b39e9ac3 Author: Alexey Platonov Date: 2018-12-21T11:49:15Z refactoring tests for DataStreamGenerator commit 0db299f8b987e4af9d21672a12121e40d7dd5aca Author: Alexey Platonov Date: 2018-12-21T11:50:00Z reformat code commit b9c16678c4ff9e8385d35ff297e68aa73c520b93 Author: Alexey Platonov Date: 2018-12-21T12:04:43Z add package-infos commit 376e702f85292e33f35eb76fa92544cf26f786f2 Author: Alexey Platonov Date: 2018-12-21T12:23:12Z javadocs WIP commit a1e20c40a848f2ae3af0227af3fefe5e200ca1d8 Author: Alexey Platonov Date: 2018-12-21T12:46:48Z javadocs WIP commit 37fd575d686a926f344b0a5403925ba11292104a Author: Alexey Platonov Date: 2018-12-21T14:48:40Z javadocs WIP commit 6b98663d0cde3b5cb0d1ec98411c82fb9f1a3da7 Author: Alexey Platonov Date: 2018-12-21T15:07:45Z javadocs WIP > [ML] Test/train sample
