[jira] [Commented] (IGNITE-7298) Web console: error on web agent start in case if demo is opened in browser
[
https://issues.apache.org/jira/browse/IGNITE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523142#comment-16523142
]
Andrey Novikov commented on IGNITE-7298:
Demo mode was broken after merge of
https://issues.apache.org/jira/browse/IGNITE-8428. Please await fix, and try
again.
> Web console: error on web agent start in case if demo is opened in browser
> --
>
> Key: IGNITE-7298
> URL: https://issues.apache.org/jira/browse/IGNITE-7298
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.6
>
>
> {code}
> [ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
> config/java.util.logging.properties
> Console logging handler is not configured.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8428) Web Console: Support connect to secured cluster
[ https://issues.apache.org/jira/browse/IGNITE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-8428: -- Assignee: Pavel Konstantinov (was: Andrey Novikov) Fix Version/s: (was: 2.7) 2.6 Affects Version/s: 2.6 Fixed demo mode. [~pkonstantinov], please test. > Web Console: Support connect to secured cluster > --- > > Key: IGNITE-8428 > URL: https://issues.apache.org/jira/browse/IGNITE-8428 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.6 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.6 > > > See: > https://stackoverflow.com/questions/50065120/how-to-add-security-to-run-ignite-web-console-in-k8s -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-8428) Web Console: Support connect to secured cluster
[ https://issues.apache.org/jira/browse/IGNITE-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reopened IGNITE-8428: Assignee: Andrey Novikov (was: Pavel Konstantinov) After this changes, demo mode is not working (always throw error: Failed to execute request on cluster). > Web Console: Support connect to secured cluster > --- > > Key: IGNITE-8428 > URL: https://issues.apache.org/jira/browse/IGNITE-8428 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.7 > > > See: > https://stackoverflow.com/questions/50065120/how-to-add-security-to-run-ignite-web-console-in-k8s -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8745) Add ability to monitor TCP discovery ring information
[ https://issues.apache.org/jira/browse/IGNITE-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523101#comment-16523101 ] ASF GitHub Bot commented on IGNITE-8745: GitHub user ezagumennov opened a pull request: https://github.com/apache/ignite/pull/4256 IGNITE-8745 Make tcp-disco-worker thread name reflect the node to whi… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8745 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4256.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 #4256 commit b9f1f01d6319166f22142f66638c290b534e0f7d Author: ezagumennov Date: 2018-06-13T08:45:30Z IGNITE-8745 Make tcp-disco-worker thread name reflect the node to which the local node is connected. Add a method on TCP discovery MBean to return current topology version. Dump ring structure > Add ability to monitor TCP discovery ring information > - > > Key: IGNITE-8745 > URL: https://issues.apache.org/jira/browse/IGNITE-8745 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Evgenii Zagumennov >Priority: Major > > We should add the following modifications: > 1) Add a method on TCP discovery MBean to dump the ring structure on local > node and on all nodes in the grid > 2) Make tcp-disco-worker thread name reflect the node to which the local node > is connected > 3) Add a method on TCP discovery MBean to return current topology version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8768) JVM crash in PDS1 suite in master branch
[ https://issues.apache.org/jira/browse/IGNITE-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522927#comment-16522927 ] Pavel Kovalenko edited comment on IGNITE-8768 at 6/25/18 11:10 PM: --- [~agoncharuk] Your concern has fixed. Could you please look at the changes again? was (Author: jokser): [~agoncharuk] Your concert has fixed. Could you please look at the changes again? > JVM crash in PDS1 suite in master branch > > > Key: IGNITE-8768 > URL: https://issues.apache.org/jira/browse/IGNITE-8768 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.4, 2.5 >Reporter: Sergey Chugunov >Assignee: Pavel Kovalenko >Priority: Blocker > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > JVM crash in latest build: [TC > link|https://ci.ignite.apache.org/viewLog.html?buildId=1372456=buildResultsDiv=IgniteTests24Java8_Pds1] > It is the first crash is latest 15 builds: [TC > link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8856) Incorrect behavior of BinaryTypeConfiguration in case of using a wildcard for type names
[
https://issues.apache.org/jira/browse/IGNITE-8856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-8856:
Summary: Incorrect behavior of BinaryTypeConfiguration in case of using a
wildcard for type names (was: Incorrect behavior of BinaryTypeConfiguration in
case of using a wildcard fro type names)
> Incorrect behavior of BinaryTypeConfiguration in case of using a wildcard for
> type names
>
>
> Key: IGNITE-8856
> URL: https://issues.apache.org/jira/browse/IGNITE-8856
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.5
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
>
> Let's consider the following BinaryConfiguration:
> {code:java}
>
>
> ...
>
>
> class="org.apache.ignite.binary.BinaryTypeConfiguration">
> value="org.apache.ignite.examples.*"/>
>
> class="org.apache.ignite.binary.BinaryBasicNameMapper">
> value="false"/>
>
>
>
>
>
>
>
> {code}
> My intention is using custom BinaryBasicMapper for all classes in the
> specified package and its sub packages,
> but BinaryContext implementation matches only classes that reside in the
> "org.apache.ignite.examples" package.
> Classes from subpackages are not matched, and therefore do not use the
> specified BinaryBasicNameMapper.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6055) SQL: Add String length constraint
[ https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522719#comment-16522719 ] Nikolay Izhikov edited comment on IGNITE-6055 at 6/25/18 7:34 PM: -- [~vozerov] > 1) > org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor#toQueryEntity > - this check is redundant, we should check whether QueryEntity is valid on > cache start, not inside DDL (to handle both DDL and cache create through API > in the same place). See > org.apache.ignite.internal.processors.query.QueryUtils#validateQueryEntity Fixed. > 2) I am not very happy with precision/scale/maxLength properties - too much > of them. Instead, we can re-use "precision" for String length. H2 works this > way (see their docs), so it should be ok for us as well. In fact, this is why > GridSqlColumn.maxLength() return the same value as GridSqlColumn.precision() Fixed. > 3) QueryEntity - getters should return current value, without wrapping it > into unmodifiable collection, because this is how users frequently use us - > QueryEntity.getNotNullFields().add(...) Fixed. > 4) Let's split single decimal property into "scale" and "precision". Because > single precision would be needed not only for strings, but for other data > types as well (e.g. DOUBLE, REAL, BINARY) Fixed. > 6) QueryBinaryProperty, QueryTypeDescriptorImpl, QueryUtils - checks for > "_KEY" and "_VAL" are illegal, because key/val field names could be overriden > with QueryEntity.keyFieldName/valFieldName. These checks should be more > generic Fixed. > 7) QueryBinaryProperty.value() - new logic around key/val should be removed > as it breaks an invariant that only nested fields can be read/written here. > Please find a way to perform a check on key/value without changing central > field extraction logic. FIxed. > 8) We need more tests for cache API. E.g. I do not see tests for invoke(). Tests added. > 5) I do not see how compatibility is handled in .NET - new fields are > serialized unconditionally, meaning that we cannot talk to previous version. > Am I wrong? Do we have compatibility for a .Net client? I don't see any conditional logic for a "default field value" implementation [1]. Can you give me an example of such logic? Please, review the PR. [1] [https://github.com/apache/ignite/commit/78e79e011f1bb017653e628587faf606cfd37510] was (Author: nizhikov): > 1) > org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor#toQueryEntity > - this check is redundant, we should check whether QueryEntity is valid on > cache start, not inside DDL (to handle both DDL and cache create through API > in the same place). See > org.apache.ignite.internal.processors.query.QueryUtils#validateQueryEntity Fixed. > 2) I am not very happy with precision/scale/maxLength properties - too much > of them. Instead, we can re-use "precision" for String length. H2 works this > way (see their docs), so it should be ok for us as well. In fact, this is why > GridSqlColumn.maxLength() return the same value as GridSqlColumn.precision() Fixed. > 3) QueryEntity - getters should return current value, without wrapping it > into unmodifiable collection, because this is how users frequently use us - > QueryEntity.getNotNullFields().add(...) Fixed. > 4) Let's split single decimal property into "scale" and "precision". Because > single precision would be needed not only for strings, but for other data > types as well (e.g. DOUBLE, REAL, BINARY) Fixed. > 6) QueryBinaryProperty, QueryTypeDescriptorImpl, QueryUtils - checks for > "_KEY" and "_VAL" are illegal, because key/val field names could be overriden > with QueryEntity.keyFieldName/valFieldName. These checks should be more > generic Fixed. > 7) QueryBinaryProperty.value() - new logic around key/val should be removed > as it breaks an invariant that only nested fields can be read/written here. > Please find a way to perform a check on key/value without changing central > field extraction logic. FIxed. > 8) We need more tests for cache API. E.g. I do not see tests for invoke(). Tests added. > 5) I do not see how compatibility is handled in .NET - new fields are > serialized unconditionally, meaning that we cannot talk to previous version. > Am I wrong? Do we have compatibility for a .Net client? I don't see any conditional logic for a "default field value" implementation [1]. Can you give me an example of such logic? [1] [https://github.com/apache/ignite/commit/78e79e011f1bb017653e628587faf606cfd37510] > SQL: Add String length constraint > - > > Key: IGNITE-6055 > URL: https://issues.apache.org/jira/browse/IGNITE-6055 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.1 >Reporter: Vladimir Ozerov >
[jira] [Commented] (IGNITE-6055) SQL: Add String length constraint
[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522719#comment-16522719
]
Nikolay Izhikov commented on IGNITE-6055:
-
> 1)
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor#toQueryEntity
> - this check is redundant, we should check whether QueryEntity is valid on
> cache start, not inside DDL (to handle both DDL and cache create through API
> in the same place). See
> org.apache.ignite.internal.processors.query.QueryUtils#validateQueryEntity
Fixed.
> 2) I am not very happy with precision/scale/maxLength properties - too much
> of them. Instead, we can re-use "precision" for String length. H2 works this
> way (see their docs), so it should be ok for us as well. In fact, this is why
> GridSqlColumn.maxLength() return the same value as GridSqlColumn.precision()
Fixed.
> 3) QueryEntity - getters should return current value, without wrapping it
> into unmodifiable collection, because this is how users frequently use us -
> QueryEntity.getNotNullFields().add(...)
Fixed.
> 4) Let's split single decimal property into "scale" and "precision". Because
> single precision would be needed not only for strings, but for other data
> types as well (e.g. DOUBLE, REAL, BINARY)
Fixed.
> 6) QueryBinaryProperty, QueryTypeDescriptorImpl, QueryUtils - checks for
> "_KEY" and "_VAL" are illegal, because key/val field names could be overriden
> with QueryEntity.keyFieldName/valFieldName. These checks should be more
> generic
Fixed.
> 7) QueryBinaryProperty.value() - new logic around key/val should be removed
> as it breaks an invariant that only nested fields can be read/written here.
> Please find a way to perform a check on key/value without changing central
> field extraction logic.
FIxed.
> 8) We need more tests for cache API. E.g. I do not see tests for invoke().
Tests added.
> 5) I do not see how compatibility is handled in .NET - new fields are
> serialized unconditionally, meaning that we cannot talk to previous version.
> Am I wrong?
Do we have compatibility for a .Net client?
I don't see any conditional logic for a "default field value" implementation
[1].
Can you give me an example of such logic?
[1]
[https://github.com/apache/ignite/commit/78e79e011f1bb017653e628587faf606cfd37510]
> SQL: Add String length constraint
> -
>
> Key: IGNITE-6055
> URL: https://issues.apache.org/jira/browse/IGNITE-6055
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: sql-engine
>
> We should support {{CHAR(X)}} and {{VARCHAR{X}} syntax. Currently, we ignore
> it. First, it affects semantics. E.g., one can insert a string with greater
> length into a cache/table without any problems. Second, it limits efficiency
> of our default configuration. E.g., index inline cannot be applied to
> {{String}} data type as we cannot guess it's length.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8741) [ML] Make a tutorial for data preprocessing
[ https://issues.apache.org/jira/browse/IGNITE-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522705#comment-16522705 ] ASF GitHub Bot commented on IGNITE-8741: GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4254 IGNITE-8741: Added Tutorial You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8741 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4254.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 #4254 commit 098d2832b3f4af23c72bc25f43e4ab8a95f2f416 Author: Zinoviev Alexey Date: 2018-04-11T18:40:27Z IGNITE-7829: Added example commit 78f9ea687bff77ec9f6bef87126569cb92cbe745 Author: Zinoviev Alexey Date: 2018-04-13T15:44:26Z Merge branch 'master' of https://github.com/apache/ignite commit 199e17d19ccbde9f15aba5375d834c3930b3a989 Author: Zinoviev Alexey Date: 2018-04-27T10:12:47Z Merge branch 'master' of https://github.com/apache/ignite commit aca9833df4d3cc4a641dd9109daaf628bc85acdf Author: Zinoviev Alexey Date: 2018-05-08T05:29:49Z Merge branch 'master' of https://github.com/apache/ignite commit bb244de762b89d0a1e5606aa282e34d92752595b Author: Zinoviev Alexey Date: 2018-05-16T11:42:06Z Merge branch 'master' of https://github.com/apache/ignite commit b4cb1a42d35a0da9f8b762207011a46c6f542a20 Author: Zinoviev Alexey Date: 2018-05-16T16:17:39Z Merge branch 'master' of https://github.com/apache/ignite commit 5d447d57d61c77b9f415093d634df8f3dccd55eb Author: Zinoviev Alexey Date: 2018-06-01T09:36:16Z Merge branch 'master' of https://github.com/apache/ignite commit 81ddb1c5db410d50208ada6d3de869e127506f56 Author: Zinoviev Alexey Date: 2018-06-04T08:21:37Z Merge branch 'master' of https://github.com/apache/ignite commit 780efa9f05bc5dbcc56e2ec373a0be93d63878d3 Author: Zinoviev Alexey Date: 2018-06-13T13:19:42Z Merge branch 'master' of https://github.com/apache/ignite commit c2aeffd5bf381b96beca706712803d9d4be8b350 Author: Zinoviev Alexey Date: 2018-06-13T16:40:58Z Add 3 tutorial steps commit 4144c7d1a61ac922a6fce0ebce722a1f3f59dd95 Author: Zinoviev Alexey Date: 2018-06-19T15:57:23Z Added CV and split support commit af91db4177466099098867ac043d9ac1c6cbebab Author: Zinoviev Alexey Date: 2018-06-19T17:19:16Z Added the best model commit 1b336eecec0457fd6a03ded72bcb0b78c7f650ae Author: Zinoviev Alexey Date: 2018-06-19T17:37:37Z Added the best model commit fecb9941c10e80db030870ee263b4d70353f5461 Author: zaleslaw Date: 2018-06-21T14:19:26Z Added correct CV example with inner CV to tune hyperparams commit b71bd58e62ca8c590c63fc8cba6f9d6ddbd4a4e5 Author: zaleslaw Date: 2018-06-21T16:30:33Z Fixed Desicion Trees commit 80e5cd2fcb4a3a179c2a1457efd78dcf23b54fb7 Author: zaleslaw Date: 2018-06-21T16:31:46Z Fixed Desicion Trees commit 14d08adaefdef49efbe9317f0c7b08a1b9a80b8d Author: Zinoviev Alexey Date: 2018-06-25T12:30:14Z Fixed bug in tests commit bfa2ba43bf4ca1361a119175e70121bb0427dacd Author: Zinoviev Alexey Date: 2018-06-25T18:08:48Z Fixed bug in StringEncoder and JavaDocs in tutorial commit 609adca1509495abb08884cd842b42c224aae160 Author: Zinoviev Alexey Date: 2018-06-25T18:10:06Z Fixed unused imports commit ff517ba80fe14e36ff13da03930c917900aed016 Author: Zinoviev Alexey Date: 2018-06-25T18:11:38Z Merge branch 'master' of https://github.com/apache/ignite commit 127566c4effd322b1263919f5979a3854015a9d2 Author: Zinoviev Alexey Date: 2018-06-25T19:02:10Z Merge branch 'master' into ignite-8741 commit 2dafb9f088960a462a79ba23daa906860c5040ed Author: Zinoviev Alexey Date: 2018-06-25T19:17:12Z Fixed RF > [ML] Make a tutorial for data preprocessing > --- > > Key: IGNITE-8741 > URL: https://issues.apache.org/jira/browse/IGNITE-8741 > Project: Ignite > Issue Type: Wish > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8873) Optimize cache scans with enabled persistence.
Alexei Scherbakov created IGNITE-8873: - Summary: Optimize cache scans with enabled persistence. Key: IGNITE-8873 URL: https://issues.apache.org/jira/browse/IGNITE-8873 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.6 Currently cache scans with enabled persistence involve link resolution, which can lead to radom disk access resulting in bad performace on SAS disks. One possibility is to preload cache data pages to remove slow random disk access. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-8836: - Fix Version/s: (was: 1.9) > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9, 2.4, 2.5 >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 2.6 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522473#comment-16522473 ] Andrew Mashenkov edited comment on IGNITE-8836 at 6/25/18 4:32 PM: --- PR looks irrelevant to the issue. Moreover, there is no such code in master that cause this failure. was (Author: amashenkov): PR looks irrelevant to the issue. > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9, 2.4, 2.5 >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 2.6 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8860) IgniteDiscoveryThread marker interface should be restored on RingMessageWorker class
[ https://issues.apache.org/jira/browse/IGNITE-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522490#comment-16522490 ] Dmitriy Pavlov commented on IGNITE-8860: I've retriggered failed tests on TC, let's wait it to be finished. > IgniteDiscoveryThread marker interface should be restored on > RingMessageWorker class > > > Key: IGNITE-8860 > URL: https://issues.apache.org/jira/browse/IGNITE-8860 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Sergey Chugunov >Assignee: Andrey Kuznetsov >Priority: Major > > It seems that *IgniteDiscoveryThread* interface was removed from > *ServerImpl.RingMessageWorker* class. > It should be restored as it is used to prevent deadlocks on updates of > BinaryMetadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8840) Random Forest
[ https://issues.apache.org/jira/browse/IGNITE-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522487#comment-16522487 ] ASF GitHub Bot commented on IGNITE-8840: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4251 > Random Forest > - > > Key: IGNITE-8840 > URL: https://issues.apache.org/jira/browse/IGNITE-8840 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > Fix For: 2.7 > > > We want to implement random forest algorithm. It should be based on our > implementation of decision trees. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8872) WAL scanner for crash recovery
Anton Kalashnikov created IGNITE-8872: - Summary: WAL scanner for crash recovery Key: IGNITE-8872 URL: https://issues.apache.org/jira/browse/IGNITE-8872 Project: Ignite Issue Type: Task Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522473#comment-16522473 ] Andrew Mashenkov commented on IGNITE-8836: -- PR looks irrelevant to the issue. > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9, 2.4, 2.5 >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 1.9, 2.6 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6587) Ignite watchdog service
[
https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522457#comment-16522457
]
Sergey Chugunov commented on IGNITE-6587:
-
[~andrey-kuznetsov],
I haven't finished review yet but have some high-level questions:
* As I see from code there is no way to turn this functionality off. It may
worth adding such ability e.g. on FailureHandler level. Users may even want not
to stop the node but log message at ERROR level and let monitoring systems to
identify such nodes and make appropriate actions.
* It is not clear what to do with GC pauses longer than
criticalHeartbeatTimeout - in that case node will stop when GC is finished.
[~agoncharuk], [~agura], what do you guys think about handling this? Should we
come up with some mechanism to deal with it?
> Ignite watchdog service
> ---
>
> Key: IGNITE-6587
> URL: https://issues.apache.org/jira/browse/IGNITE-6587
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Andrey Kuznetsov
>Priority: Major
> Labels: IEP-5
> Fix For: 2.6
>
> Attachments: watchdog.sh
>
>
> As described in [1], each Ignite node has a number of system-critical
> threads. We should implement a periodic check that calls failure handler when
> one of the following conditions has been detected:
> * Critical thread is not alive anymore.
> * Critical thread 'hangs' for a long time, e.g. while executing a task
> extracted from task queue.
> In case of failure condition, call stacks of all threads should be logged
> before invoking failure handler.
> Actual list of system-critical threads can be found at [1].
> Implementations based on separate diagnostic thread seem fragile, cause this
> thread become a vulnerable point with respect to thread termination and CPU
> resource starvation. So we are to use self-monitoring approach: critical
> threads themselves should monitor each other.
> Currently we have {{o.a.i.internal.worker.WorkersRegistry}} facility that
> fits best to store and track system critical threads. All of them should be
> refactored to be {{GridWorker's}} and added to {{WorkersRegistry}}. Each
> worker should periodically choose some subset of peer workers and check
> whether
> * All of them are alive.
> * All of them are actively running.
> It's required to add a 'heartbeat' timestamp to worker in order to implement
> latter check. Additionally, infinite queue polls, waits on monitors or thread
> parks should be refactored to their timed equivalents in system critical
> threads.
> Monitoring parameters (enable/disable, check interval, thread 'hang'
> threshold, etc.) are to be set via system properties.
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8426) Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing
[
https://issues.apache.org/jira/browse/IGNITE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522454#comment-16522454
]
Evgenii Zhuravlev commented on IGNITE-8426:
---
I've checked TC:
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll_IgniteTests24Java8=pull%2F4249%2Fhead=buildTypeStatusDiv
and it looks good, there is no new test failures
> Some classes creates JavaLogger directly which lead to SEVERE message in logs
> if JUL config file is missing
> ---
>
> Key: IGNITE-8426
> URL: https://issues.apache.org/jira/browse/IGNITE-8426
> Project: Ignite
> Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>Priority: Blocker
> Fix For: 2.7
>
>
> Here is the error message:
> SEVERE: Failed to resolve default logging config file:
> config/java.util.logging.properties
> For example, problem code is placed in LongJVMPauseDetector and
> IgniteJdbcDriver classes.
> Reproducer:
> IgniteConfiguration configuration = new IgniteConfiguration();
> configuration.setGridLogger(new
> Slf4jLogger(LoggerFactory.getLogger("ignite")));
> Ignition.start(configuration);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8742) Direct IO 2 suite is timed out by 'out of disk space' failure emulation test: WAL manager failure does not stoped execution
[
https://issues.apache.org/jira/browse/IGNITE-8742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522361#comment-16522361
]
ASF GitHub Bot commented on IGNITE-8742:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4158
> Direct IO 2 suite is timed out by 'out of disk space' failure emulation test:
> WAL manager failure does not stoped execution
> ---
>
> Key: IGNITE-8742
> URL: https://issues.apache.org/jira/browse/IGNITE-8742
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Sorokin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1366882=buildResultsDiv=IgniteTests24Java8_PdsDirectIo2
> Test
> org.apache.ignite.internal.processors.cache.persistence.IgniteNativeIoWalFlushFsyncSelfTest#testFailAfterStart
> emulates problem with disc space using exception.
> In direct IO environment real IO with disk is performed, tmpfs is not used.
> Sometimes this error can come from rollover() of segment, failure handler
> reacted accordingly.
> {noformat}
> detected. Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeFailureHandler, failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class o.a.i.i.pagemem.wal.StorageException: Unable
> to write]]
> class org.apache.ignite.internal.pagemem.wal.StorageException: Unable to write
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.writeBuffer(FsyncModeFileWriteAheadLogManager.java:2964)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2640)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2572)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2525)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.close(FsyncModeFileWriteAheadLogManager.java:2795)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$700(FsyncModeFileWriteAheadLogManager.java:2340)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.rollOver(FsyncModeFileWriteAheadLogManager.java:1029)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.log(FsyncModeFileWriteAheadLogManager.java:673)
> {noformat}
> But test seems to be not able to stop, node stopper thread tries to stop
> cache, flush WAL. flush wait for rollover, which will never happen.
> {noformat}
> Thread [name="node-stopper", id=2836, state=WAITING, blockCnt=7, waitCnt=9]
> Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@47f6473,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
> at o.a.i.i.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7473)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2546)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.fsync(FsyncModeFileWriteAheadLogManager.java:2750)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$2000(FsyncModeFileWriteAheadLogManager.java:2340)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.flush(FsyncModeFileWriteAheadLogManager.java:699)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1243)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:969)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:943)
> at o.a.i.i.IgniteKernal.stop0(IgniteKernal.java:2289)
> at o.a.i.i.IgniteKernal.stop(IgniteKernal.java:2167)
> at
[jira] [Updated] (IGNITE-8742) Direct IO 2 suite is timed out by 'out of disk space' failure emulation test: WAL manager failure does not stoped execution
[
https://issues.apache.org/jira/browse/IGNITE-8742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-8742:
---
Fix Version/s: 2.7
> Direct IO 2 suite is timed out by 'out of disk space' failure emulation test:
> WAL manager failure does not stoped execution
> ---
>
> Key: IGNITE-8742
> URL: https://issues.apache.org/jira/browse/IGNITE-8742
> Project: Ignite
> Issue Type: Test
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Sorokin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1366882=buildResultsDiv=IgniteTests24Java8_PdsDirectIo2
> Test
> org.apache.ignite.internal.processors.cache.persistence.IgniteNativeIoWalFlushFsyncSelfTest#testFailAfterStart
> emulates problem with disc space using exception.
> In direct IO environment real IO with disk is performed, tmpfs is not used.
> Sometimes this error can come from rollover() of segment, failure handler
> reacted accordingly.
> {noformat}
> detected. Will be handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeFailureHandler, failureCtx=FailureContext
> [type=CRITICAL_ERROR, err=class o.a.i.i.pagemem.wal.StorageException: Unable
> to write]]
> class org.apache.ignite.internal.pagemem.wal.StorageException: Unable to write
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.writeBuffer(FsyncModeFileWriteAheadLogManager.java:2964)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2640)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2572)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2525)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.close(FsyncModeFileWriteAheadLogManager.java:2795)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$700(FsyncModeFileWriteAheadLogManager.java:2340)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.rollOver(FsyncModeFileWriteAheadLogManager.java:1029)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.log(FsyncModeFileWriteAheadLogManager.java:673)
> {noformat}
> But test seems to be not able to stop, node stopper thread tries to stop
> cache, flush WAL. flush wait for rollover, which will never happen.
> {noformat}
> Thread [name="node-stopper", id=2836, state=WAITING, blockCnt=7, waitCnt=9]
> Lock
> [object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@47f6473,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
> at o.a.i.i.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7473)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2546)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.fsync(FsyncModeFileWriteAheadLogManager.java:2750)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$2000(FsyncModeFileWriteAheadLogManager.java:2340)
> at
> o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.flush(FsyncModeFileWriteAheadLogManager.java:699)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1243)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:969)
> at
> o.a.i.i.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:943)
> at o.a.i.i.IgniteKernal.stop0(IgniteKernal.java:2289)
> at o.a.i.i.IgniteKernal.stop(IgniteKernal.java:2167)
> at o.a.i.i.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2588)
> - locked o.a.i.i.IgnitionEx$IgniteNamedInstance@90f6bfd
> at
[jira] [Assigned] (IGNITE-8715) Problems with Closeable objects from Factory
[ https://issues.apache.org/jira/browse/IGNITE-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-8715: Assignee: Pavel Pereslegin > Problems with Closeable objects from Factory > > > Key: IGNITE-8715 > URL: https://issues.apache.org/jira/browse/IGNITE-8715 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexander Menshikov >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-21 > Fix For: 2.6 > > > According to specification Cache#close() should clean up all Closeable > objects (CacheLoader, CacheWriter, CacheEntryListener, ExpiryPolicy) created > by factories. > And in TCK 1.0.1 there are no such tests. But in TCK 1.1.0 there are checks > for it. And Ignite fails it because hasn't such functionality. > So this task about improvement. > Please see links for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7149) Gradient boosting for decision tree
[ https://issues.apache.org/jira/browse/IGNITE-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-7149: -- Assignee: Alexey Platonov (was: Artem Malykh) > Gradient boosting for decision tree > --- > > Key: IGNITE-7149 > URL: https://issues.apache.org/jira/browse/IGNITE-7149 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > > We want to implement gradient boosting for decision trees. It should be new > implementation of Trainer interface and we should keep possibility to choose > which trainer we want to use for our tree. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8688) Pending tree is initialized outside of checkpoint lock
[
https://issues.apache.org/jira/browse/IGNITE-8688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov reassigned IGNITE-8688:
Assignee: (was: Andrew Mashenkov)
> Pending tree is initialized outside of checkpoint lock
> --
>
> Key: IGNITE-8688
> URL: https://issues.apache.org/jira/browse/IGNITE-8688
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.6
>
>
> This may lead to possible page corruption.
> {noformat}
> handled accordingly to configured handler [hnd=class
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.AssertionError]]
> [00:11:56]W: [org.gridgain:gridgain-compatibility]
> java.lang.AssertionError
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.allocatePage(PageMemoryImpl.java:463)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.allocateForTree(IgniteCacheOffheapManagerImpl.java:818)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.initPendingTree(IgniteCacheOffheapManagerImpl.java:164)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.onCacheStarted(IgniteCacheOffheapManagerImpl.java:151)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.CacheGroupContext.onCacheStarted(CacheGroupContext.java:283)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1965)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:791)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:946)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2458)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2338)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [00:11:56]W: [org.gridgain:gridgain-compatibility] at
> java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8860) IgniteDiscoveryThread marker interface should be restored on RingMessageWorker class
[ https://issues.apache.org/jira/browse/IGNITE-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522333#comment-16522333 ] Sergey Chugunov commented on IGNITE-8860: - [~andrey-kuznetsov], Change looks good to me, please proceed with merging. Thank you for contribution! > IgniteDiscoveryThread marker interface should be restored on > RingMessageWorker class > > > Key: IGNITE-8860 > URL: https://issues.apache.org/jira/browse/IGNITE-8860 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Sergey Chugunov >Assignee: Andrey Kuznetsov >Priority: Major > > It seems that *IgniteDiscoveryThread* interface was removed from > *ServerImpl.RingMessageWorker* class. > It should be restored as it is used to prevent deadlocks on updates of > BinaryMetadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-8871: Component/s: documentation > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8871) TDE - Phase-1. Documentation
Nikolay Izhikov created IGNITE-8871: --- Summary: TDE - Phase-1. Documentation Key: IGNITE-8871 URL: https://issues.apache.org/jira/browse/IGNITE-8871 Project: Ignite Issue Type: Sub-task Affects Versions: 2.5 Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.7 TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-8871: Labels: documentation (was: ) > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8870) TDE - Phase-1. Examples
Nikolay Izhikov created IGNITE-8870: --- Summary: TDE - Phase-1. Examples Key: IGNITE-8870 URL: https://issues.apache.org/jira/browse/IGNITE-8870 Project: Ignite Issue Type: Sub-task Affects Versions: 2.5 Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.7 Examples should be provided for TDE implementations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8869) PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-8869: - Summary: PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity (was: PartitionsExchangeOnDiscoveryHistoryOverflowTest fails permanently) > PartitionsExchangeOnDiscoveryHistoryOverflowTest hangs on TeamCity > -- > > Key: IGNITE-8869 > URL: https://issues.apache.org/jira/browse/IGNITE-8869 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Ivan Daschinskiy >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > After introduction of ExhangeLatches, > PartitionsExchangeOnDiscoveryHistoryOverflowTest will hangs permanently. In > current implementation, ExchangeLatchManager retrieves alive nodes from > discoveryCache with specific affinity topology version and fails because of a > too short discovery history. This causes fail of exchange-worker and > therefore NoOpFailureHandler leaves node in hanging state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8869) PartitionsExchangeOnDiscoveryHistoryOverflowTest
Ivan Daschinskiy created IGNITE-8869: Summary: PartitionsExchangeOnDiscoveryHistoryOverflowTest Key: IGNITE-8869 URL: https://issues.apache.org/jira/browse/IGNITE-8869 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Ivan Daschinskiy Fix For: 2.6 After introduction of ExhangeLatches, PartitionsExchangeOnDiscoveryHistoryOverflowTest will hangs permanently. In current implementation, ExchangeLatchManager retrieves alive nodes from discoveryCache with specific affinity topology version and fails because of a too short discovery history. This causes fail of exchange-worker and therefore NoOpFailureHandler leaves node in hanging state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8869) PartitionsExchangeOnDiscoveryHistoryOverflowTest fails permanently
[ https://issues.apache.org/jira/browse/IGNITE-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-8869: - Summary: PartitionsExchangeOnDiscoveryHistoryOverflowTest fails permanently (was: PartitionsExchangeOnDiscoveryHistoryOverflowTest ) > PartitionsExchangeOnDiscoveryHistoryOverflowTest fails permanently > -- > > Key: IGNITE-8869 > URL: https://issues.apache.org/jira/browse/IGNITE-8869 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Ivan Daschinskiy >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > After introduction of ExhangeLatches, > PartitionsExchangeOnDiscoveryHistoryOverflowTest will hangs permanently. In > current implementation, ExchangeLatchManager retrieves alive nodes from > discoveryCache with specific affinity topology version and fails because of a > too short discovery history. This causes fail of exchange-worker and > therefore NoOpFailureHandler leaves node in hanging state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8594) Make error messages in validate_indexes command report more informative
[
https://issues.apache.org/jira/browse/IGNITE-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522323#comment-16522323
]
ASF GitHub Bot commented on IGNITE-8594:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4197
> Make error messages in validate_indexes command report more informative
> ---
>
> Key: IGNITE-8594
> URL: https://issues.apache.org/jira/browse/IGNITE-8594
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.6
>
>
> In case index is broken and contains links to missing items in data pages,
> validate_indexes command will show "Item not found" messages in report:
> {noformat}
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=_key_PK], class java.lang.IllegalStateException: Item not found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=_key_PK], class java.lang.IllegalStateException: Item not found: 15
> SQL Index [cache=cache_group_1_028, idx=LONG__VAL_IDX]
> ValidateIndexesPartitionResult [consistentId=node2, sqlIdxName=LONG__VAL_IDX]
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 60
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 15
> {noformat}
> It would be better to explain what is happening: key is present in SQL index,
> but is missing in corresponding data page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7163) Validate connection from a pre-previous node
[ https://issues.apache.org/jira/browse/IGNITE-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522312#comment-16522312 ] Dmitriy Pavlov commented on IGNITE-7163: [~dkarachentsev] I agree, it seems it was flaky failure. Sorry for inconvinence. > Validate connection from a pre-previous node > > > Key: IGNITE-7163 > URL: https://issues.apache.org/jira/browse/IGNITE-7163 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: 2.3 >Reporter: Alexandr Kuramshin >Assignee: Dmitry Karachentsev >Priority: Major > Labels: discovery > Fix For: 2.6 > > > If some pre-previous node connects to the local node with the previous node > in the message's failed nodes collection additional steps should be done: > # Connection with the previous node should be validated. > # If a message from the previous node was not received a long time ago, the > previous node should be considered as failed and the pre-previous node > connection accepted. > # If the previous node connection is alive then different scenarios possible > ## Answer with a new result code causing the pre-previous node to try to > reconnect to the previous node > ## Break connection with the pre-previous node causing to continue the > possible cluster split. > ## Check connections with nodes after pre-previous node and delay decision by > answering RES_WAIT to get more predictable split and stable topology. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8868) IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite
[ https://issues.apache.org/jira/browse/IGNITE-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522293#comment-16522293 ] ASF GitHub Bot commented on IGNITE-8868: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4253 > IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite > --- > > Key: IGNITE-8868 > URL: https://issues.apache.org/jira/browse/IGNITE-8868 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > All Data Frame specs should be included in IgniteDataFrameSuite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8868) IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite
[ https://issues.apache.org/jira/browse/IGNITE-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522277#comment-16522277 ] ASF GitHub Bot commented on IGNITE-8868: GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/4253 IGNITE-8868: DateFuncSpec added to IgniteDataFrameSuite You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-8868 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4253.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 #4253 commit c4a5f3c81790713f5fa8b1a5389f277524c6e2b4 Author: Nikolay Izhikov Date: 2018-06-25T13:30:15Z IGNITE-8868: IgniteOptimizationDateFuncSpec added to IgniteDataFrameSuite > IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite > --- > > Key: IGNITE-8868 > URL: https://issues.apache.org/jira/browse/IGNITE-8868 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > All Data Frame specs should be included in IgniteDataFrameSuite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8868) IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite
[ https://issues.apache.org/jira/browse/IGNITE-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-8868: --- Assignee: Nikolay Izhikov > IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite > --- > > Key: IGNITE-8868 > URL: https://issues.apache.org/jira/browse/IGNITE-8868 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > All Data Frame specs should be included in IgniteDataFrameSuite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8868) IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite
Nikolay Izhikov created IGNITE-8868: --- Summary: IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite Key: IGNITE-8868 URL: https://issues.apache.org/jira/browse/IGNITE-8868 Project: Ignite Issue Type: Bug Reporter: Nikolay Izhikov All Data Frame specs should be included in IgniteDataFrameSuite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8868) IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite
[ https://issues.apache.org/jira/browse/IGNITE-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-8868: Fix Version/s: 2.7 > IgniteOptimizationDateFuncSpec not included in IgniteDataFrameSuite > --- > > Key: IGNITE-8868 > URL: https://issues.apache.org/jira/browse/IGNITE-8868 > Project: Ignite > Issue Type: Bug >Reporter: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > All Data Frame specs should be included in IgniteDataFrameSuite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8867) Bootstrapping for learning sample
Yury Babak created IGNITE-8867: -- Summary: Bootstrapping for learning sample Key: IGNITE-8867 URL: https://issues.apache.org/jira/browse/IGNITE-8867 Project: Ignite Issue Type: Improvement Components: ml Reporter: Yury Babak Fix For: 2.7 Need to implement bootstrapping algorithm in Bagging-classifier -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0
[
https://issues.apache.org/jira/browse/IGNITE-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522272#comment-16522272
]
Nikolay Izhikov commented on IGNITE-8534:
-
Hello, [~ldz]
I found failed tests in your branch.
Please, run {{IgniteDataFrameSuite}} and fix all fails.
> Upgrade Ignite Spark Module's Spark version to 2.3.0
>
>
> Key: IGNITE-8534
> URL: https://issues.apache.org/jira/browse/IGNITE-8534
> Project: Ignite
> Issue Type: Improvement
> Components: spark
>Reporter: Ray
>Assignee: Ray
>Priority: Major
> Fix For: 2.6
>
>
> Spark released its newest version 2.3.0 on Feb 28th, we should upgrade Ignite
> Spark module to to the latest version.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8866) Need attempt to upload class until node leave or fail topology by discovery SPI
Vladislav Pyatkov created IGNITE-8866:
-
Summary: Need attempt to upload class until node leave or fail
topology by discovery SPI
Key: IGNITE-8866
URL: https://issues.apache.org/jira/browse/IGNITE-8866
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
After one fail attempt to upload a class, client code getting exception:
{noformat}
10:04:46,253 INFO [stdout] (Thread-732) java.lang.NoClassDefFoundError:
ru/sbt/deposit_pf_api/core/utils/DplUtils
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.nodeIdIgnite(CommonPredicate.java:225)
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.cacheEntities(CommonPredicate.java:191)
10:04:46,253 INFO [stdout] (Thread-732) at
ru.sbt.deposit_pf_api.comparators.CommonPredicate.(CommonPredicate.java:116)
{noformat}
And log contains some related warnings:
{noformat}
018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentCommunication]
Failed to receive peer response from node within duration
[node=5861d763-a552-463e-817a-0742f7aad114, duration=5008]
2018-06-19 10:04:18.459 [WARN
][pub-#3308%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDeploymentPerVersionStore]
Failed to send class-loading request to node (is node alive?)
[node=5861d763-a552-463e-817a-0742f7aad114,
clsName=ru.sbt.deposit_pf_api.core.utils.DplUtils,
clsPath=ru/sbt/deposit_pf_api/core/utils/DplUtils.class,
clsLdrId=370f1361461-5861d763-a552-463e-817a-0742f7aad114,
parentClsLdr=com.sbt.dpl.gridgain.ignite.NodeClassLoader@1ce4a752]
{noformat}
I think should to upload class through p2p until node present in topology.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8746) EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-8746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Vinokurov reassigned IGNITE-8746: --- Assignee: Pavel Vinokurov > EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator > node > --- > > Key: IGNITE-8746 > URL: https://issues.apache.org/jira/browse/IGNITE-8746 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Fix For: 2.6 > > Attachments: EvtDataLostTwiceOnCoordinatorReprocuder.java > > > After a node left the cluster the coordinator recieves the partition lost > event twice. > The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8840) Random Forest
[ https://issues.apache.org/jira/browse/IGNITE-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522122#comment-16522122 ] ASF GitHub Bot commented on IGNITE-8840: GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/4251 IGNITE-8840: Random Forest Implementation of bagging classification logic and random forest regression/classification based on it You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8840 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4251.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 #4251 commit c62bb6c4ea095efbf7ba81c864e3fd619800ee35 Author: gridgain Date: 2018-06-22T10:17:16Z first iteration commit b8ea97355de90d96f0e4de04122c84b4e7710dd4 Author: gridgain Date: 2018-06-22T11:18:18Z second iteration - create abstract BaggingClassifier commit 7006cc58cce08f2d7511f441050d9bb8c35eba54 Author: gridgain Date: 2018-06-22T14:53:47Z add tests for trainers and classifier example, add copyright headers commit e3f15e5be02a44ee59d3809d662167aab9dea14e Author: gridgain Date: 2018-06-25T08:52:24Z add threadpool and regression example commit 17e26ffe0ebc2ca0372938733a67a28dca645552 Author: gridgain Date: 2018-06-25T10:09:13Z add tests to aggreagators and add comments and formatting for ml.composition classes commit 023046dc5a0681166e569b402eea6c7f9254f07d Author: gridgain Date: 2018-06-25T10:21:06Z add comments and formatting for ml.composition classes > Random Forest > - > > Key: IGNITE-8840 > URL: https://issues.apache.org/jira/browse/IGNITE-8840 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > Fix For: 2.7 > > > We want to implement random forest algorithm. It should be based on our > implementation of decision trees. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522117#comment-16522117 ] Anton Kurbanov commented on IGNITE-8836: [TC|https://ci.ignite.apache.org/viewLog.html?buildId=1416980=buildResultsDiv=IgniteTests24Java8_RunAll] > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 1.9 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8819) Web Console: Edit everywhere the export buttons (2 types of design)
[ https://issues.apache.org/jira/browse/IGNITE-8819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8819. > Web Console: Edit everywhere the export buttons (2 types of design) > --- > > Key: IGNITE-8819 > URL: https://issues.apache.org/jira/browse/IGNITE-8819 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: New Export.png > > > See the attachment, the goal is to make "export to CSV" button more subdued. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7298) Web console: error on web agent start in case if demo is opened in browser
[
https://issues.apache.org/jira/browse/IGNITE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-7298:
--
Assignee: Andrey Novikov (was: Pavel Konstantinov)
> Web console: error on web agent start in case if demo is opened in browser
> --
>
> Key: IGNITE-7298
> URL: https://issues.apache.org/jira/browse/IGNITE-7298
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.6
>
>
> {code}
> [ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
> config/java.util.logging.properties
> Console logging handler is not configured.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8819) Web Console: Edit everywhere the export buttons (2 types of design)
[ https://issues.apache.org/jira/browse/IGNITE-8819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8819: - Fix Version/s: 2.7 > Web Console: Edit everywhere the export buttons (2 types of design) > --- > > Key: IGNITE-8819 > URL: https://issues.apache.org/jira/browse/IGNITE-8819 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: New Export.png > > > See the attachment, the goal is to make "export to CSV" button more subdued. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7298) Web console: error on web agent start in case if demo is opened in browser
[
https://issues.apache.org/jira/browse/IGNITE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522091#comment-16522091
]
Pavel Konstantinov commented on IGNITE-7298:
[~anovikov] Demo failed to start - no errors in the log.
Also, the page continuously shows error "Failed to execute request on cluster."
> Web console: error on web agent start in case if demo is opened in browser
> --
>
> Key: IGNITE-7298
> URL: https://issues.apache.org/jira/browse/IGNITE-7298
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.6
>
>
> {code}
> [ERROR][demo-nodes-start-0][] Failed to resolve default logging config file:
> config/java.util.logging.properties
> Console logging handler is not configured.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8818) Web Console: Reduce the height of head of all tables and change the location of the content
[ https://issues.apache.org/jira/browse/IGNITE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8818. > Web Console: Reduce the height of head of all tables and change the location > of the content > --- > > Key: IGNITE-8818 > URL: https://issues.apache.org/jira/browse/IGNITE-8818 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: Table-header.png > > > New height: 64px -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8768) JVM crash in PDS1 suite in master branch
[
https://issues.apache.org/jira/browse/IGNITE-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522077#comment-16522077
]
Alexey Goncharuk commented on IGNITE-8768:
--
[~Jokser], I do not like that we wait for the complete partition eviction
during a node shutdown. I think we can pass some sort of a status monitor to
stop partition clear process during the node stop into {{tryClear()}} method.
Otherwise, a node with a large persisted database will be stopping indefinitely
long time.
> JVM crash in PDS1 suite in master branch
>
>
> Key: IGNITE-8768
> URL: https://issues.apache.org/jira/browse/IGNITE-8768
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.4, 2.5
>Reporter: Sergey Chugunov
>Assignee: Pavel Kovalenko
>Priority: Blocker
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> JVM crash in latest build: [TC
> link|https://ci.ignite.apache.org/viewLog.html?buildId=1372456=buildResultsDiv=IgniteTests24Java8_Pds1]
> It is the first crash is latest 15 builds: [TC
> link|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8818) Web Console: Reduce the height of head of all tables and change the location of the content
[ https://issues.apache.org/jira/browse/IGNITE-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8818: - Fix Version/s: 2.7 > Web Console: Reduce the height of head of all tables and change the location > of the content > --- > > Key: IGNITE-8818 > URL: https://issues.apache.org/jira/browse/IGNITE-8818 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: Table-header.png > > > New height: 64px -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8858) Client node may not stop
[
https://issues.apache.org/jira/browse/IGNITE-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-8858:
Summary: Client node may not stop (was: Client none may not stop)
> Client node may not stop
>
>
> Key: IGNITE-8858
> URL: https://issues.apache.org/jira/browse/IGNITE-8858
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.6
>
>
> There is possible case when client node is not stopped and blocked on waiting
> when SocketReader will be completed. Looks like interruption was lost, and
> the only place where it could happen is in unmarshaling message from input
> stream.
> The way to overcome/fix it is to check if InterruptedException was in cause
> of IgniteCheckedException and repeatedly interrupt reader on stop.
>
> {noformat}
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1245)
> - locked <0x00041016a140> (a
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketReader)
> at java.lang.Thread.join(Thread.java:1319)
> at
> org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4604)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStop(ClientImpl.java:315)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2061)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1608)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2216)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2094)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2545)
> - locked <0x000410065e80> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2508)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:365)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3417)
> "tcp-client-disco-sock-reader-#35%Default%" #746 prio=5 os_prio=0
> tid=0x7f6090561800 nid=0x3441 in Object.wait() [0x7f60f23d8000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketReader.body(ClientImpl.java:1006)
> - locked <0x00041016a2e0> (a java.lang.Object)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8817) Web Console: Remove red links everywhere and do all links blue
[ https://issues.apache.org/jira/browse/IGNITE-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8817: - Fix Version/s: 2.7 > Web Console: Remove red links everywhere and do all links blue > -- > > Key: IGNITE-8817 > URL: https://issues.apache.org/jira/browse/IGNITE-8817 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > screenshot-4.png > > > * Do this on Admin Panel screen (period control and Email column) > * Do this in all modal windows, where we have the links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8817) Web Console: Remove red links everywhere and do all links blue
[ https://issues.apache.org/jira/browse/IGNITE-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8817. > Web Console: Remove red links everywhere and do all links blue > -- > > Key: IGNITE-8817 > URL: https://issues.apache.org/jira/browse/IGNITE-8817 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > screenshot-4.png > > > * Do this on Admin Panel screen (period control and Email column) > * Do this in all modal windows, where we have the links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6000) Assertion during destroy GridH2Table
[
https://issues.apache.org/jira/browse/IGNITE-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Fedotov reassigned IGNITE-6000:
Assignee: Ivan Fedotov
> Assertion during destroy GridH2Table
>
>
> Key: IGNITE-6000
> URL: https://issues.apache.org/jira/browse/IGNITE-6000
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Ivan Fedotov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> It was found here
> org.apache.ignite.internal.processors.cache.index.DynamicIndexReplicatedAtomicConcurrentSelfTest#testConcurrentOperationsAndCacheStartStopMultithreaded
> {code}
> [18:25:16] (err) Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1...@6000c93bjava.lang.AssertionError:
> {}
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.destroy(GridH2Table.java:508)
> at
> org.apache.ignite.internal.processors.query.h2.H2TableDescriptor.onDrop(H2TableDescriptor.java:346)
> at
> org.apache.ignite.internal.processors.query.h2.H2Schema.drop(H2Schema.java:114)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:2154)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1481)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:863)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1225)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:1999)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2149)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1294)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:1812)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processMessage(GridDhtPartitionsExchangeFuture.java:1479)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:110)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1.apply(GridDhtPartitionsExchangeFuture.java:1422)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1.apply(GridDhtPartitionsExchangeFuture.java:1410)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1410)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1425)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:127)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:292)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:290)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2294)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2273)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1042)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:561)
> 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
>
[jira] [Assigned] (IGNITE-809) Old value can be missed for tx near cache entry
[
https://issues.apache.org/jira/browse/IGNITE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-809:
---
Assignee: Alexey Kuznetsov
> Old value can be missed for tx near cache entry
> ---
>
> Key: IGNITE-809
> URL: https://issues.apache.org/jira/browse/IGNITE-809
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Artem Shutak
>Assignee: Alexey Kuznetsov
>Priority: Major
> Labels: Muted_test
>
> GridCacheMultinodeUpdateNearEnabledSelfTest fails.
> {noformat}
> junit.framework.AssertionFailedError: Got null in processor.
> at
> org.apache.ignite.internal.processors.cache.GridCacheMultinodeUpdateAbstractSelfTest.testInvoke(GridCacheMultinodeUpdateAbstractSelfTest.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1361)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:67)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$2.run(GridAbstractTest.java:1304)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7993) Striped pool can't be disabled
[
https://issues.apache.org/jira/browse/IGNITE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521998#comment-16521998
]
Roman Guseinov commented on IGNITE-7993:
Hi [~vkulichenko] , thank you for the comments.
According to the conversation with [~yzhdanov] , in this ticket, we just need
to restore an ability to disable striped pool. The additional pool can be the
next step once we create a reproducer.
> Striped pool can't be disabled
> --
>
> Key: IGNITE-7993
> URL: https://issues.apache.org/jira/browse/IGNITE-7993
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Valentin Kulichenko
>Assignee: Roman Guseinov
>Priority: Major
> Fix For: 2.6
>
>
> Javadoc for {{IgniteConfiguration#setStripedPoolSize}} states that striped
> pool can be disabled by providing value less or equal than zero:
> {noformat}
> If set to non-positive value then requests get processed in system pool.
> {noformat}
> However, doing that prevents node from startup, it fails with the following
> exception:
> {noformat}
> Caused by: class org.apache.ignite.IgniteCheckedException: Invalid
> stripedPool thread pool size (must be greater than 0), actual value: 0
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.validateThreadPoolSize(IgnitionEx.java:2061)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1799)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:664)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> ... 7 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-5980) [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
[ https://issues.apache.org/jira/browse/IGNITE-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Fedotov reassigned IGNITE-5980: Assignee: Ivan Fedotov > [Test Failed] > IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover > --- > > Key: IGNITE-5980 > URL: https://issues.apache.org/jira/browse/IGNITE-5980 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Ivan Fedotov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Example of failing > http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId-4067536648656067727 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8816) Web Console: Remove the red line in all tables
[ https://issues.apache.org/jira/browse/IGNITE-8816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8816. > Web Console: Remove the red line in all tables > -- > > Key: IGNITE-8816 > URL: https://issues.apache.org/jira/browse/IGNITE-8816 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: Red-line.png > > > Need to remove the red line in all the tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8864) sql-query-put x 5 performance drop
[ https://issues.apache.org/jira/browse/IGNITE-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov closed IGNITE-8864. > sql-query-put x 5 performance drop > -- > > Key: IGNITE-8864 > URL: https://issues.apache.org/jira/browse/IGNITE-8864 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Ilya Suntsov >Priority: Major > > Between commits, 631b659 and 303bd356 is a cause of x 5 performance drop on > sql query put. > Configuration: > * wal mode BACKGROUND > * sync mode PRIMARY SYNC > * 4 serv 8 clients > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8864) sql-query-put x 5 performance drop
[ https://issues.apache.org/jira/browse/IGNITE-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Suntsov resolved IGNITE-8864. -- Resolution: Won't Fix Not a problem in Ignite code. It was an environment issue. > sql-query-put x 5 performance drop > -- > > Key: IGNITE-8864 > URL: https://issues.apache.org/jira/browse/IGNITE-8864 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Ilya Suntsov >Priority: Major > > Between commits, 631b659 and 303bd356 is a cause of x 5 performance drop on > sql query put. > Configuration: > * wal mode BACKGROUND > * sync mode PRIMARY SYNC > * 4 serv 8 clients > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8816) Web Console: Remove the red line in all tables
[ https://issues.apache.org/jira/browse/IGNITE-8816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8816: - Fix Version/s: 2.7 > Web Console: Remove the red line in all tables > -- > > Key: IGNITE-8816 > URL: https://issues.apache.org/jira/browse/IGNITE-8816 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: Red-line.png > > > Need to remove the red line in all the tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
