[jira] [Commented] (IGNITE-10446) control.sh --cache idle_verify fail with NPE when node left grid
[
https://issues.apache.org/jira/browse/IGNITE-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709704#comment-16709704
]
Ignite TC Bot commented on IGNITE-10446:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2462603]]
* HibernateL2CacheTransactionalSelfTest.testRegionClear (last started)
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462670]]
* IgnitePdsTestSuite2:
WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync - 1,0% fails in
last 100 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2462685&buildTypeId=IgniteTests24Java8_RunAll]
> control.sh --cache idle_verify fail with NPE when node left grid
>
>
> Key: IGNITE-10446
> URL: https://issues.apache.org/jira/browse/IGNITE-10446
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: ARomantsov
>Assignee: Vladislav Pyatkov
>Priority: Critical
> Fix For: 2.8
>
>
>
> Command [IDLE_VERIFY -host=***] started at [2018-11-28 15:54:23]...
> Error code: 13000. java.lang.NullPointerException.
> Command [IDLE_VERIFY] failed with error: 13000 - command failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10534) DDL operations don't work on not started caches
[ https://issues.apache.org/jira/browse/IGNITE-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709687#comment-16709687 ] Yury Gerzhedovich commented on IGNITE-10534: PR link - [https://github.com/apache/ignite/pull/5574] > DDL operations don't work on not started caches > --- > > Key: IGNITE-10534 > URL: https://issues.apache.org/jira/browse/IGNITE-10534 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > Exception throws in case try execute create or drop index operations for not > started cache on not affinity node > java.lang.AssertionError > at > org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.isDdlSupported(DdlStatementsProcessor.java:532) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10534) DDL operations don't work on not started caches
[ https://issues.apache.org/jira/browse/IGNITE-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich updated IGNITE-10534: --- Description: Exception throws in case try execute create or drop index operations for not started cache on not affinity node java.lang.AssertionError at org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.isDdlSupported(DdlStatementsProcessor.java:532) was: Exception trows in case try execute create or drop index operations for not started cache on not affinity node java.lang.AssertionError at org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.isDdlSupported(DdlStatementsProcessor.java:532) > DDL operations don't work on not started caches > --- > > Key: IGNITE-10534 > URL: https://issues.apache.org/jira/browse/IGNITE-10534 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > Exception throws in case try execute create or drop index operations for not > started cache on not affinity node > java.lang.AssertionError > at > org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.isDdlSupported(DdlStatementsProcessor.java:532) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10534) DDL operations don't work on not started caches
Yury Gerzhedovich created IGNITE-10534: -- Summary: DDL operations don't work on not started caches Key: IGNITE-10534 URL: https://issues.apache.org/jira/browse/IGNITE-10534 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.8 Reporter: Yury Gerzhedovich Assignee: Yury Gerzhedovich Fix For: 2.8 Exception trows in case try execute create or drop index operations for not started cache on not affinity node java.lang.AssertionError at org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.isDdlSupported(DdlStatementsProcessor.java:532) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Ilya Borisov > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709571#comment-16709571 ] Ilya Borisov edited comment on IGNITE-9839 at 12/5/18 3:30 AM: --- [~kuaw26] it affects most of the screens. was (Author: klaster_1): [~kuaw26] it affects all screens. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-9839: Assignee: Pavel Konstantinov (was: Ilya Borisov) > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709571#comment-16709571 ] Ilya Borisov commented on IGNITE-9839: -- [~kuaw26] it affects all screens. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10533) Web Console: Images outdated on web site.
Alexey Kuznetsov created IGNITE-10533: - Summary: Web Console: Images outdated on web site. Key: IGNITE-10533 URL: https://issues.apache.org/jira/browse/IGNITE-10533 Project: Ignite Issue Type: Task Components: documentation Reporter: Alexey Kuznetsov Assignee: Prachi Garg For example see: https://apacheignite-tools.readme.io/docs/ignite-web-console -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709385#comment-16709385 ] Dmitriy Govorukhin commented on IGNITE-9023: [~daradurvs] I did review your change and I have a small question and remarks. questions: # Why do you use a custom topic? Can we do a test with standard P2P topic? # Why test was added in kernel test suite but not in p2p? remarks: # Use static IP finder instead multicast (by default) # Add dot at the end of string comments # Some line is very long, and do not fit into the page # I suggest use GridFutureAdapter instead CompletableFuture, in your test your future return status boolean (true/false) but false is never used, so I suggest change future and leave 2 states, done or exception > LinkageError or ClassNotFoundException should not be swollen by > GridDeploymentCommunication during processing deployment request. > - > > Key: IGNITE-9023 > URL: https://issues.apache.org/jira/browse/IGNITE-9023 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Ivan Daschinskiy >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > In current implementation any error, that is thrown in > GridDeploymentCommunication#processResourceRequest, is ignored silently. > Any error should be logged and send to client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10509) Rollback exception instead of timeout exception
[ https://issues.apache.org/jira/browse/IGNITE-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709371#comment-16709371 ] Dmitriy Govorukhin commented on IGNITE-10509: - [~akalashnikov] I did review your changes, and I have a question. Why this reordering solve a problem? I can get timeout status (true), but transaction state wasn't changed. Why is it ok? I mean, we still have a race between changes timeout status and change transaction change. Should we change timeout first in all cases? > Rollback exception instead of timeout exception > --- > > Key: IGNITE-10509 > URL: https://issues.apache.org/jira/browse/IGNITE-10509 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > > Looks like we have race on changing transaction state between timedOut and > state set > Reproducer - TxRollbackOnTimeoutNearCacheTest.testEnlistManyWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9023) LinkageError or ClassNotFoundException should not be swollen by GridDeploymentCommunication during processing deployment request.
[ https://issues.apache.org/jira/browse/IGNITE-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709365#comment-16709365 ] Dmitriy Govorukhin commented on IGNITE-9023: [~dpavlov] Yes, I will do it soon > LinkageError or ClassNotFoundException should not be swollen by > GridDeploymentCommunication during processing deployment request. > - > > Key: IGNITE-9023 > URL: https://issues.apache.org/jira/browse/IGNITE-9023 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Ivan Daschinskiy >Assignee: Vyacheslav Daradur >Priority: Minor > Fix For: 2.8 > > > In current implementation any error, that is thrown in > GridDeploymentCommunication#processResourceRequest, is ignored silently. > Any error should be logged and send to client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10509) Rollback exception instead of timeout exception
[ https://issues.apache.org/jira/browse/IGNITE-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10509: Ignite Flags: (was: Docs Required) > Rollback exception instead of timeout exception > --- > > Key: IGNITE-10509 > URL: https://issues.apache.org/jira/browse/IGNITE-10509 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > > Looks like we have race on changing transaction state between timedOut and > state set > Reproducer - TxRollbackOnTimeoutNearCacheTest.testEnlistManyWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10509) Rollback exception instead of timeout exception
[ https://issues.apache.org/jira/browse/IGNITE-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10509: Fix Version/s: 2.8 > Rollback exception instead of timeout exception > --- > > Key: IGNITE-10509 > URL: https://issues.apache.org/jira/browse/IGNITE-10509 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > > Looks like we have race on changing transaction state between timedOut and > state set > Reproducer - TxRollbackOnTimeoutNearCacheTest.testEnlistManyWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10519) [TC Bot] Create project documentation
[ https://issues.apache.org/jira/browse/IGNITE-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10519: Ignite Flags: (was: Docs Required) > [TC Bot] Create project documentation > - > > Key: IGNITE-10519 > URL: https://issues.apache.org/jira/browse/IGNITE-10519 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Minor > > Fill javadocs and package infos. > Create readme with multiclass interactions for developers with links to > package infos. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout
[
https://issues.apache.org/jira/browse/IGNITE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh reassigned IGNITE-9213:
Assignee: (was: Ilya Lantukh)
> CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading
> to TC timeout
> ---
>
> Key: IGNITE-9213
> URL: https://issues.apache.org/jira/browse/IGNITE-9213
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: ignite-9213-threaddump.txt
>
>
> Probability is quite low, < 5%.
> One thread gets stuck in GridCacheAdapter.lockAll(...), holding gw readlock
> and waiting for future that never completes. Another one cannot acquire gw
> writelock.
> {code}
> "test-runner-#123405%distributed.CacheLockReleaseNodeLeaveTest%" #136172
> prio=5 os_prio=0 tid=0x7f20cd3d7000 nid=0x356f
> sleeping[0x7f1eae48b000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7678)
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:970)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2195)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2082)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2595)
> - locked <0xc2e69580> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2558)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1153)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1196)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1174)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest.testLockTopologyChange(CacheLockReleaseNodeLeaveTest.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2156)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2071)
> at java.lang.Thread.run(Thread.java:745)
> "test-lock-thread-4" #136488 prio=5 os_prio=0 tid=0x7f208802a000
> nid=0x36a5 waiting on condition [0x7f1ea81c3000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.lockAll(GridCacheAdapter.java:3405)
> at
> org.apache.ignite.internal.processors.cache.CacheLockImpl.lock(CacheLockImpl.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest$3.run(CacheLockReleaseNodeLeaveTest.java:154)
> at
> org.apache.ignite.testframework.GridTestUtils$6.call(GridTestUtils.java:1254)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709159#comment-16709159
]
Ignite TC Bot commented on IGNITE-10434:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2462723]]
{color:#d04437}PDS 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2462790]]
{color:#d04437}MVCC Queries{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462757]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testPutAllGetAll_ClientServer_Backups1_RestartCoordinator_ScanDml_Persistence
- 0,0% fails in last 100 master runs.
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462747]]
* ZookeeperDiscoverySpiTestSuite2:
GridCachePartitionedNodeRestartTest.testRestartWithPutTenNodesTwoBackups - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462778]]
* IgniteCacheTestSuite7:
AuthenticationProcessorNodeRestartTest.testConcurrentFailedOperationNodeRestartServer
- 0,0% fails in last 100 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462727]]
* IgniteClientTestSuite: ClientTcpSslMultiNodeSelfTest.testTopologyListener -
0,0% fails in last 100 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2462806&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10348) Safely recreate metastore to mitigate IGNITE-8735
[ https://issues.apache.org/jira/browse/IGNITE-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709091#comment-16709091 ] Ivan Rakov commented on IGNITE-10348: - Looks good to me. [~agoncharuk], can you please take a glance as well? > Safely recreate metastore to mitigate IGNITE-8735 > - > > Key: IGNITE-10348 > URL: https://issues.apache.org/jira/browse/IGNITE-10348 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Alexey Goncharuk >Assignee: Alexey Stelmak >Priority: Critical > Fix For: 2.8 > > > We've fixed the issue IGNITE-8735, so new Ignite deployments are not affected > by this issue, but old deployments still may fail if a wrong page was already > put to the free list. We need to find out a way to repair this situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10428) [ML] Add example for OneVsRest trainer/model usage
[ https://issues.apache.org/jira/browse/IGNITE-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10428: -- Priority: Critical (was: Major) > [ML] Add example for OneVsRest trainer/model usage > -- > > Key: IGNITE-10428 > URL: https://issues.apache.org/jira/browse/IGNITE-10428 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > This example should use LogReg or SVM or DT to train multiclass model to > distinguish classes on prepared dataset (generate or use wide-known dataset) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9281) [ML] Starter ML tasks
[ https://issues.apache.org/jira/browse/IGNITE-9281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9281: - Priority: Minor (was: Major) > [ML] Starter ML tasks > - > > Key: IGNITE-9281 > URL: https://issues.apache.org/jira/browse/IGNITE-9281 > Project: Ignite > Issue Type: Wish > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: None > > > This ticket is an umbrella ticket for ML starter tasks. > Please, contact [~zaleslaw] to assign and get help with one of this tasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10532) [ML] Add Confusion Matrix for multi-class classification
[ https://issues.apache.org/jira/browse/IGNITE-10532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10532: -- Priority: Minor (was: Major) > [ML] Add Confusion Matrix for multi-class classification > > > Key: IGNITE-10532 > URL: https://issues.apache.org/jira/browse/IGNITE-10532 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Explore ability to integrate the OneVsRest with ConfusionMatrix calculation > also it can be implemented only after MultiClassEvaluator (no ticket yet) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9634) [ML] Trainers as pipeline parameters that can be varied
[ https://issues.apache.org/jira/browse/IGNITE-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9634: - Priority: Minor (was: Major) > [ML] Trainers as pipeline parameters that can be varied > --- > > Key: IGNITE-9634 > URL: https://issues.apache.org/jira/browse/IGNITE-9634 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Based > http://apache-ignite-developers.2346864.n4.nabble.com/ML-New-Feature-Trainers-as-pipeline-parameters-that-can-be-varied-td35132.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9513) [ML] Unify all preprocessors trainers' generics
[ https://issues.apache.org/jira/browse/IGNITE-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9513: - Priority: Trivial (was: Major) > [ML] Unify all preprocessors trainers' generics > --- > > Key: IGNITE-9513 > URL: https://issues.apache.org/jira/browse/IGNITE-9513 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > > Currently we have > EncoderTrainer implements PreprocessingTrainer > and > BinarizationTrainer implements PreprocessingTrainer Vector> > It will helps with raw types in OneVsRest or in Pipeline and CV processes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9989) JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
[
https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709074#comment-16709074
]
Pavel Kuznetsov commented on IGNITE-9989:
-
Pgsql plan for SelectBySalaryWithJoin :
{noformat}
Hash Join (cost=1292.42..2624.51 rows=361 width=1572)Hash Cond:
(o.id = p.org_id)-> Seq Scan on organization o (cost=0.00..839.04
rows=10304 width=524)
-> Hash (cost=1287.91..1287.91 rows=361 width=1056)
-> Bitmap Heap Scan on person p (cost=60.12..1287.91 rows=361 width=1056)
Recheck Cond: ((salary >= '366018000'::bigint) AND
(salary <= '367017000'::bigint)) -> Bitmap Index
Scan on sal_idx (cost=0.00..60.03 rows=361 width=0)
Index Cond: ((salary >= '366018000'::bigint) AND (salary <=
'367017000'::bigint))
{noformat}
Pgsql plan for SelectByPkWithJoin :
{noformat}
Hash Join (cost=1292.42..2624.51 rows=361 width=1572)Hash Cond:
(o.id = p.org_id)-> Seq Scan on organization o (cost=0.00..839.04
rows=10304 width=524)
-> Hash (cost=1287.91..1287.91 rows=361 width=1056)
-> Bitmap Heap Scan on person p (cost=60.12..1287.91 rows=361 width=1056)
Recheck Cond: ((id >= '661420'::bigint) AND (id <=
'662419'::bigint)) -> Bitmap Index Scan on
person_pkey (cost=0.00..60.03 rows=361 width=0)
Index Cond: ((id >= '661420'::bigint) AND (id <= '662419'::bigint))
{noformat}
> JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
> -
>
> Key: IGNITE-9989
> URL: https://issues.apache.org/jira/browse/IGNITE-9989
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Kuznetsov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Labels: jdbc
>
> Jdbc v2 driver has hardcoded values for meta attibutes :
> COLUMN_NAME = _KEY
> KEY_SEQ = 1
> PK_NAME = _KEY
> But this values should be different for different tables.
> how to reproduce:
> 1) connect to the cluser using jdbcv2 driver
> 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID))
> 3) check result of connection.getMetadata().getPrimaryKeys()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10528) [ML] Fix incorrect comparing of double values in ML examples
[ https://issues.apache.org/jira/browse/IGNITE-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10528: -- Priority: Critical (was: Major) > [ML] Fix incorrect comparing of double values in ML examples > > > Key: IGNITE-10528 > URL: https://issues.apache.org/jira/browse/IGNITE-10528 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > Look at code row > if (groundTruth != prediction) > in each example > Fix with Math.abs or Double.compare method (don't forget precision) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9497) [ML] Add Pipeline support to Cross-Validation process
[ https://issues.apache.org/jira/browse/IGNITE-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9497: - Priority: Minor (was: Major) > [ML] Add Pipeline support to Cross-Validation process > - > > Key: IGNITE-9497 > URL: https://issues.apache.org/jira/browse/IGNITE-9497 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Change API of ParamGrid.addHyperParam to support meta-information about > Pipeline Stage > Add to Cross-Validation method to support evaluate the whole Pipeline Process > and inject hyper-parameters from the ParamGrid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10371) [ML] Add multiple metrics calculation fo Binary Classification Evaluation process
[ https://issues.apache.org/jira/browse/IGNITE-10371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10371: -- Priority: Critical (was: Major) > [ML] Add multiple metrics calculation fo Binary Classification Evaluation > process > - > > Key: IGNITE-10371 > URL: https://issues.apache.org/jira/browse/IGNITE-10371 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > Add ability to get map of metrics to evaluate binary classification. > Try to implement: All implemented metrics should be calculated for one > iteration cycle along the data > Naive implementation: compose all passed metrics and calculate them separatly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10407) [ML] Add Multi-label multi-class classification trainer and model
[ https://issues.apache.org/jira/browse/IGNITE-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10407: -- Priority: Minor (was: Major) > [ML] Add Multi-label multi-class classification trainer and model > - > > Key: IGNITE-10407 > URL: https://issues.apache.org/jira/browse/IGNITE-10407 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > > Improve Ignite ML ability to work with tasks for multi-labeled > multi-classification > It requiers > * extension of current API with models for Double prediction only > * addition of common OneVsRest Multi-labeled Multi-classification Model and > Trainer > * preparing apropriate datasets for example and testing > * -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9633) [ML] Hyperparameter tuning improvements umbrella ticket
[ https://issues.apache.org/jira/browse/IGNITE-9633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-9633: - Priority: Minor (was: Major) > [ML] Hyperparameter tuning improvements umbrella ticket > --- > > Key: IGNITE-9633 > URL: https://issues.apache.org/jira/browse/IGNITE-9633 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Umbrella ticket for all hyperparameter tuning improvements -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10145) [ML] ROC AUC score
[ https://issues.apache.org/jira/browse/IGNITE-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10145: -- Priority: Major (was: Critical) > [ML] ROC AUC score > -- > > Key: IGNITE-10145 > URL: https://issues.apache.org/jira/browse/IGNITE-10145 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.8 > > > Compute Area Under the Receiver Operating Characteristic Curve (ROC AUC) from > prediction scores. > We want to implement this score for our models. > Some links: > * [wiki|https://en.wikipedia.org/wiki/Receiver_operating_characteristic] > * [google > dev|https://developers.google.com/machine-learning/crash-course/classification/roc-and-auc] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4380) Cache invoke calls can be lost
[
https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709072#comment-16709072
]
Eduard Shangareev commented on IGNITE-4380:
---
Would change status and assignee because of long silence time.
> Cache invoke calls can be lost
> --
>
> Key: IGNITE-4380
> URL: https://issues.apache.org/jira/browse/IGNITE-4380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Semen Boikov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> * Recently added test
> GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded fails on TC in
> various configurations with transactional cache.
> Example of failure
> GridCacheReplicatedOffHeapTieredMultiNodeFullApiSelfTest.testInvokeAllMultithreaded:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<10868>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded(GridCacheAbstractFullApiSelfTest.java:342)
> at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4380) Cache invoke calls can be lost
[
https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-4380:
-
Assignee: Eduard Shangareev (was: Alexey Kuznetsov)
> Cache invoke calls can be lost
> --
>
> Key: IGNITE-4380
> URL: https://issues.apache.org/jira/browse/IGNITE-4380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Semen Boikov
>Assignee: Eduard Shangareev
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> * Recently added test
> GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded fails on TC in
> various configurations with transactional cache.
> Example of failure
> GridCacheReplicatedOffHeapTieredMultiNodeFullApiSelfTest.testInvokeAllMultithreaded:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<10868>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded(GridCacheAbstractFullApiSelfTest.java:342)
> at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4380) Cache invoke calls can be lost
[
https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev reassigned IGNITE-4380:
-
Assignee: (was: Eduard Shangareev)
> Cache invoke calls can be lost
> --
>
> Key: IGNITE-4380
> URL: https://issues.apache.org/jira/browse/IGNITE-4380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Semen Boikov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> * Recently added test
> GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded fails on TC in
> various configurations with transactional cache.
> Example of failure
> GridCacheReplicatedOffHeapTieredMultiNodeFullApiSelfTest.testInvokeAllMultithreaded:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<10868>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded(GridCacheAbstractFullApiSelfTest.java:342)
> at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10529) [ML] Add Confusion Matrix support for classification algorithms
[ https://issues.apache.org/jira/browse/IGNITE-10529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10529: -- Priority: Minor (was: Major) > [ML] Add Confusion Matrix support for classification algorithms > --- > > Key: IGNITE-10529 > URL: https://issues.apache.org/jira/browse/IGNITE-10529 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > This is an umbrella ticket for Confusion Matrix Support -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10530) [ML] Add Confusion Matrix for Binary Classification
[ https://issues.apache.org/jira/browse/IGNITE-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev updated IGNITE-10530: -- Priority: Minor (was: Major) > [ML] Add Confusion Matrix for Binary Classification > --- > > Key: IGNITE-10530 > URL: https://issues.apache.org/jira/browse/IGNITE-10530 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Minor > Fix For: 2.8 > > > Add special class to build confusion matrix as a product of evaluation process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10531) [ML] Refactor all examples to use Binary Confusion Matrix instead of calculations by hand
[
https://issues.apache.org/jira/browse/IGNITE-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Zinoviev updated IGNITE-10531:
--
Priority: Minor (was: Major)
> [ML] Refactor all examples to use Binary Confusion Matrix instead of
> calculations by hand
> -
>
> Key: IGNITE-10531
> URL: https://issues.apache.org/jira/browse/IGNITE-10531
> Project: Ignite
> Issue Type: Sub-task
> Components: ml
>Affects Versions: 2.8
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Minor
> Fix For: 2.8
>
>
> Change
> // Build confusion matrix. See https://en.wikipedia.org/wiki/Confusion_matrix
> int[][] confusionMtx = \{{0, 0}, \{0, 0}};
> to usage of ConfusionMatrix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10532) [ML] Add Confusion Matrix for multi-class classification
Aleksey Zinoviev created IGNITE-10532: - Summary: [ML] Add Confusion Matrix for multi-class classification Key: IGNITE-10532 URL: https://issues.apache.org/jira/browse/IGNITE-10532 Project: Ignite Issue Type: Sub-task Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Explore ability to integrate the OneVsRest with ConfusionMatrix calculation also it can be implemented only after MultiClassEvaluator (no ticket yet) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9989) JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME
[ https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709070#comment-16709070 ] Pavel Kuznetsov commented on IGNITE-9989: - So first results for select-range benchmarks: ||Vendor\Benchmark (Q/sec, Avg) ||SelectBySalary||SelectByPk ||SelectBySalaryWithJoin||SelectByPkWithJoin|| ||ignite thin inmemory |885.36 |1,030.81 |170.41 |189.30| ||ignite jdbc v2 inmemory |891.48 |1,046.89 |157.34 |170.51| ||ignite thin persistence |560.58 |669.73 |141.23 |146.14| ||ignite jdbc v2 persistence|582.89 |653.87 |128.28 |137.35| ||Mysql (tunned)|770.97 |786.83 |199.29 |237.16| ||PgSQL (tunned)|1,845.70 |1,795.23 |73.94 |74.05| > JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME > - > > Key: IGNITE-9989 > URL: https://issues.apache.org/jira/browse/IGNITE-9989 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Labels: jdbc > > Jdbc v2 driver has hardcoded values for meta attibutes : > COLUMN_NAME = _KEY > KEY_SEQ = 1 > PK_NAME = _KEY > But this values should be different for different tables. > how to reproduce: > 1) connect to the cluser using jdbcv2 driver > 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID)) > 3) check result of connection.getMetadata().getPrimaryKeys() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10531) [ML] Refactor all examples to use Binary Confusion Matrix instead of calculations by hand
Aleksey Zinoviev created IGNITE-10531:
-
Summary: [ML] Refactor all examples to use Binary Confusion Matrix
instead of calculations by hand
Key: IGNITE-10531
URL: https://issues.apache.org/jira/browse/IGNITE-10531
Project: Ignite
Issue Type: Sub-task
Components: ml
Affects Versions: 2.8
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev
Fix For: 2.8
Change
// Build confusion matrix. See https://en.wikipedia.org/wiki/Confusion_matrix
int[][] confusionMtx = \{{0, 0}, \{0, 0}};
to usage of ConfusionMatrix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10530) [ML] Add Confusion Matrix for Binary Classification
Aleksey Zinoviev created IGNITE-10530: - Summary: [ML] Add Confusion Matrix for Binary Classification Key: IGNITE-10530 URL: https://issues.apache.org/jira/browse/IGNITE-10530 Project: Ignite Issue Type: Sub-task Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Add special class to build confusion matrix as a product of evaluation process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10529) [ML] Add Confusion Matrix support for classification algorithms
Aleksey Zinoviev created IGNITE-10529: - Summary: [ML] Add Confusion Matrix support for classification algorithms Key: IGNITE-10529 URL: https://issues.apache.org/jira/browse/IGNITE-10529 Project: Ignite Issue Type: New Feature Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 This is an umbrella ticket for Confusion Matrix Support -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10528) [ML] Fix incorrect comparing of double values in ML examples
Aleksey Zinoviev created IGNITE-10528: - Summary: [ML] Fix incorrect comparing of double values in ML examples Key: IGNITE-10528 URL: https://issues.apache.org/jira/browse/IGNITE-10528 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Look at code row if (groundTruth != prediction) in each example Fix with Math.abs or Double.compare method (don't forget precision) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709007#comment-16709007 ] ASF GitHub Bot commented on IGNITE-10523: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5570 > Ignite Compatibility: add check that started node is of expected version > > > Key: IGNITE-10523 > URL: https://issues.apache.org/jira/browse/IGNITE-10523 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > It's necessary to check that node started in separate JVM is of a specified > version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10513) Java client stucks when connects to server with slow disk
[
https://issues.apache.org/jira/browse/IGNITE-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709008#comment-16709008
]
Ignite TC Bot commented on IGNITE-10513:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2462519]]
* IgniteSpiTestSuite:
TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
- 0,0% fails in last 100 master runs.
* IgniteSpiTestSuite:
TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished - 0,0%
fails in last 100 master runs.
{color:#d04437}Platform C++ (Windows x64){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2462529]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Java Client{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2462507]]
* IgniteClientTestSuite: RedisProtocolStringSelfTest.testStrlen - 0,0% fails in
last 100 master runs.
* IgniteClientTestSuite: RedisProtocolStringSelfTest.testSetRange - 0,0% fails
in last 100 master runs.
* IgniteClientTestSuite: RedisProtocolStringSelfTest.testGetSet - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache (Deadlock Detection){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462541]]
* TxDeadlockDetectionTestSuite:
TxPessimisticDeadlockDetectionTest.testDeadlocksPartitionedNear - 0,0% fails in
last 100 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2462534]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache (Failover) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2462545]]
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverTxTest.testPutAllAsyncFailover - 0,0% fails in last
100 master runs.
{color:#d04437}Streamers{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2462517]]
* IgniteKafkaStreamerSelfTestSuite:
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation - 0,0% fails in last
100 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2462528]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Binary Objects{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2462492]]
* IgniteBinaryObjectsTestSuite:
BinaryMetadataUpdatesFlowTest.testFlowNoConflictsWithClients - 0,0% fails in
last 100 master runs.
* IgniteBinaryObjectsTestSuite:
GridCacheBinaryObjectMetadataExchangeMultinodeTest.testReadRequestBlockedOnUpdatingMetadata
- 0,0% fails in last 100 master runs.
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2462582]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2462586&buildTypeId=IgniteTests24Java8_RunAll]
> Java client stucks when connects to server with slow disk
> -
>
> Key: IGNITE-10513
> URL: https://issues.apache.org/jira/browse/IGNITE-10513
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.6
>Reporter: Dmitry Lazurkin
>Priority: Major
> Attachments: ignite-client.log
>
>
> For emulating slow disk add _sleep_ to partitions cycle in
> _GridCacheDatabaseSharedManager#restorePartitionStates_:
> {noformat}
> //...
> for (int i = 0; i < grp.affinity().partitions(); i++) {
> try {
> log.error("Wait");
> Thread.sleep(1);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> //...
> {noformat}
> My server has 1024 partitions.
> Steps to reproduce:
> * Start server
> * Start client
> * On client wait message "Join cluster while cluster state transition is in
> progress, waiting when transition finish."
> * Kill server
> * On client wait repeatable java.net.ConnectException: Connection refused
> (Connection refused)
> * Start server (I have 100% chance to reproduce issue on my computer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10526) IgniteWalReaderTest logs too much garbage on node stop.
[
https://issues.apache.org/jira/browse/IGNITE-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10526:
Ignite Flags: (was: Docs Required)
> IgniteWalReaderTest logs too much garbage on node stop.
> ---
>
> Key: IGNITE-10526
> URL: https://issues.apache.org/jira/browse/IGNITE-10526
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> WalIterator log stacktrace for each data record if no cache context found for
> entry.
> Let's make it less verbose somehow (e.g. throttle or mock cache context) to
> reduce logs and save TC disk space.
>
> {noformat}
> [18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04
> 15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root]
> Failed to perform post processing for data record
> [18:41:53]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteException: Failed to find cache context for the given
> cache ID: -1368047378
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:248){noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10527) [ML] DenseMatrix(double[] mtx, int rows) mixes args
[ https://issues.apache.org/jira/browse/IGNITE-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Malykh updated IGNITE-10527: -- Summary: [ML] DenseMatrix(double[] mtx, int rows) mixes args (was: DenseMatrix(double[] mtx, int rows) mixes args) > [ML] DenseMatrix(double[] mtx, int rows) mixes args > --- > > Key: IGNITE-10527 > URL: https://issues.apache.org/jira/browse/IGNITE-10527 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Artem Malykh >Priority: Major > > this(mtx, StorageConstants.ROW_STORAGE_MODE, rows) -> > this(mtx, rows, StorageConstants.ROW_STORAGE_MODE); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10527) DenseMatrix(double[] mtx, int rows) mixes args
Artem Malykh created IGNITE-10527: - Summary: DenseMatrix(double[] mtx, int rows) mixes args Key: IGNITE-10527 URL: https://issues.apache.org/jira/browse/IGNITE-10527 Project: Ignite Issue Type: Bug Components: ml Reporter: Artem Malykh this(mtx, StorageConstants.ROW_STORAGE_MODE, rows) -> this(mtx, rows, StorageConstants.ROW_STORAGE_MODE); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10526) IgniteWalReaderTest logs too much garbage on node stop.
[
https://issues.apache.org/jira/browse/IGNITE-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-10526:
--
Description:
WalIterator log stacktrace for each data record if no cache context found for
entry.
Let's make it less verbose somehow (e.g. throttle or mock cache context) to
reduce logs and save TC disk space.
{noformat}
[18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04
15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root]
Failed to perform post processing for data record
[18:41:53]W: [org.apache.ignite:ignite-core] class
org.apache.ignite.IgniteException: Failed to find cache context for the given
cache ID: -1368047378
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:248){noformat}
was:
WalIterator log stacktrace for each data record if no cache context found for
entry.
Let's make it less verbose somehow, e.g. throttle or mock cach context.
{noformat}
[18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04
15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root]
Failed to perform post processing for data record
[18:41:53]W: [org.apache.ignite:ignite-core] class
org.apache.ignite.IgniteException: Failed to find cache context for the given
cache ID: -1368047378
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:248){noformat}
> IgniteWalReaderTest logs too much garbage on node stop.
> ---
>
> Key: IGNITE-10526
> URL: https://issues.apache.org/jira/browse/IGNITE-10526
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> WalIterator log stacktrace for each data record if no cache context found for
> entry.
> Let's make it less verbose somehow (e.g. throttle or mock cache context) to
> reduce logs and save TC disk space.
>
> {noformat}
> [18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04
> 15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root]
> Failed to perform post processing for data record
> [18:41:53]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteException: Failed to find cache context for the given
> cache ID: -1368047378
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
> [18:41:53]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(Abs
[jira] [Created] (IGNITE-10526) IgniteWalReaderTest logs too much garbage on node stop.
Andrew Mashenkov created IGNITE-10526:
-
Summary: IgniteWalReaderTest logs too much garbage on node stop.
Key: IGNITE-10526
URL: https://issues.apache.org/jira/browse/IGNITE-10526
Project: Ignite
Issue Type: Improvement
Components: persistence
Reporter: Andrew Mashenkov
WalIterator log stacktrace for each data record if no cache context found for
entry.
Let's make it less verbose somehow, e.g. throttle or mock cach context.
{noformat}
[18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04
15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root]
Failed to perform post processing for data record
[18:41:53]W: [org.apache.ignite:ignite-core] class
org.apache.ignite.IgniteException: Failed to find cache context for the given
cache ID: -1368047378
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
[18:41:53]W: [org.apache.ignite:ignite-core] at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:248){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10386) Add mode when WAL won't be disabled during rebalancing caused by BLT change
[ https://issues.apache.org/jira/browse/IGNITE-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708973#comment-16708973 ] Ivan Rakov commented on IGNITE-10386: - Thanks, merged to master. > Add mode when WAL won't be disabled during rebalancing caused by BLT change > --- > > Key: IGNITE-10386 > URL: https://issues.apache.org/jira/browse/IGNITE-10386 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Rakov >Assignee: Andrey Kuznetsov >Priority: Major > Fix For: 2.8 > > > Enabling IgniteSystemProperties#IGNITE_DISABLE_WAL_DURING_REBALANCING > disables WAL for cache group during rebalancing in case local node has no > OWNING partitions for this group. > We should add mode when in specific case (after BaselineTopology change) WAL > won't be disabled even if this property is switched on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9630) Partitions intersection for AND condition of same key
[ https://issues.apache.org/jira/browse/IGNITE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708946#comment-16708946 ] Vladimir Ozerov commented on IGNITE-9630: - Implemented. Left: cleanup, more tests. Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=2463618 > Partitions intersection for AND condition of same key > - > > Key: IGNITE-9630 > URL: https://issues.apache.org/jira/browse/IGNITE-9630 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Sergey Grimstad >Assignee: Vladimir Ozerov >Priority: Major > Labels: iep-24 > Fix For: 2.8 > > > GridSqlQuerySplitter when extractPartition for AND operation type should > calculate intersection of resolved partitions for the same key -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9630) Partitions intersection for AND condition of same key
[ https://issues.apache.org/jira/browse/IGNITE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9630: Attachment: (was: sgrimstad_IGNITE_9630_implementation_.patch) > Partitions intersection for AND condition of same key > - > > Key: IGNITE-9630 > URL: https://issues.apache.org/jira/browse/IGNITE-9630 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Sergey Grimstad >Assignee: Vladimir Ozerov >Priority: Major > Labels: iep-24 > Fix For: 2.8 > > > GridSqlQuerySplitter when extractPartition for AND operation type should > calculate intersection of resolved partitions for the same key -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9630) Partitions intersection for AND condition of same key
[ https://issues.apache.org/jira/browse/IGNITE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708942#comment-16708942 ] ASF GitHub Bot commented on IGNITE-9630: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/5572 IGNITE-9630 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9630-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5572.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 #5572 commit 1a41a15edf6ad9f394fc09fc91052abbf7004d7f Author: SGrimstad Date: 2018-09-27T14:23:28Z IGNITE-9632 implementation commit 03d73e26e4ccee1753f213d01f5656788c135d85 Author: SGrimstad Date: 2018-10-12T13:58:09Z IGNITE-9630 implementation commit dd43a544e2ae29595090fc29efd404f3df58d002 Author: SGrimstad Date: 2018-10-15T09:11:03Z Merge branch 'master' into IGNITE-9630 commit ac1ff7ec683b3a3889fea43d155bc7a0ba8fceb1 Author: SGrimstad Date: 2018-10-16T07:16:30Z IGNITE-6677 fix (braces returned) commit e197d0217bb7ccf17c89f195b72a23c30d529c56 Author: SGrimstad Date: 2018-10-16T11:40:10Z IGNITE-6677 fix TableView commit 9afd0a4e4379f8ea95c4d5ad1446f04376fdd8cb Author: devozerov Date: 2018-10-23T12:22:08Z Merge branch 'master' into IGNITE-9630 # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/sql/GridSqlQuerySplitter.java # modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/h2/twostep/InOperationExtractPartitionSelfTest.java commit 9b6eaeeac1bb2974a9ac342712a20bf23d1035d2 Author: devozerov Date: 2018-10-23T12:24:48Z WIP. commit ddaf01b1f4b1b025298e6adbe44959ccee30df7e Author: SGrimstad Date: 2018-10-24T08:39:46Z IGNITE-9630 fixed according to review commit 7eb76c354230c6cb90dda046d97ec3aa39873c52 Author: devozerov Date: 2018-11-15T20:18:00Z Merge branch 'master' into IGNITE-9630 # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/affinity/PartitionInfo.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/sql/GridSqlQuerySplitter.java # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite2.java commit ad7e904c112244381996b2344b99feb25b86cf49 Author: devozerov Date: 2018-11-15T20:34:58Z Mege. commit 22f4c765b81ee37b1127061a294b4807ec83db0a Author: devozerov Date: 2018-11-15T20:38:08Z WIP. commit f8d6c1b3ccec91f37c6291f0a52c5c6434a9d5b5 Author: devozerov Date: 2018-11-15T20:41:06Z WIP. commit d0551103dd7aae28c0e984c6420ebd65beb0c553 Author: devozerov Date: 2018-11-29T10:24:52Z Merge branch 'master' into ignite-9630-1 commit 2dc57345fcaf1363ad1e155a59027430694ac6dc Author: devozerov Date: 2018-11-29T11:19:15Z Minors. commit be4510f6796d89970af0dba6a1d7a183ee3bb4b0 Author: devozerov Date: 2018-11-29T12:08:41Z Nodes. commit 4d0fca6aaa39c8e130c22426a0a9db7107181e87 Author: devozerov Date: 2018-11-29T12:25:08Z WIP. commit 1c89061efcdecd51fbc4fa73fe715fff66a0415e Author: devozerov Date: 2018-11-29T14:12:32Z Optimization algebra. commit e7830c3c7a9707e80c634086c5e35528fbade95a Author: devozerov Date: 2018-11-29T14:18:13Z Optimization algebra. commit b3908e3d7ac811a7830809e95c1f89fa026d03bc Author: devozerov Date: 2018-11-29T15:01:42Z Partition extractor for new logic. commit 8ca4a504cd38083585af4337bf5b3539b91d6914 Author: devozerov Date: 2018-11-29T15:07:12Z WIP. commit ebe5fc9481a1580920364bfc92f1becf32d3da54 Author: devozerov Date: 2018-11-29T15:12:42Z WIP. commit 49698f5862c1fb6b6b035b1b9fd3544417e3e2d9 Author: devozerov Date: 2018-12-04T12:54:52Z Merge branch 'master' into ignite-9630-1 commit 93d5d9b080d508aa8a1eb19bc3fa6a86cb4f392d Author: devozerov Date: 2018-12-04T13:11:17Z Simplified existing merge. commit e0d775332997afa980d8930272ca1f6fd7bd7174 Author: devozerov Date: 2018-12-04T14:52:57Z WIP on better resolver placement. commit 795b6245d55a05430a7701200433d29ddaff6f9e Author: devozerov Date: 2018-12-04T15:49:57Z WIP. commit 41302c9e7b07ed2ba38556a9fe1bba77d1d4e481 Author: devozerov Date: 2018-12-04T15:59:11Z Wire up. commit e27c289fb6ef99e80f16ea82b352e5f83290016d Author: devozerov Date: 2018-12-04T16:03:45Z Finished wire up. commit d7b1a4876e31264e6fa86f1fb46d5e7da076cae2 Author: devozerov Date: 2018-12-04T16:04:46Z Minors. commit a7e89aa7c18314
[jira] [Updated] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9839: - Fix Version/s: 2.8 > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9839) Web Console: update to RxJS 6
[ https://issues.apache.org/jira/browse/IGNITE-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9839: Assignee: Ilya Borisov (was: Alexey Kuznetsov) Looks good to me. [~Klaster_1], Please prepare a list of affected screens and assign to [~pkonstantinov] to smoke test Web Console. > Web Console: update to RxJS 6 > - > > Key: IGNITE-9839 > URL: https://issues.apache.org/jira/browse/IGNITE-9839 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Fix For: 2.8 > > Time Spent: 6h 47m > Remaining Estimate: 0h > > Since RxJS 6 is required by latest version of Angular, we won't be able to > proceed with UI framework migration without it. To do: update import paths, > convert to pipe API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10406) .NET Failed to run ScanQuery with custom filter after server node restart
[
https://issues.apache.org/jira/browse/IGNITE-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708919#comment-16708919
]
Pavel Tupitsyn commented on IGNITE-10406:
-
The bug is caused by cached Binary Writer Structure: we send meta only once per
type. The fix is to reset cached meta on reconnect with full cluster restart.
The is one potential issue with the fix (rare use case), see comments in
Marshaller.OnClientReconnected.
> .NET Failed to run ScanQuery with custom filter after server node restart
> -
>
> Key: IGNITE-10406
> URL: https://issues.apache.org/jira/browse/IGNITE-10406
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5, 2.6
>Reporter: Ivan Daschinskiy
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .net
> Fix For: 2.8
>
> Attachments: CacheQueriesWithRestartServerTest.cs
>
>
> Scenario:
> 1. Start server
> 2. Start client.
> 3. Restart server and wait for client reconnects the server.
> 4. Put some data to cache and run ScanQuery with custom filter
>
> StackTrace:
> {code:java}
> class org.apache.ignite.IgniteCheckedException: Failed to inject resource
> [method=setIgniteInstance,
> target=org.apache.ignite.internal.processors.platform.cache.PlatformCacheEntryFilterImpl@6225c21c,
> rsrc=IgniteKernal [cfg=IgniteConfiguration
> [igniteInstanceName=CashflowCluster, pubPoolSize=8, svcPoolSize=8,
> callbackPoolSize=8, stripedPoolSize=8, sysPoolSize=8, mgmtPoolSize=4,
> igfsPoolSize=4, dataStreamerPoolSize=8,
> utilityCachePoolSize=8, utilityCacheKeepAliveTime=6, p2pPoolSize=2,
> qryPoolSize=8,
> igniteHome=C:\Job\fd-tasks\7404\IgniteTests2\packages\Apache.Ignite.2.6.0,
> igniteWorkDir=C:\Job\fd-tasks\7404\IgniteTests2\packages\Apache.Ignite.2.6.0\work,
> mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@49993335,
> nodeId=3f4aadd9-01b3-4ffe-b629-895fb6ac886f,
> marsh=org.apache.ignite.internal.binary.BinaryMarshaller@77a57272, mar
> shLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
> sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
> metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
> discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@65b1c1e3],
> reconCnt=10, reconDelay=2000, maxAckTimeout=60, forceSrvMode=fals
> e, clientReconnectDisabled=false, internalLsnr=null], segPlc=STOP,
> segResolveAttempts=2, waitForSegOnStart=true, allResolversPassReq=true,
> segChkFreq=1, commSpi=TcpCommunicationSpi
> [connectGate=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$ConnectGateway@4737110c,
>
> connPlc=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$6@bce0ed4,
> enableForcibleNodeKill=false, enableTroubleshootingLog=fa
> lse,
> srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@11c20519,
> locAddr=null, locHost=0.0.0.0/0.0.0.0, locPort=47100, locPortRange=100,
> shmemPort=-1, directBuf=true, directSndBuf=false, idleConnTimeout=60,
> connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
> sockRcvBuf=32768, msgQueueLimit=0, slowClientQueueLimit=0,
> nioSrvr=GridNioServer [selectorSpins=0, filterChain=Filte
> rChain[filters=[GridNioCodecFilter
> [parser=org.apache.ignite.internal.util.nio.GridDirectParser@6839fd4e,
> directMode=true], GridConnectionBytesVerifyFilter],
> lsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@11c20519,
> closed=false, directBuf=true, tcpNoDelay=true, sockSndBuf=32768,
> sockRcvBuf=32768, writeTimeout=2000, idleTimeout=60, skipWrite=false,
> skipRead=false, locAddr=0.0.0.0/0.0.0.0:47100
> , order=LITTLE_ENDIAN, sndQueueLimit=0, directMode=true,
> metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@4e41089d,
> sslFilter=null, msgQueueLsnr=null, readerMoveCnt=0, writerMoveCnt=0,
> readWriteSelectorsAssign=false], shmemSrv=null, usePairedConnections=false,
> connectionsPerNode=1, tcpNoDelay=true, filterReachableAddresses=false,
> ackSndThreshold=32, unackedMsgsBufSize=0, sockWriteT
> imeout=2000,
> lsnr=org.apache.ignite.internal.managers.communication.GridIoManager$2@432d2e4e,
> boundTcpPort=47100, boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0,
> addrRslvr=null,
> ctxInitLatch=java.util.concurrent.CountDownLatch@70beb599[Count = 0],
> stopping=false,
> metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@4e41089d],
> evtSpi=org.apache.ignite.spi.eventstorage.NoopEventSt
> orageSpi@32a068d1, colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi
> [lsnr=org.apache.ignite.internal.managers.dep
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708918#comment-16708918
]
Ryabov Dmitrii commented on IGNITE-10437:
-
[~ilantukh], I made loop as you suggested. Tests are ok.
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708903#comment-16708903 ] Vyacheslav Daradur commented on IGNITE-10523: - [~dpavlov], please, have a look at the prepared PR. > Ignite Compatibility: add check that started node is of expected version > > > Key: IGNITE-10523 > URL: https://issues.apache.org/jira/browse/IGNITE-10523 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > It's necessary to check that node started in separate JVM is of a specified > version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708913#comment-16708913
]
Ignite TC Bot commented on IGNITE-10437:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2453717&buildTypeId=IgniteTests24Java8_RunAll]
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9458) SQL benchmarks: absence of "--mvcc" benchmark flag should not overwrite config values
[ https://issues.apache.org/jira/browse/IGNITE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9458: --- Ignite Flags: (was: Docs Required) > SQL benchmarks: absence of "--mvcc" benchmark flag should not overwrite > config values > - > > Key: IGNITE-9458 > URL: https://issues.apache.org/jira/browse/IGNITE-9458 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Minor > > Currently, IgniteNode benchmark application ignores mvccEnable property of > IgniteConfiguration. > Absence of --mvcc flag is treateted as "turn mvcc off forcibly", existence as > "turn mvcc on forcibly". > We need to change sematics of absence of this flag as "Use value from config". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-995) Nodes on one host doesn't discover each other if IP finder doesn't explicitly provide port
[ https://issues.apache.org/jira/browse/IGNITE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708904#comment-16708904 ] Dmitriy Pavlov commented on IGNITE-995: --- [~voropava] could you please review the change? > Nodes on one host doesn't discover each other if IP finder doesn't explicitly > provide port > -- > > Key: IGNITE-995 > URL: https://issues.apache.org/jira/browse/IGNITE-995 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: sprint-4 >Reporter: Valentin Kulichenko >Assignee: Mikhail Lipkovich >Priority: Major > Labels: Usability, newbie > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov reassigned IGNITE-7611: -- Assignee: Artem Budnikov (was: Stanislav Lukyanov) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10461) MVCC: Create "PDS 1" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708895#comment-16708895
]
Ignite TC Bot commented on IGNITE-10461:
{panel:title=-> Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-> Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2462150&buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> MVCC: Create "PDS 1" test suite for MVCC mode.
> --
>
> Key: IGNITE-10461
> URL: https://issues.apache.org/jira/browse/IGNITE-10461
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgnitePdsTestSuite and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov reassigned IGNITE-7611: -- Assignee: Prachi Garg (was: Artem Budnikov) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708887#comment-16708887 ] Stanislav Lukyanov commented on IGNITE-7611: On the Logging Configuration Tips section: I would be happy to see it as a short walkthrough to get a decent logging setup. Ideally, this should be the first (and only) section that a user reads to setup logging sufficient to debug issues - either themselves or with the help of community/experts/etc. What I imagine there: - Use log4j framework. Even though log4j2 is more advanced, log4j currently have some additional support in Ignite (in that Ignite is able to pick it up more easily without additional configuration). -- If you use Maven --- add ignite-log4j dependency --- add log4j XML configuration file to META-INF/ignite-log4j.xml (you can copy it from binary distribution) -- If you use Ignite binary distribution --- move libs/option/ignite-log4j into libs/ - Review the ignite-log4j.xml file. Uncomment CONSOLE_OUT appender. - If you don't use Ignite binary distribution make sure to set workDirectory path - Start Ignite in verbose mode -- If you use ignite.sh use -v -- If you stat Ignite from Java code, set IGNITE_QUIET=false A walkthrough like this is arguably more important than any other ways we can document logging. It will solve the issue for 99% of users. The current draft is fine as is and can be published, but I believe we need to 1) Make sure we have a ticket to document the walkthrough like the one above 2) Make sure we have a ticket to document the logging options that [~Artem Budnikov] has described as "difficult to comprehend" - if not in the user docs, we need to have them documented on dev Wiki or somewhere else, and eventually either improve so that they're usable or just remove them. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10522) Remote node has not joined
[ https://issues.apache.org/jira/browse/IGNITE-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708886#comment-16708886 ] ASF GitHub Bot commented on IGNITE-10522: - GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5571 IGNITE-10522 added removing .tmp checkpoint files on start You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10522 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5571.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 #5571 commit 3cd8bc740a39a6701ca5735d0a4789c163825ccb Author: Anton Kalashnikov Date: 2018-12-04T15:35:28Z IGNITE-10522 added removing .tmp checkpoint files on start commit 67d03cb3d29f0255bd045f5f81af64823387a773 Author: Anton Kalashnikov Date: 2018-12-04T15:38:48Z IGNITE-10522 fixed typo > Remote node has not joined > -- > > Key: IGNITE-10522 > URL: https://issues.apache.org/jira/browse/IGNITE-10522 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > > Sometimes tests failed because of "Remote node has not joined" > suit - PDS (Indexing) > example test - IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash > In fact checkpoint tmp files doesn't not removed on start. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.
[
https://issues.apache.org/jira/browse/IGNITE-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov resolved IGNITE-10525.
---
Resolution: Fixed
> Web Console: "Import models" dialog should be a singleton.
> --
>
> Key: IGNITE-10525
> URL: https://issues.apache.org/jira/browse/IGNITE-10525
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.8
>
>
> # Click on *Import from Database* button to open dialog.
> # Quick click by work area in time when background become dark prevent dialog
> opening.
> When dialog opening is prevented any try to open it produce error:
> {code}
> TypeError: this.parent.fqn is not a function
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.fqn
> (stateObject.js:61)
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.toString
> (stateObject.js:102)
> at
> StateRegistry.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateRegistry.js.StateRegistry.deregister
> (stateRegistry.js:141)
> at ModalImportModels._goToDynamicState (service.js:24)
> at ModalImportModels.open (service.js:54)
> at ButtonImportModels.startImport (component.js:27)
> at fn (eval at compile (angular.js:15869), :4:181)
> at callback (angular.js:28101)
> at Scope.$eval (angular.js:18838)
> at Scope.$apply (angular.js:18937) undefined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.
[
https://issues.apache.org/jira/browse/IGNITE-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-10525:
-
Assignee: Pavel Konstantinov (was: Alexey Kuznetsov)
Fixed. Merged to master.
[~pkonstantinov], Please retest.
> Web Console: "Import models" dialog should be a singleton.
> --
>
> Key: IGNITE-10525
> URL: https://issues.apache.org/jira/browse/IGNITE-10525
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.8
>
>
> # Click on *Import from Database* button to open dialog.
> # Quick click by work area in time when background become dark prevent dialog
> opening.
> When dialog opening is prevented any try to open it produce error:
> {code}
> TypeError: this.parent.fqn is not a function
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.fqn
> (stateObject.js:61)
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.toString
> (stateObject.js:102)
> at
> StateRegistry.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateRegistry.js.StateRegistry.deregister
> (stateRegistry.js:141)
> at ModalImportModels._goToDynamicState (service.js:24)
> at ModalImportModels.open (service.js:54)
> at ButtonImportModels.startImport (component.js:27)
> at fn (eval at compile (angular.js:15869), :4:181)
> at callback (angular.js:28101)
> at Scope.$eval (angular.js:18838)
> at Scope.$apply (angular.js:18937) undefined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10522) Remote node has not joined
[ https://issues.apache.org/jira/browse/IGNITE-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov updated IGNITE-10522: --- Description: Sometimes tests failed because of "Remote node has not joined" suit - PDS (Indexing) example test - IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash In fact checkpoint tmp files doesn't not removed on start. was: Sometimes tests failed because of "Remote node has not joined" suit - PDS (Indexing) example test - IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash > Remote node has not joined > -- > > Key: IGNITE-10522 > URL: https://issues.apache.org/jira/browse/IGNITE-10522 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > > Sometimes tests failed because of "Remote node has not joined" > suit - PDS (Indexing) > example test - IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash > In fact checkpoint tmp files doesn't not removed on start. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708877#comment-16708877 ] ASF GitHub Bot commented on IGNITE-8227: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4974 > Research possibility and implement JUnit test failure handler for TeamCity > -- > > Key: IGNITE-8227 > URL: https://issues.apache.org/jira/browse/IGNITE-8227 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > > After IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > we found a lot of TC failures involving unexpected nodes stop. > To avoid suites exit codes, tests have NoOpFailureHandler as default. > But instead of this, better handler could be > stopNode + fail currenly running test with message. > This default allows to identify such failures without log-message fail > condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708861#comment-16708861 ] ASF GitHub Bot commented on IGNITE-10523: - GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/5570 IGNITE-10523 Ignite Compatibility: add check that started node is of expected version You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-10523 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5570.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 #5570 commit 7232a8f1cbfb5084cc6439b91122330fd84ce083 Author: Vyacheslav Daradur Date: 2018-12-04T15:20:28Z Added check of started version > Ignite Compatibility: add check that started node is of expected version > > > Key: IGNITE-10523 > URL: https://issues.apache.org/jira/browse/IGNITE-10523 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > It's necessary to check that node started in separate JVM is of a specified > version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5115) Investigation of failing tests of coordinator node failure
[
https://issues.apache.org/jira/browse/IGNITE-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708860#comment-16708860
]
Yakov Zhdanov commented on IGNITE-5115:
---
[~agoncharuk] [~voropava] [~NSAmelchev]
Overall idea seems to be absolutely valid. However, new code seems to fail if
user configures NOOP segmentation policy - coordinator will not stop. So we
need to have guaranteed way to stop coordinator.
Cancelling patch for now
Yakov
> Investigation of failing tests of coordinator node failure
> ---
>
> Key: IGNITE-5115
> URL: https://issues.apache.org/jira/browse/IGNITE-5115
> Project: Ignite
> Issue Type: Bug
> Components: messaging
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Tests *customEventCoordinatorFailure1/2* from *TcpDiscoverySelfTest* are
> flaky on TC and sometimes hang with the following assertion in logs:
> {code}
> Exception in thread "tcp-disco-msg-worker-#5245%tcp.TcpDiscoverySelfTest0%"
> java.lang.AssertionError
> at
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing.removeNode(TcpDiscoveryNodesRing.java:353)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeFailedMessage(ServerImpl.java:4670)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2567)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2366)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6485)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2456)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> It seems that this happens because tests' implementation drops connections of
> *TcpCommunicatonSpi* on coordinator node with *simulateNodeFailure* method.
> At the same time tests leave *TcpDiscoverySpi* operational; it receives
> subsequent NodeFailed message and throws the assertion error shown above.
> The whole situation looks legitimate as it is possible to imagine a situation
> when CommSPI connections on coordinator fail for some reason while DiscoSPI
> connections are healthy.
> It is needed to investigate the situation deeper, figure out whether the root
> cause is using of *simulateNodeFailure* or not and propose a solution if the
> error may happen in the real life.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708828#comment-16708828 ] Artem Budnikov edited comment on IGNITE-7611 at 12/4/18 3:15 PM: - [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. [https://apacheignite.readme.io/v2.6/docs/logging-27] was (Author: artem budnikov): [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.
[
https://issues.apache.org/jira/browse/IGNITE-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-10525:
--
Ignite Flags: (was: Docs Required)
> Web Console: "Import models" dialog should be a singleton.
> --
>
> Key: IGNITE-10525
> URL: https://issues.apache.org/jira/browse/IGNITE-10525
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> # Click on *Import from Database* button to open dialog.
> # Quick click by work area in time when background become dark prevent dialog
> opening.
> When dialog opening is prevented any try to open it produce error:
> {code}
> TypeError: this.parent.fqn is not a function
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.fqn
> (stateObject.js:61)
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.toString
> (stateObject.js:102)
> at
> StateRegistry.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateRegistry.js.StateRegistry.deregister
> (stateRegistry.js:141)
> at ModalImportModels._goToDynamicState (service.js:24)
> at ModalImportModels.open (service.js:54)
> at ButtonImportModels.startImport (component.js:27)
> at fn (eval at compile (angular.js:15869), :4:181)
> at callback (angular.js:28101)
> at Scope.$eval (angular.js:18838)
> at Scope.$apply (angular.js:18937) undefined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10355) Tx rollback failure on put operations with caches whose topology fails validation
[
https://issues.apache.org/jira/browse/IGNITE-10355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708832#comment-16708832
]
Ignite TC Bot commented on IGNITE-10355:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2461555&buildTypeId=IgniteTests24Java8_RunAll]
> Tx rollback failure on put operations with caches whose topology fails
> validation
> -
>
> Key: IGNITE-10355
> URL: https://issues.apache.org/jira/browse/IGNITE-10355
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6, 2.7
>Reporter: Dmitriy Sorokin
>Assignee: Dmitriy Sorokin
>Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The issue may occur as stacktrace below:
> {noformat}
> [2018-10-12 18:47:28,351][ERROR][test-runner-#1][GridDhtColocatedCache]
> Failed to rollback transaction (cache may contain stale locks):
> GridNearTxLocal[xid=95ce5f86661--08fd-9fc9--0002,
> xidVersion=GridCacheVersion [topVer=150839241, order=1539359239257,
> nodeOrder=2], concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> state=ROLLED_BACK, invalidate=false, rollbackOnly=true,
> nodeId=108e38a0-64e2-4da6-ab06-6db7e6ae9001, timeout=0, duration=0,
> label=null]
> class org.apache.ignite.IgniteCheckedException: Failed to rollback
> transaction:
> GridNearTxLocal[xid=95ce5f86661--08fd-9fc9--0002,
> xidVersion=GridCacheVersion [topVer=150839241, order=1539359239257,
> nodeOrder=2], concurrency=OPTIMISTIC, isolation=READ_COMMITTED,
> state=ROLLED_BACK, invalidate=false, rollbackOnly=true,
> nodeId=108e38a0-64e2-4da6-ab06-6db7e6ae9001, timeout=0, duration=0,
> label=null]
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:514)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:425)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$27.apply(GridNearTxLocal.java:3962)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$27.apply(GridNearTxLocal.java:3950)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.chainFinishFuture(GridNearTxLocal.java:3950)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3864)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3833)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$18.applyx(GridNearTxLocal.java:2966)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$18.applyx(GridNearTxLocal.java:2948)
> at
> org.apache.ignite.internal.util.lang.IgniteClosureX.apply(IgniteClosureX.java:38)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter$ChainFuture.(GridFutureAdapter.java:574)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.chain(GridFutureAdapter.java:360)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.optimisticPutFuture(GridNearTxLocal.java:2947)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:693)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:447)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2470)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2468)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4233)
> at
> org.apache.ignite.internal.processors.
[jira] [Commented] (IGNITE-10368) MVCC: Create "Cache 9" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708835#comment-16708835
]
Ignite TC Bot commented on IGNITE-10368:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2462168]]
{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2460850]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2460887&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Create "Cache 9" test suite for MVCC mode.
>
>
> Key: IGNITE-10368
> URL: https://issues.apache.org/jira/browse/IGNITE-10368
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgniteCacheTestSuite9 and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.
[
https://issues.apache.org/jira/browse/IGNITE-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-10525:
--
Fix Version/s: 2.8
> Web Console: "Import models" dialog should be a singleton.
> --
>
> Key: IGNITE-10525
> URL: https://issues.apache.org/jira/browse/IGNITE-10525
> Project: Ignite
> Issue Type: Task
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> # Click on *Import from Database* button to open dialog.
> # Quick click by work area in time when background become dark prevent dialog
> opening.
> When dialog opening is prevented any try to open it produce error:
> {code}
> TypeError: this.parent.fqn is not a function
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.fqn
> (stateObject.js:61)
> at
> Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.toString
> (stateObject.js:102)
> at
> StateRegistry.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateRegistry.js.StateRegistry.deregister
> (stateRegistry.js:141)
> at ModalImportModels._goToDynamicState (service.js:24)
> at ModalImportModels.open (service.js:54)
> at ButtonImportModels.startImport (component.js:27)
> at fn (eval at compile (angular.js:15869), :4:181)
> at callback (angular.js:28101)
> at Scope.$eval (angular.js:18838)
> at Scope.$apply (angular.js:18937) undefined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10525) Web Console: "Import models" dialog should be a singleton.
Alexey Kuznetsov created IGNITE-10525:
-
Summary: Web Console: "Import models" dialog should be a singleton.
Key: IGNITE-10525
URL: https://issues.apache.org/jira/browse/IGNITE-10525
Project: Ignite
Issue Type: Task
Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
# Click on *Import from Database* button to open dialog.
# Quick click by work area in time when background become dark prevent dialog
opening.
When dialog opening is prevented any try to open it produce error:
{code}
TypeError: this.parent.fqn is not a function
at
Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.fqn
(stateObject.js:61)
at
Object.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateObject.js.StateObject.toString
(stateObject.js:102)
at
StateRegistry.push.../../../../incubator-ignite/modules/web-console/frontend/node_modules/@uirouter/core/lib/state/stateRegistry.js.StateRegistry.deregister
(stateRegistry.js:141)
at ModalImportModels._goToDynamicState (service.js:24)
at ModalImportModels.open (service.js:54)
at ButtonImportModels.startImport (component.js:27)
at fn (eval at compile (angular.js:15869), :4:181)
at callback (angular.js:28101)
at Scope.$eval (angular.js:18838)
at Scope.$apply (angular.js:18937) undefined
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-7611: -- Assignee: Stanislav Lukyanov (was: Artem Budnikov) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708828#comment-16708828 ] Artem Budnikov commented on IGNITE-7611: [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These ones are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708828#comment-16708828 ] Artem Budnikov edited comment on IGNITE-7611 at 12/4/18 3:06 PM: - [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These are difficult to comprehend and bring little value to users. Please review the changes. was (Author: artem budnikov): [~slukyanov] I updated the page adding information you requested except for the following system properties: * IGNITE_UPDATE_NOTIFIER * IGNITE_STARVATION_CHECK_INTERVAL * IGNITE_TROUBLESHOOTING_LOGGER * IGNITE_CONSOLE_APPENDER * IGNITE_GRID_CLIENT_LOG_ENABLED * IGNITE_DEV_ONLY_LOGGING_DISABLED These ones are difficult to comprehend and bring little value to users. Please review the changes. > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10524) IgniteCache.iterator() from a client node leads to OOM
Pavel Vinokurov created IGNITE-10524: Summary: IgniteCache.iterator() from a client node leads to OOM Key: IGNITE-10524 URL: https://issues.apache.org/jira/browse/IGNITE-10524 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.4 Reporter: Pavel Vinokurov Looks like "iterator()" method perform a scan query and load all cache rows into heap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708793#comment-16708793
]
ASF GitHub Bot commented on IGNITE-10457:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5538
> MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
> --
>
> Key: IGNITE-10457
> URL: https://issues.apache.org/jira/browse/IGNITE-10457
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
>
> See the log below:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow
> []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildSelfTest.putData(GridIndexRebuildSelfTest.java:191)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildWithMvccEnabledSelfTest.testIndexRebuild(GridIndexRebuildWithMvccEnabledSelfTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:2032)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:420)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:167)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:143)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:331)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:246)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2076)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:785)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2522)
[jira] [Updated] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
[ https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Daradur updated IGNITE-10523: Fix Version/s: 2.8 > Ignite Compatibility: add check that started node is of expected version > > > Key: IGNITE-10523 > URL: https://issues.apache.org/jira/browse/IGNITE-10523 > Project: Ignite > Issue Type: Improvement >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > It's necessary to check that node started in separate JVM is of a specified > version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10523) Ignite Compatibility: add check that started node is of expected version
Vyacheslav Daradur created IGNITE-10523: --- Summary: Ignite Compatibility: add check that started node is of expected version Key: IGNITE-10523 URL: https://issues.apache.org/jira/browse/IGNITE-10523 Project: Ignite Issue Type: Improvement Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur It's necessary to check that node started in separate JVM is of a specified version to avoid unexpected behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5439) JDBC thin: support query cancel
[
https://issues.apache.org/jira/browse/IGNITE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708775#comment-16708775
]
Taras Ledkov commented on IGNITE-5439:
--
[~alapin], the patch is OK with me.
[~vozerov], please review the patch.
> JDBC thin: support query cancel
> ---
>
> Key: IGNITE-5439
> URL: https://issues.apache.org/jira/browse/IGNITE-5439
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Alexander Lapin
>Priority: Major
> Fix For: 2.8
>
>
> The JDBC {{Statement.cancel}} method must be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-10521) Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node
[
https://issues.apache.org/jira/browse/IGNITE-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov resolved IGNITE-10521.
Resolution: Won't Fix
> Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on
> server node
> -
>
> Key: IGNITE-10521
> URL: https://issues.apache.org/jira/browse/IGNITE-10521
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5, 2.7
>Reporter: Sergey Kozlov
>Assignee: Ivan Bessonov
>Priority: Critical
> Fix For: 2.8
>
>
> 1. Start serve node with PDS
> 2. Run sqlline via thin driver
> 3. Execute
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE t308 ( id DATE NOT NULL, col1
> INT NOT NULL, col2 VARCHAR, PRIMARY KEY (id
> )) ;
> Error: class org.apache.ignite.IgniteCheckedException: Failed to find value
> class in the node classpath (use default mar
> shaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706 (state=5,code=0)
> java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Failed
> to find value class in the node classpath
> (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:753)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:210)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:473)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> We do not support datetime for PK but server node stopped:
> {noformat}
> [14:26:32,882][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Updating caches registry performed in 3 ms.
> [14:26:32,963][SEVERE][exchange-worker-#43][CacheAffinitySharedManager]
> Failed to initialize cache. Will try to rollback cache start routine.
> [cacheName=SQL_PUBLIC_T2]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in
> the node classpath (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T2_7080b5da_4dde_4491_b596_4a085313a98d
> at
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:451)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:700)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:860)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1212)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1972)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:880)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1065)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:696)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2582)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2462)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [14:26:32,964][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
> starting performed in 82 ms.
> [14:26:32,966][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Affinity initialization for started caches performed in 2 ms.
> [14:26:32,968][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
> Finished waiting for partition release future [topVer=AffinityTopologyVersion
> [topVer=4, minorTopVer=4], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
> [14:26:32,973][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
> Finished waiting for partitions release latch: ClientLatch
> [
[jira] [Commented] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708752#comment-16708752
]
Vladimir Ozerov commented on IGNITE-10457:
--
[~gvvinblade], changes looks good. But I do not get why we changed
"transactional_snapshot" to "transactional" in test? Could you please elaborate?
> MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
> --
>
> Key: IGNITE-10457
> URL: https://issues.apache.org/jira/browse/IGNITE-10457
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
>
> See the log below:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow
> []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildSelfTest.putData(GridIndexRebuildSelfTest.java:191)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildWithMvccEnabledSelfTest.testIndexRebuild(GridIndexRebuildWithMvccEnabledSelfTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:2032)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:420)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:167)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:143)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:331)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:246)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2076)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:785)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.ca
[jira] [Commented] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708757#comment-16708757
]
Vladimir Ozerov commented on IGNITE-10457:
--
[~gvvinblade], got it. Looks good to me then.
> MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
> --
>
> Key: IGNITE-10457
> URL: https://issues.apache.org/jira/browse/IGNITE-10457
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
>
> See the log below:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow
> []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildSelfTest.putData(GridIndexRebuildSelfTest.java:191)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildWithMvccEnabledSelfTest.testIndexRebuild(GridIndexRebuildWithMvccEnabledSelfTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:2032)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:420)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:167)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:143)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:331)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:246)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2076)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:785)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2522)
> at
> org.apache.ignite.internal.processors.ca
[jira] [Commented] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708755#comment-16708755
]
Igor Seliverstov commented on IGNITE-10457:
---
[~gvvinblade], there are two test classes for mvcc and not-mvcc cases, by
mistake both of them are run over a mvcc cache, the wrong test was changed.
> MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
> --
>
> Key: IGNITE-10457
> URL: https://issues.apache.org/jira/browse/IGNITE-10457
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
>
> See the log below:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow
> []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildSelfTest.putData(GridIndexRebuildSelfTest.java:191)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildWithMvccEnabledSelfTest.testIndexRebuild(GridIndexRebuildWithMvccEnabledSelfTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:2032)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:420)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:167)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:143)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:331)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:246)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2076)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:785)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processor
[jira] [Commented] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708747#comment-16708747
]
ASF GitHub Bot commented on IGNITE-10434:
-
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5569
IGNITE-10434
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10434
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5569.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 #5569
commit 7a911e48d66bd906a0f2287fea88d465a3e44822
Author: Igor Seliverstov
Date: 2018-12-04T14:09:04Z
pending
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10457) MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708741#comment-16708741
]
Igor Seliverstov commented on IGNITE-10457:
---
[~vozerov], Please look at
> MVCC TX: GridIndexRebuildWithMvccEnabledSelfTest fails
> --
>
> Key: IGNITE-10457
> URL: https://issues.apache.org/jira/browse/IGNITE-10457
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.8
>
>
> See the log below:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow
> []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildSelfTest.putData(GridIndexRebuildSelfTest.java:191)
> at
> org.apache.ignite.internal.processors.query.h2.GridIndexRebuildWithMvccEnabledSelfTest.testIndexRebuild(GridIndexRebuildWithMvccEnabledSelfTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1968)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:2032)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:420)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:167)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:143)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:331)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:246)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2076)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:785)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2522)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdap
[jira] [Created] (IGNITE-10522) Remote node has not joined
Anton Kalashnikov created IGNITE-10522: -- Summary: Remote node has not joined Key: IGNITE-10522 URL: https://issues.apache.org/jira/browse/IGNITE-10522 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov Sometimes tests failed because of "Remote node has not joined" suit - PDS (Indexing) example test - IgniteWalRecoveryWithCompactionTest.testLargeRandomCrash -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5115) Investigation of failing tests of coordinator node failure
[
https://issues.apache.org/jira/browse/IGNITE-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708722#comment-16708722
]
Alexey Goncharuk commented on IGNITE-5115:
--
[~NSAmelchev], why do we fail the old coordinator if a non-verified message is
received? From the explanation above I thought the message should have been
verified by another node that already became a coordinator.
[~yzhdanov], can you take a look? The change seems a bit dangerous to me,
because we fail the coordinator node when a non-verified message is received.
> Investigation of failing tests of coordinator node failure
> ---
>
> Key: IGNITE-5115
> URL: https://issues.apache.org/jira/browse/IGNITE-5115
> Project: Ignite
> Issue Type: Bug
> Components: messaging
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Tests *customEventCoordinatorFailure1/2* from *TcpDiscoverySelfTest* are
> flaky on TC and sometimes hang with the following assertion in logs:
> {code}
> Exception in thread "tcp-disco-msg-worker-#5245%tcp.TcpDiscoverySelfTest0%"
> java.lang.AssertionError
> at
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing.removeNode(TcpDiscoveryNodesRing.java:353)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeFailedMessage(ServerImpl.java:4670)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2567)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2366)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6485)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2456)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
> It seems that this happens because tests' implementation drops connections of
> *TcpCommunicatonSpi* on coordinator node with *simulateNodeFailure* method.
> At the same time tests leave *TcpDiscoverySpi* operational; it receives
> subsequent NodeFailed message and throws the assertion error shown above.
> The whole situation looks legitimate as it is possible to imagine a situation
> when CommSPI connections on coordinator fail for some reason while DiscoSPI
> connections are healthy.
> It is needed to investigate the situation deeper, figure out whether the root
> cause is using of *simulateNodeFailure* or not and propose a solution if the
> error may happen in the real life.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10446) control.sh --cache idle_verify fail with NPE when node left grid
[ https://issues.apache.org/jira/browse/IGNITE-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708717#comment-16708717 ] ASF GitHub Bot commented on IGNITE-10446: - GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5568 IGNITE-10446 control.sh --cache idle_verify fail with NPE when node l… …eft grid You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10446 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5568.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 #5568 commit 28d8fad9f201f695b837156b4524505905f50105 Author: vd-pyatkov Date: 2018-12-04T13:44:19Z IGNITE-10446 control.sh --cache idle_verify fail with NPE when node left grid > control.sh --cache idle_verify fail with NPE when node left grid > > > Key: IGNITE-10446 > URL: https://issues.apache.org/jira/browse/IGNITE-10446 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: ARomantsov >Assignee: Vladislav Pyatkov >Priority: Critical > Fix For: 2.8 > > > > Command [IDLE_VERIFY -host=***] started at [2018-11-28 15:54:23]... > Error code: 13000. java.lang.NullPointerException. > Command [IDLE_VERIFY] failed with error: 13000 - command failed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10513) Java client stucks when connects to server with slow disk
[
https://issues.apache.org/jira/browse/IGNITE-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-10513:
-
Ignite Flags: (was: Docs Required)
> Java client stucks when connects to server with slow disk
> -
>
> Key: IGNITE-10513
> URL: https://issues.apache.org/jira/browse/IGNITE-10513
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.6
>Reporter: Dmitry Lazurkin
>Priority: Major
> Attachments: ignite-client.log
>
>
> For emulating slow disk add _sleep_ to partitions cycle in
> _GridCacheDatabaseSharedManager#restorePartitionStates_:
> {noformat}
> //...
> for (int i = 0; i < grp.affinity().partitions(); i++) {
> try {
> log.error("Wait");
> Thread.sleep(1);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> //...
> {noformat}
> My server has 1024 partitions.
> Steps to reproduce:
> * Start server
> * Start client
> * On client wait message "Join cluster while cluster state transition is in
> progress, waiting when transition finish."
> * Kill server
> * On client wait repeatable java.net.ConnectException: Connection refused
> (Connection refused)
> * Start server (I have 100% chance to reproduce issue on my computer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10521) Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node
[
https://issues.apache.org/jira/browse/IGNITE-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708712#comment-16708712
]
Ivan Bessonov commented on IGNITE-10521:
Hi [~skozlov], this problem was fixed in IGNITE-8640. As far as I know that
issue is already backported for 2.5 and 2.7 future releases, please confirm it.
> Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on
> server node
> -
>
> Key: IGNITE-10521
> URL: https://issues.apache.org/jira/browse/IGNITE-10521
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5, 2.7
>Reporter: Sergey Kozlov
>Assignee: Ivan Bessonov
>Priority: Critical
> Fix For: 2.8
>
>
> 1. Start serve node with PDS
> 2. Run sqlline via thin driver
> 3. Execute
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE t308 ( id DATE NOT NULL, col1
> INT NOT NULL, col2 VARCHAR, PRIMARY KEY (id
> )) ;
> Error: class org.apache.ignite.IgniteCheckedException: Failed to find value
> class in the node classpath (use default mar
> shaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706 (state=5,code=0)
> java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Failed
> to find value class in the node classpath
> (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:753)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:210)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:473)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> We do not support datetime for PK but server node stopped:
> {noformat}
> [14:26:32,882][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Updating caches registry performed in 3 ms.
> [14:26:32,963][SEVERE][exchange-worker-#43][CacheAffinitySharedManager]
> Failed to initialize cache. Will try to rollback cache start routine.
> [cacheName=SQL_PUBLIC_T2]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in
> the node classpath (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T2_7080b5da_4dde_4491_b596_4a085313a98d
> at
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:451)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:700)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:860)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1212)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1972)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:880)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1065)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:696)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2582)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2462)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [14:26:32,964][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
> starting performed in 82 ms.
> [14:26:32,966][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Affinity initialization for started caches performed in 2 ms.
> [14:26:32,968][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
> Finished waiting for partition release future [topVer=AffinityTopologyVersion
> [topVer=4, minorTopVer=4],
[jira] [Assigned] (IGNITE-10521) Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on server node
[
https://issues.apache.org/jira/browse/IGNITE-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov reassigned IGNITE-10521:
--
Assignee: Ivan Bessonov
> Creating table with datetime for PK leads to j.l.IndexOutOfBoundsException on
> server node
> -
>
> Key: IGNITE-10521
> URL: https://issues.apache.org/jira/browse/IGNITE-10521
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5, 2.7
>Reporter: Sergey Kozlov
>Assignee: Ivan Bessonov
>Priority: Critical
> Fix For: 2.8
>
>
> 1. Start serve node with PDS
> 2. Run sqlline via thin driver
> 3. Execute
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE t308 ( id DATE NOT NULL, col1
> INT NOT NULL, col2 VARCHAR, PRIMARY KEY (id
> )) ;
> Error: class org.apache.ignite.IgniteCheckedException: Failed to find value
> class in the node classpath (use default mar
> shaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706 (state=5,code=0)
> java.sql.SQLException: class org.apache.ignite.IgniteCheckedException: Failed
> to find value class in the node classpath
> (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T308_bb0725c8_7db7_4309_8f4a_a63d2fffa706
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:753)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:210)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:473)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> We do not support datetime for PK but server node stopped:
> {noformat}
> [14:26:32,882][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Updating caches registry performed in 3 ms.
> [14:26:32,963][SEVERE][exchange-worker-#43][CacheAffinitySharedManager]
> Failed to initialize cache. Will try to rollback cache start routine.
> [cacheName=SQL_PUBLIC_T2]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in
> the node classpath (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T2_7080b5da_4dde_4491_b596_4a085313a98d
> at
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:451)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:700)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:860)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1212)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1972)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:880)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1065)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:696)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2582)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2462)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [14:26:32,964][INFO][exchange-worker-#43][CacheAffinitySharedManager] Caches
> starting performed in 82 ms.
> [14:26:32,966][INFO][exchange-worker-#43][CacheAffinitySharedManager]
> Affinity initialization for started caches performed in 2 ms.
> [14:26:32,968][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
> Finished waiting for partition release future [topVer=AffinityTopologyVersion
> [topVer=4, minorTopVer=4], waitTime=0ms, futInfo=NA, mode=DISTRIBUTED]
> [14:26:32,973][INFO][exchange-worker-#43][GridDhtPartitionsExchangeFuture]
> Finished waiting for partitions release latch: ClientLat
[jira] [Comment Edited] (IGNITE-10450) In Ignite code style inspections increase level for those used at Teamcity build checks
[
https://issues.apache.org/jira/browse/IGNITE-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708687#comment-16708687
]
Oleg Ignatenko edited comment on IGNITE-10450 at 12/4/18 1:21 PM:
--
(i) Per referred discussion at dev list suggested changes were merged to master
as a part of IGNITE-10422 and are now included in project default inspections
profile.
As for this ticket, I plan to keep it open for a little while for just the case
if we quickly decide to do some adjustments. Then I plan to close it (assuming
that if we will want to change something later this could be done per new
tickets).
was (Author: oignatenko):
(i) Per referred discussion at dev list suggested changes were merged to master
as a part of IGNITE-10450 and are now included in project default inspections
profile.
As for this ticket, I plan to keep it open for a little while for just the case
if we quickly decide to do some adjustments. Then I plan to close it (assuming
that if we will want to change something later this could be done per new
tickets).
> In Ignite code style inspections increase level for those used at Teamcity
> build checks
> ---
>
> Key: IGNITE-10450
> URL: https://issues.apache.org/jira/browse/IGNITE-10450
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: IDEA.inspections.TC-bot.obscured.png,
> IDEA.inspections.TC-bot.png
>
>
> Some of [Ignite code
> style|https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines]
> inspections are verified at Teamcity per IGNITE-9983. (Currently TC
> inspections are "SizeReplaceableByIsEmpty", "UnusedImport",
> "MissingOverrideAnnotation", "MissortedModifiers", "RedundantSuppression".)
> Per discussion of issue IGNITE-10399 it looks like there is a room for
> improvement here. Specifically, the problem occurred because it was too
> difficult to find a new deviation that made TC inspections check fail because
> it was buried among multiple similar looking but non-critical deviations in a
> particular piece of old code
> ([PageMemoryImpl.java|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/pagemem/PageMemoryImpl.java]).
> It would be more convenient if programmer could easier see subset of checks
> that are used at Teamcity because this would allow to fix these earlier and
> avoid cumbersome TC runs and failure reports analysis.
> Technically this could be achieved by editing inspections config file and
> increasing respective inspections level to {{ERROR}}. I briefly checked how
> it would work in a "sandbox" project on my machine and it looked quite
> convenient: violations of inspections used by TC were shown as red in Error
> Stripe while the rest remained yellow, easy to see. (It's probably not very
> important but for the sake of completeness a thing I noticed when testing is
> that having red inspections didn't block compilation and execution of the
> code.) Screen shot of how it worked in my experiment is attached:
> [^IDEA.inspections.TC-bot.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10450) In Ignite code style inspections increase level for those used at Teamcity build checks
[
https://issues.apache.org/jira/browse/IGNITE-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708687#comment-16708687
]
Oleg Ignatenko commented on IGNITE-10450:
-
(i) Per referred discussion at dev list suggested changes were merged to master
as a part of IGNITE-10450 and are now included in project default inspections
profile.
As for this ticket, I plan to keep it open for a little while for just the case
if we quickly decide to do some adjustments. Then I plan to close it (assuming
that if we will want to change something later this could be done per new
tickets).
> In Ignite code style inspections increase level for those used at Teamcity
> build checks
> ---
>
> Key: IGNITE-10450
> URL: https://issues.apache.org/jira/browse/IGNITE-10450
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: IDEA.inspections.TC-bot.obscured.png,
> IDEA.inspections.TC-bot.png
>
>
> Some of [Ignite code
> style|https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines]
> inspections are verified at Teamcity per IGNITE-9983. (Currently TC
> inspections are "SizeReplaceableByIsEmpty", "UnusedImport",
> "MissingOverrideAnnotation", "MissortedModifiers", "RedundantSuppression".)
> Per discussion of issue IGNITE-10399 it looks like there is a room for
> improvement here. Specifically, the problem occurred because it was too
> difficult to find a new deviation that made TC inspections check fail because
> it was buried among multiple similar looking but non-critical deviations in a
> particular piece of old code
> ([PageMemoryImpl.java|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/pagemem/PageMemoryImpl.java]).
> It would be more convenient if programmer could easier see subset of checks
> that are used at Teamcity because this would allow to fix these earlier and
> avoid cumbersome TC runs and failure reports analysis.
> Technically this could be achieved by editing inspections config file and
> increasing respective inspections level to {{ERROR}}. I briefly checked how
> it would work in a "sandbox" project on my machine and it looked quite
> convenient: violations of inspections used by TC were shown as red in Error
> Stripe while the rest remained yellow, easy to see. (It's probably not very
> important but for the sake of completeness a thing I noticed when testing is
> that having red inspections didn't block compilation and execution of the
> code.) Screen shot of how it worked in my experiment is attached:
> [^IDEA.inspections.TC-bot.png]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
