[jira] [Commented] (IGNITE-10731) ZookeeperDiscoverySpiTestSuite4: IgniteCacheReplicatedQuerySelfTest.testNodeLeft fails
[
https://issues.apache.org/jira/browse/IGNITE-10731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724904#comment-16724904
]
Dmitriy Pavlov commented on IGNITE-10731:
-
Hi [~Jokser] could you please take a look?
> ZookeeperDiscoverySpiTestSuite4:
> IgniteCacheReplicatedQuerySelfTest.testNodeLeft fails
> --
>
> Key: IGNITE-10731
> URL: https://issues.apache.org/jira/browse/IGNITE-10731
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :0
> Actual :312
>
> 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.distributed.replicated.IgniteCacheReplicatedQuerySelfTest.testNodeLeft(IgniteCacheReplicatedQuerySelfTest.java:348)
> 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:151)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2102)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2117)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8131) ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* tests fail on TC
[
https://issues.apache.org/jira/browse/IGNITE-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724832#comment-16724832
]
Dmitriy Pavlov commented on IGNITE-8131:
[~zstan] thank you for noticing that. [~garus.d.g] could you please remove
fail(), unmute test. By lazy consensus, I will do it in 72h, but anyway, if the
author will do the removal, it reduces the risk of introducing new failures to
master.
> ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* tests fail on TC
>
>
> Key: IGNITE-8131
> URL: https://issues.apache.org/jira/browse/IGNITE-8131
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Denis Garus
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments: ZK_client_reconnect_failure.log,
> ZK_client_reconnect_success.log
>
>
> Two tests always fail on TC with the assertion
> {noformat}
> junit.framework.AssertionFailedError: Failed to wait for disconnect/reconnect
> event.
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.waitReconnectEvent(ZookeeperDiscoverySpiTest.java:4221)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectClientNodes(ZookeeperDiscoverySpiTest.java:4183)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.clientReconnectSessionExpire(ZookeeperDiscoverySpiTest.java:2231)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testClientReconnectSessionExpire1_1(ZookeeperDiscoverySpiTest.java:2206)
> {noformat}
> from client disconnect/reconnect events check. Obviously client doesn't
> generate these events as it supposed to do.
> (TC runs can be found
> [here|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteZooKeeperDiscovery&branch_IgniteTests24Java8=pull%2F3730%2Fhead&tab=buildTypeStatusDiv]).
> It is possible to reproduce test failure locally as well, but with low
> probability: one failure for 50 or even 300 successful executions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10709) New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on TC configuration
[
https://issues.apache.org/jira/browse/IGNITE-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724103#comment-16724103
]
Dmitriy Pavlov commented on IGNITE-10709:
-
Blockers came from https://issues.apache.org/jira/browse/IGNITE-10723 fix, not
related to this issue.
> New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on
> TC configuration
> --
>
> Key: IGNITE-10709
> URL: https://issues.apache.org/jira/browse/IGNITE-10709
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
>
> IntelliJ IDEA since 2018.1 version has new inspection rules enabled by
> default. This leads to the {{[Inspections] Core}} suite fail as these rules
> are not fixed in the Apache Ignite project code.
> # We need to add and disable them in {{ignite_inspections_teamcity.xml}}
> configuration file.
> # Remove unnecessary suppression according to {{Redundant suppression}} rule
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10723) Investigate failures related to enabling tests (IGNITE-1094)
[ https://issues.apache.org/jira/browse/IGNITE-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10723: Labels: MakeTeamcityGreenAgain (was: ) > Investigate failures related to enabling tests (IGNITE-1094) > > > Key: IGNITE-10723 > URL: https://issues.apache.org/jira/browse/IGNITE-10723 > Project: Ignite > Issue Type: Test >Affects Versions: 2.7 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: MakeTeamcityGreenAgain > > The following tests were muted due to IGNITE-1094: > * IgniteChangeGlobalStateTest.testActivateAfterFailGetLock > * CacheHibernateStoreFactorySelfTest.testIncorrectBeanConfiguration > (Hibernate-4.2) > * CacheHibernateStoreFactorySelfTest.testIncorrectBeanConfiguration > (Hibernate-5.1) > * IgniteSqlSchemaIndexingTest.testCaseSensitive > * IgniteSqlSchemaIndexingTest.testCustomSchemaMultipleCachesTablesCollision > * GridPartitionedCacheJtaLookupClassNameSelfTest.testIncompatibleTmLookup > * CacheJdbcBlobStoreFactorySelfTest.testIncorrectBeanConfiguration > * CacheJdbcPojoStoreFactorySelfTest.testIncorrectBeanConfiguration > These test should be analyzed and enabled on the TC if possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-1112) Atomic cache #get method returns old value if near cache enabled after second putAll.
[
https://issues.apache.org/jira/browse/IGNITE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-1112:
---
Labels: MakeTeamcityGreenAgain Muted_test (was: MakeTeamcityGreenAgain)
> Atomic cache #get method returns old value if near cache enabled after second
> putAll.
> -
>
> Key: IGNITE-1112
> URL: https://issues.apache.org/jira/browse/IGNITE-1112
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> These tests failed:
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll
> GridCacheAtomicNearEnabledFairAffinityMultiJvmFullApiSelfTest.testPutAllPutAll
>
> These tests work fine in one jvm, but fails in multi-JVM case.
> Looks like, second putAll does not update data at near cache and get method
> returns old value. But iteration from cache return actual data.
> See ignite-648-putAll branch with more debug information.
> Original log for
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll.
> {noformat}
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> 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:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridCachePartitionedMultiNodeFullApiSelfTest.testPutAllPutAll(GridCachePartitionedMultiNodeFullApiSelfTest.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 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:1618)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1561)
> --- Stdout: ---
> [17:59:33,524][INFO ][main][root] >>> Starting test: testPutAllPutAll <<<
> [17:59:33,527][INFO ][test-runner][root] > Grid0:
> 00ac324c-cfd0-4433-b00b-1048858b6000
> [17:59:33,528][INFO ][test-runner][root] > Grid1:
> 0a0c6919-127f-4d44-988d-8a236d033379
> [17:59:33,530][INFO ][test-runner][root] > Grid2:
> 17e5a787-5b00-4c68-88ea-cf0e393fefd1
> [17:59:33,531][INFO ][test-runner][root] > Grid3:
> d63de793-e754-4849-826e-2f43669385ba
> [17:59:33,544][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,544][INFO][ignite-#12%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$10
> [17:59:33,736][INFO ][test-runner][root] >>> Before second put.
> [17:59:33,736][INFO ][test-runner][GridDeploymentLocalStore] Class locally
> deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,741][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,741][INFO][ignite-#16%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,757][INFO ][test-runner][root] >>> After second put.
> [17:59:33,766][INFO ][main][root] >>> Stopping test: testPutAllPutAll in 240
> ms <<<
> [17:59:33,766][INFO ][main][root] Checking grid: 0
> [17:59:33,787][INFO ][main][root] Size after [idx=0, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries
> []]
> [17:59:33,787][INFO ][main][root] Checking grid: 1
> [17:59:33,812][INFO ][main][root] Size after [idx=1, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,815][INFO ][main][root] Checking grid: 2
> [17:59:33,839][INFO ][main][root] Size after [idx=2, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,842][INFO ][main][root] Checking grid: 3
> [17:59:33,866][INFO ][main][root] Size after [idx=3, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> --- Stderr: ---
> [17:59:33,765][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> a
[jira] [Updated] (IGNITE-1112) Atomic cache #get method returns old value if near cache enabled after second putAll.
[
https://issues.apache.org/jira/browse/IGNITE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-1112:
---
Labels: MakeTeamcityGreenAgain (was: )
> Atomic cache #get method returns old value if near cache enabled after second
> putAll.
> -
>
> Key: IGNITE-1112
> URL: https://issues.apache.org/jira/browse/IGNITE-1112
> Project: Ignite
> Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Andrey Gura
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> These tests failed:
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll
> GridCacheAtomicNearEnabledFairAffinityMultiJvmFullApiSelfTest.testPutAllPutAll
>
> These tests work fine in one jvm, but fails in multi-JVM case.
> Looks like, second putAll does not update data at near cache and get method
> returns old value. But iteration from cache return actual data.
> See ignite-648-putAll branch with more debug information.
> Original log for
> GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest.testPutAllPutAll.
> {noformat}
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> 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:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridCachePartitionedMultiNodeFullApiSelfTest.testPutAllPutAll(GridCachePartitionedMultiNodeFullApiSelfTest.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 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:1618)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:70)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1561)
> --- Stdout: ---
> [17:59:33,524][INFO ][main][root] >>> Starting test: testPutAllPutAll <<<
> [17:59:33,527][INFO ][test-runner][root] > Grid0:
> 00ac324c-cfd0-4433-b00b-1048858b6000
> [17:59:33,528][INFO ][test-runner][root] > Grid1:
> 0a0c6919-127f-4d44-988d-8a236d033379
> [17:59:33,530][INFO ][test-runner][root] > Grid2:
> 17e5a787-5b00-4c68-88ea-cf0e393fefd1
> [17:59:33,531][INFO ][test-runner][root] > Grid3:
> d63de793-e754-4849-826e-2f43669385ba
> [17:59:33,544][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,544][INFO][ignite-#12%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$10
> [17:59:33,736][INFO ][test-runner][root] >>> Before second put.
> [17:59:33,736][INFO ][test-runner][GridDeploymentLocalStore] Class locally
> deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,741][INFO ][Thread-110][jvm-0a0c6919]
> [17:59:33,741][INFO][ignite-#16%pub-multijvm.GridCacheAtomicNearEnabledMultiJvmFullApiSelfTest1%][GridDeploymentLocalStore]
> Class locally deployed: class
> org.apache.ignite.testframework.junits.multijvm.IgniteCacheProcessProxy$17
> [17:59:33,757][INFO ][test-runner][root] >>> After second put.
> [17:59:33,766][INFO ][main][root] >>> Stopping test: testPutAllPutAll in 240
> ms <<<
> [17:59:33,766][INFO ][main][root] Checking grid: 0
> [17:59:33,787][INFO ][main][root] Size after [idx=0, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=CacheLocalEntries
> []]
> [17:59:33,787][INFO ][main][root] Checking grid: 1
> [17:59:33,812][INFO ][main][root] Size after [idx=1, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,815][INFO ][main][root] Checking grid: 2
> [17:59:33,839][INFO ][main][root] Size after [idx=2, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> [17:59:33,842][INFO ][main][root] Checking grid: 3
> [17:59:33,866][INFO ][main][root] Size after [idx=3, size=0, keySize=0,
> primarySize=0, globalSize=0, globalPrimarySize=0, entrySet=[]]
> --- Stderr: ---
> [17:59:33,765][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: expected:<64> but was:<8>
> at junit.framework.Assert.fail(Assert.java:57)
[jira] [Commented] (IGNITE-10708) SQL implement system view for partition states
[ https://issues.apache.org/jira/browse/IGNITE-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723166#comment-16723166 ] Dmitriy Pavlov commented on IGNITE-10708: - [~alex_pl] could you please mention any potential reviewer directly in comments? > SQL implement system view for partition states > -- > > Key: IGNITE-10708 > URL: https://issues.apache.org/jira/browse/IGNITE-10708 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-13 > Fix For: 2.8 > > > Implement SQL system view to partition states in the cluster for each cache > group and each node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10709) New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on TC configuration
[
https://issues.apache.org/jira/browse/IGNITE-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10709:
Fix Version/s: 2.8
> New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on
> TC configuration
> --
>
> Key: IGNITE-10709
> URL: https://issues.apache.org/jira/browse/IGNITE-10709
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
>
> IntelliJ IDEA since 2018.1 version has new inspection rules enabled by
> default. This leads to the {{[Inspections] Core}} suite fail as these rules
> are not fixed in the Apache Ignite project code.
> # We need to add and disable them in {{ignite_inspections_teamcity.xml}}
> configuration file.
> # Remove unnecessary suppression according to {{Redundant suppression}} rule
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-845) TcpDiscoveryCloudIpFinderSelfTest.testAmazonWebServices always fails on public TC
[ https://issues.apache.org/jira/browse/IGNITE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723079#comment-16723079 ] Dmitriy Pavlov commented on IGNITE-845: --- Removed test from code here https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=8cb502bc9da52aca39d4dc067a6b36a298c6b376 Feel free to add a test back if it will be covered by any open test-fix issue. > TcpDiscoveryCloudIpFinderSelfTest.testAmazonWebServices always fails on > public TC > - > > Key: IGNITE-845 > URL: https://issues.apache.org/jira/browse/IGNITE-845 > Project: Ignite > Issue Type: Bug >Affects Versions: sprint-4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > > AWS didn't authorize us when the amazon test is run on the public TC from > docker containers. Everything is fine on the private TC (configuration is > identical on both TCs). Noted that ignite-aws module's tests are also failing > on the public TC. Probably there is some docker + aws related issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10314) Spark dataframe will get wrong schema if user executes add/drop column DDL
[ https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723013#comment-16723013 ] Dmitriy Pavlov commented on IGNITE-10314: - [~ldz] thank you, I've retriggered couple suites on TC for PR 5598 License& headers were broken in the master, so it is not related to the PR. > Spark dataframe will get wrong schema if user executes add/drop column DDL > -- > > Key: IGNITE-10314 > URL: https://issues.apache.org/jira/browse/IGNITE-10314 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > When user performs add/remove column in DDL, Spark will get the old/wrong > schema. > > Analyse > Currently Spark data frame API relies on QueryEntity to construct schema, but > QueryEntity in QuerySchema is a local copy of the original QueryEntity, so > the original QueryEntity is not updated when modification happens. > > Solution > Get the latest schema using JDBC thin driver's column metadata call, then > update fields in QueryEntity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16722937#comment-16722937
]
Dmitriy Pavlov commented on IGNITE-9213:
[~sboikov], yes I'm going to add support. There is no ticket for that, but
anyway, it is not so complicated to do.
> 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
>Assignee: Semen Boikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> 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-10707) BinaryField: Allow checking NULL-value without reading value
[ https://issues.apache.org/jira/browse/IGNITE-10707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722854#comment-16722854 ] Dmitriy Pavlov commented on IGNITE-10707: - [~dmitry.lazurkin] please fill ticket description. Why this change is needed? You can also provide an example of failing of check nulls, reproducer. > BinaryField: Allow checking NULL-value without reading value > > > Key: IGNITE-10707 > URL: https://issues.apache.org/jira/browse/IGNITE-10707 > Project: Ignite > Issue Type: Improvement > Components: binary >Reporter: Dmitry Lazurkin >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16722851#comment-16722851
]
Dmitriy Pavlov edited comment on IGNITE-9213 at 12/17/18 10:26 AM:
---
[~sboikov] TC Bot does not support branches for automatic mode now, but it
supports PRs. As a workaround, it is possible to create PR using branch in
Apache git.
was (Author: dpavlov):
[~sboikov] TC Bot do not support branches for automatic mode, but it supports
PRs. As a workaround, it is possible to create PR using branch in Apache git.
> 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
>Assignee: Semen Boikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> 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.
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16722851#comment-16722851
]
Dmitriy Pavlov commented on IGNITE-9213:
[~sboikov] TC Bot do not support branches for automatic mode, but it supports
PRs. As a workaround, it is possible to create PR using branch in Apache git.
> 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
>Assignee: Semen Boikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> 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] [Updated] (IGNITE-4015) Continuous query events could be lost on backup node when primary leaves (transactional cache).
[ https://issues.apache.org/jira/browse/IGNITE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4015: --- Labels: MakeTeamcityGreenAgain transactions (was: transactions) > Continuous query events could be lost on backup node when primary leaves > (transactional cache). > --- > > Key: IGNITE-4015 > URL: https://issues.apache.org/jira/browse/IGNITE-4015 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6, 1.7 >Reporter: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain, transactions > > Consider the following scenario: > 1) One stable node in topology; > 2) PARTITIONED, TRANSACTIONAL cache with 1 backup; > 3) Continuous query is set on the cache; > 4) Put some data to cache. > If another node joins the cluster, it will handle some updates. > But when it leaves the topology during put transaction, transaction rolled > back with retry and events are lost. > Reproducer can be found in > org.apache.ignite.loadtests.continuous.CacheContinuousQueryFailoverTxPrimaryWriteOrderLoadTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-2229) Full text queries do not return valid results on unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-2229: --- Labels: MakeTeamcityGreenAgain (was: ) > Full text queries do not return valid results on unstable topology > -- > > Key: IGNITE-2229 > URL: https://issues.apache.org/jira/browse/IGNITE-2229 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > > Added test > org.apache.ignite.internal.processors.cache.IgniteCacheFullTextQueryNodeJoiningSelfTest > that fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9328) IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write.
[ https://issues.apache.org/jira/browse/IGNITE-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9328: --- Ignite Flags: (was: Docs Required) > IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write. > -- > > Key: IGNITE-9328 > URL: https://issues.apache.org/jira/browse/IGNITE-9328 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Assignee: Stanislav Lukyanov >Priority: Major > Labels: MakeTeamcityGreenAgain > > After I have re-enabled it in IGNITE-9220 it started failing. I have also > migrated it to multiJvm. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9328) IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write.
[ https://issues.apache.org/jira/browse/IGNITE-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9328: --- Labels: MakeTeamcityGreenAgain (was: ) > IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write. > -- > > Key: IGNITE-9328 > URL: https://issues.apache.org/jira/browse/IGNITE-9328 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Assignee: Stanislav Lukyanov >Priority: Major > Labels: MakeTeamcityGreenAgain > > After I have re-enabled it in IGNITE-9220 it started failing. I have also > migrated it to multiJvm. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721494#comment-16721494
]
Dmitriy Pavlov commented on IGNITE-4440:
[~kuaw26] kindly reminder
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions
[
https://issues.apache.org/jira/browse/IGNITE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-4890:
--
Assignee: Venky Kandaswamy
> Unable to create tables automatically because 'unconfigured columnfamily'
> error is not handled for older Cassandra versions
> ---
>
> Key: IGNITE-4890
> URL: https://issues.apache.org/jira/browse/IGNITE-4890
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
>Reporter: Venky Kandaswamy
>Assignee: Venky Kandaswamy
>Priority: Major
> Labels: patch
>
> PROBLEM:
> When running Ignite with older Cassandra versions (i.e DSE 4.8.10, Cassandra
> 2.1.6 or older), we noticed that only the first tabel in an Ignite config is
> created and the others fail with 'unconfigured columnfamily' exception.
> SUGGESTED FIX:
> It appears that the error from Cassandra is changed in newer versions to
> 'unconfigured table ...' and this is handled. The conditions checked in
> org.apache.ignite.cache.store.cassandra.common.CassandraHelper needs to be
> modified to handle the older Cassandra errors.
> We are submitting a patch to do that.
> 13:44:28,753 ERROR com.walmartlabs.qarth.ignite.tests.utils.CacheStoreHelper
> [main] - Failed to execute Cassandra CQL statement: insert into
> "test1"."blob_test2" ("key", "value") values (?,?);
> class org.apache.ignite.IgniteException: Failed to execute Cassandra CQL
> statement: insert into "test1"."blob_test2" ("key", "value") values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:163)
> at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.write(CassandraCacheStore.java:276)
> at
> com.walmartlabs.qarth.ignite.tests.cassandra.CassandraDirectPersistenceTest.blobStrategyTest(CassandraDirectPersistenceTest.java:233)
> 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:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: class org.apache.ignite.IgniteException: Failed to prepare
> Cassandra CQL statement: insert into "test1"."blob_test2" ("key", "value")
> values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.prepareStatement(CassandraSessionImpl.java:615)
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:133)
> ... 27 more
> Caused by: com.datastax.driver.core.exceptions.InvalidQueryException:
> unconfigured columnfamily blob_test2
> at
> com.datastax.driver.core.exceptions.Invali
[jira] [Comment Edited] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721495#comment-16721495
]
Dmitriy Pavlov edited comment on IGNITE-4440 at 12/14/18 3:00 PM:
--
[~prokofyev] could you please assign the issue to yourself? I've added you to
list of contributors.
was (Author: dpavlov):
[~prokofyev] could you please assign the issue to yourself. I've added you to
list of contributors.
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721495#comment-16721495
]
Dmitriy Pavlov commented on IGNITE-4440:
[~prokofyev] could you please assign the issue to yourself. I've added you to
list of contributors.
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions
[
https://issues.apache.org/jira/browse/IGNITE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721490#comment-16721490
]
Dmitriy Pavlov commented on IGNITE-4890:
[~venky1963] could you assign the issue to yourself? It will be easier for
committers to find it. Now It is unassigned but patch available.
> Unable to create tables automatically because 'unconfigured columnfamily'
> error is not handled for older Cassandra versions
> ---
>
> Key: IGNITE-4890
> URL: https://issues.apache.org/jira/browse/IGNITE-4890
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
>Reporter: Venky Kandaswamy
>Priority: Major
> Labels: patch
>
> PROBLEM:
> When running Ignite with older Cassandra versions (i.e DSE 4.8.10, Cassandra
> 2.1.6 or older), we noticed that only the first tabel in an Ignite config is
> created and the others fail with 'unconfigured columnfamily' exception.
> SUGGESTED FIX:
> It appears that the error from Cassandra is changed in newer versions to
> 'unconfigured table ...' and this is handled. The conditions checked in
> org.apache.ignite.cache.store.cassandra.common.CassandraHelper needs to be
> modified to handle the older Cassandra errors.
> We are submitting a patch to do that.
> 13:44:28,753 ERROR com.walmartlabs.qarth.ignite.tests.utils.CacheStoreHelper
> [main] - Failed to execute Cassandra CQL statement: insert into
> "test1"."blob_test2" ("key", "value") values (?,?);
> class org.apache.ignite.IgniteException: Failed to execute Cassandra CQL
> statement: insert into "test1"."blob_test2" ("key", "value") values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:163)
> at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.write(CassandraCacheStore.java:276)
> at
> com.walmartlabs.qarth.ignite.tests.cassandra.CassandraDirectPersistenceTest.blobStrategyTest(CassandraDirectPersistenceTest.java:233)
> 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:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: class org.apache.ignite.IgniteException: Failed to prepare
> Cassandra CQL statement: insert into "test1"."blob_test2" ("key", "value")
> values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.prepareStatement(CassandraSessionImpl.java:615)
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:133)
> ... 27 more
> Caused by: com.datastax.driver.core.exception
[jira] [Commented] (IGNITE-9747) [ML] Add Bernoulli Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721479#comment-16721479 ] Dmitriy Pavlov commented on IGNITE-9747: [~chief] could you please take a look? > [ML] Add Bernoulli Naive Bayes classifier > - > > Key: IGNITE-9747 > URL: https://issues.apache.org/jira/browse/IGNITE-9747 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Ravil Galeyev >Assignee: Ravil Galeyev >Priority: Major > Fix For: 2.8 > > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > [Bernoulli Naive > Bayes|http://scikit-learn.org/stable/modules/naive_bayes.html#bernoulli-naive-bayes] > implements the naive Bayes training and classification algorithms for data > that is distributed according to multivariate Bernoulli distributions; i.e., > there may be multiple features but each one is assumed to be a binary-valued > (Bernoulli, boolean) variable. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5714) Implementation of suspend/resume for pessimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721488#comment-16721488 ] Dmitriy Pavlov commented on IGNITE-5714: [~agoncharuk] please share your vision should we do both tickets simultaneously? > Implementation of suspend/resume for pessimistic transactions > - > > Key: IGNITE-5714 > URL: https://issues.apache.org/jira/browse/IGNITE-5714 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > > Support transaction suspend()\resume() operations for pessimistic > transactions. Resume can be called in another thread. >_+But there is a problem+_: Imagine, we started pessimistic transaction in > thread T1 and then perform put operation, which leads to sending > GridDistributedLockRequest to another node. Lock request contains thread id > of the transaction. Then we call suspend, resume in another thread and we > also must send messages to other nodes to change thread id. > It seems complicated task.It’s better to get rid of sending thread id to the > nodes. > We can use transaction xid on other nodes instead of thread id. Xid is sent > to nodes in GridDistributedLockRequest#nearXidVer >_+Proposed solution+_ : On remote nodes instead of thread id of near > transaction GridDistributedLockRequest#threadId use its xid > GridDistributedLockRequest#nearXidVer. > Remove usages of near transaction's thread id on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8823) Incorrect transaction state in tx manager
[
https://issues.apache.org/jira/browse/IGNITE-8823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721487#comment-16721487
]
Dmitriy Pavlov commented on IGNITE-8823:
[~andrey-kuznetsov] [~agura] is this fix ready for review?
> Incorrect transaction state in tx manager
> -
>
> Key: IGNITE-8823
> URL: https://issues.apache.org/jira/browse/IGNITE-8823
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: Ignite8823ReproducerTest.java
>
>
> Reproducable by test method {{testCreateConsistencyMultithreaded}} in
> {{IgfsPrimaryMultiNodeSelfTest}} and
> {{IgfsPrimaryRelaxedConsistencyMultiNodeSelfTest}}:
> {noformat}
> 18:34:40,701][SEVERE][sys-stripe-0-#44%ignite%][GridCacheIoManager] Failed
> processing message [senderId=e273c3f8-02ed-4201-9ac8-09f9ab6a1d31,
> msg=GridNearTxPrepareResponse [pending=[],
> futId=b4df8831461-9735f9d5-79a0-47a3-a951-e62a03af71ef, miniId=1,
> dhtVer=GridCacheVersion [topVer=140816081, order=1529336085358, nodeOrder=3],
> writeVer=GridCacheVersion [topVer=140816081, order=1529336085360,
> nodeOrder=3], ownedVals=null, retVal=GridCacheReturn [v=null, cacheObj=null,
> success=true, invokeRes=true, loc=true, cacheId=0], clientRemapVer=null,
> super=GridDistributedTxPrepareResponse
> [txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false],
> part=-1, err=null, super=GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=140816081, order=1529336085224, nodeOrder=1], committedVers=null,
> rolledbackVers=null, cnt=0, super=GridCacheIdMessage [cacheId=0]
> java.lang.AssertionError: true instead of GridCacheReturnCompletableWrapper
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.removeTxReturn(IgniteTxManager.java:1098)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.ackBackup(GridNearTxFinishFuture.java:533)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:500)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:417)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3341)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundFuture.onDone(GridCacheCompoundFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onComplete(GridNearOptimisticTxPrepareFuture.java:310)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:288)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:78)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:144)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
>
[jira] [Commented] (IGNITE-9026) Two levels of Peer class loading fails in CONTINUOUS mode
[ https://issues.apache.org/jira/browse/IGNITE-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721485#comment-16721485 ] Dmitriy Pavlov commented on IGNITE-9026: [~akalashnikov], what can be our next steps? should we move the issue to Open? > Two levels of Peer class loading fails in CONTINUOUS mode > - > > Key: IGNITE-9026 > URL: https://issues.apache.org/jira/browse/IGNITE-9026 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: David Harvey >Assignee: David Harvey >Priority: Major > Fix For: 2.8 > > Attachments: master_1b3742f4d7_p2p_two_hops.patch > > > We had an seemingly functional system in SHARED_MODE, where we have a custom > StreamReceiver that sometimes sends closures on the peer class loaded code to > other servers. However, we ended up running out of Metaspace, because we had > > 6000 class loaders! We suspected a regression in this change > [https://github.com/apache/ignite/commit/d2050237ee2b760d1c9cbc906b281790fd0976b4#diff-3fae20691c16a617d0c6158b0f61df3c], > so we switched to CONTINUOUS mode. We then started getting failures to > load some of the classes for the closures on the second server. Through > some testing and code inspection, there seems to be the following flaws > between GridDeploymentCommunication.sendResourceRequest and its two callers. > The callers iterate though all the participant nodes until they find an > online node that responds to the request (timeout is treated as offline > node), with either success or failure, and then the loop terminates. The > assumption is that all nodes are equally capable of providing the resource, > so if one fails, then the others would also fail. > The first flaw is that GridDeploymentCommunication.sendResourceRequest() has > a check for a cycle, i.e., whether the destination node is one of the nodes > that originated or forwarded this request, and in that case, a failure > response is faked. However, that causes the caller's loop to terminate. So > depending on the order of the nodes in the participant list, > sendResourceRequest() may fail before trying any nodes because it has one of > the calling nodes on this list. It should instead be skipping any of the > calling nodes. > Example with 1 client node a 2 server nodes: C1 sends data to S1, which > forwards closure to S2. C1 also sends to S2 which forwards to S1. So now > the node lists on S1 and S2 contain C1 and the other S node. If the order > of the node lists on S1 is (S2,C1) and on S2 (S1,C1), then when S1 tries to > load a class, it will try S2, then S2 will try S1, but will get a fake > failure generated, causing S2 not to try more nodes (i.e., C1), and causing > S1 also not to try more nodes. > The other flaw is the assumption that all participants have equal access to > the resource. Assume S1 knows about userVersion1 via S3 and S4, with S3 > though C1 and S4 through C2. If C2 fails, then S4 is not capable of getting > back to a master, but S1 has no way of knowing that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721484#comment-16721484 ] Dmitriy Pavlov commented on IGNITE-7616: [~EdShangGG], could you please take a look? > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.8 > > Attachments: image-2018-10-03-10-23-24-676.png, > image-2018-10-03-10-24-12-459.png, master_1b3742f4d7_mxbeans_threads2.patch > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721482#comment-16721482
]
Dmitriy Pavlov commented on IGNITE-9149:
Are any docs required here?
[~PetrovMikhail] do you have any updates?
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8617) Node Discovery Using AWS Application ELB
[ https://issues.apache.org/jira/browse/IGNITE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721480#comment-16721480 ] Dmitriy Pavlov commented on IGNITE-8617: [~slukyanov] could you please take a look? > Node Discovery Using AWS Application ELB > > > Key: IGNITE-8617 > URL: https://issues.apache.org/jira/browse/IGNITE-8617 > Project: Ignite > Issue Type: New Feature > Components: aws >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Support for Node discovery using AWS Application ELB. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7054) S3 IP finder: support client side encryption
[
https://issues.apache.org/jira/browse/IGNITE-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721426#comment-16721426
]
Dmitriy Pavlov commented on IGNITE-7054:
[~vkulichenko] are you agree with the fix now?
> S3 IP finder: support client side encryption
>
>
> Key: IGNITE-7054
> URL: https://issues.apache.org/jira/browse/IGNITE-7054
> Project: Ignite
> Issue Type: Improvement
> Components: s3
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
>
> In case client side encryption [1] is used, it may be required to use
> {{AmazonS3EncryptionClient}} instead of regular {{AmazonS3Client}}. We need
> to add this option to the S3 IP finder, along with any applicable
> configuration parameters.
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721362#comment-16721362 ] Dmitriy Pavlov commented on IGNITE-4551: [~agoncharuk] done, thanks > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.5 > > > In new cache implementation after entry is written in offheap information > about key/value classloaders in lost (before classloader ids were stored in > swap/offheap see GridCacheMapEntry.swap in 'master'). > Need decide how it should work with new architecture (maybe single type per > cache can simplify implementation). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-614) Race in preloading/unswapping
[ https://issues.apache.org/jira/browse/IGNITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721352#comment-16721352 ] Dmitriy Pavlov commented on IGNITE-614: --- [~agoncharuk] done, thanks > Race in preloading/unswapping > - > > Key: IGNITE-614 > URL: https://issues.apache.org/jira/browse/IGNITE-614 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Priority: Major > Labels: Muted_test > Fix For: 2.0 > > > During unswap entry is removed from swap then unswap listener is notified, > and this logic in preload supply worker: > - register unswap listener > - iterater over heap > - iterate over swap > - remove unswap listener > - iterate over entries recorded by unswap listener > There is a race: entry is removed from unswap, listener is not notified yet, > at this moment supply worker removes unswap listener. > These tests fail from time to time because entry can be missed during > preloading: > GridCacheSwapPreloadSelfTest.testSwapPartitionedMultithreaded > GridCacheSwapPreloadSelfTest.testSwapReplicatedMultithreaded -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9842) IgniteErrorOnRebalanceTest fails: errors in indexing cause grid to stall
[
https://issues.apache.org/jira/browse/IGNITE-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9842:
---
Labels: MakeTeamcityGreenAgain (was: )
> IgniteErrorOnRebalanceTest fails: errors in indexing cause grid to stall
> -
>
> Key: IGNITE-9842
> URL: https://issues.apache.org/jira/browse/IGNITE-9842
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2052100&#testNameId3682030486973860249
> {code}
> org.apache.ignite.IgniteException: Timeout of waiting for topology map update
> [igniteInstanceName=cache.IgniteErrorOnRebalanceTest0, cache=default,
> cacheId=1544803905, topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
> p=0, readVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
> locNode=TcpDiscoveryNode [id=e35c1f95-2e5c-406a-9266-7f6e4360,
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500],
> discPort=47500, order=4, intOrder=3, lastExchangeTime=1539180230507,
> loc=true, ver=2.7.0#20181010-sha1:9d1a551c, isClient=false]]
> at
> org.apache.ignite.internal.processors.cache.IgniteErrorOnRebalanceTest.testErrorOnRebalance(IgniteErrorOnRebalanceTest.java:129)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-614) Race in preloading/unswapping
[ https://issues.apache.org/jira/browse/IGNITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721287#comment-16721287 ] Dmitriy Pavlov commented on IGNITE-614: --- [~agoncharuk] [~sboikov], should we delete test code org.apache.ignite.internal.processors.cache.GridCacheSwapPreloadSelfTest#checkSwapMultithreaded() ? > Race in preloading/unswapping > - > > Key: IGNITE-614 > URL: https://issues.apache.org/jira/browse/IGNITE-614 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Priority: Major > Labels: Muted_test > Fix For: 2.0 > > > During unswap entry is removed from swap then unswap listener is notified, > and this logic in preload supply worker: > - register unswap listener > - iterater over heap > - iterate over swap > - remove unswap listener > - iterate over entries recorded by unswap listener > There is a race: entry is removed from unswap, listener is not notified yet, > at this moment supply worker removes unswap listener. > These tests fail from time to time because entry can be missed during > preloading: > GridCacheSwapPreloadSelfTest.testSwapPartitionedMultithreaded > GridCacheSwapPreloadSelfTest.testSwapReplicatedMultithreaded -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4551) Reconsider cache key/value peer class loading
[ https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721264#comment-16721264 ] Dmitriy Pavlov commented on IGNITE-4551: [~agoncharuk] should we delete org.apache.ignite.internal.managers.deployment.GridDeploymentMessageCountSelfTest#testCacheValueDeploymentOnPut ? > Reconsider cache key/value peer class loading > - > > Key: IGNITE-4551 > URL: https://issues.apache.org/jira/browse/IGNITE-4551 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.5 > > > In new cache implementation after entry is written in offheap information > about key/value classloaders in lost (before classloader ids were stored in > swap/offheap see GridCacheMapEntry.swap in 'master'). > Need decide how it should work with new architecture (maybe single type per > cache can simplify implementation). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9470) MVCC TX: Mvcc transactions should throw proper exception when rolled back.
[
https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9470:
---
Labels: Muted_test (was: )
> MVCC TX: Mvcc transactions should throw proper exception when rolled back.
> --
>
> Key: IGNITE-9470
> URL: https://issues.apache.org/jira/browse/IGNITE-9470
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, mvcc, odbc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: Muted_test
> Fix For: 2.8
>
>
> When MVCC transaction is rolled back due to a write conflict it throws
> {{CacheException}} with "Mvcc version mismatch" message. This behavior
> violates Ignite transactions API. Instead it should throw
> {{TransactionRollbackException}} with a clear message like a "Transaction has
> been aborted due to a write conflict (Please try again.)"
> It is also need to propogate this changes to JDBC and ODBC components and fix
> mvcc tests.
>
> In some tests we have to repeat tx operation in case of version conflict.
> Most likely, we can rely to caused-exception with some meaningful type (e.g.
> MvccVersionMismatchException) to repeat operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9322) MVCC: implement deadlock detector
[ https://issues.apache.org/jira/browse/IGNITE-9322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9322: --- Labels: MakeTeamcityGreenAgain (was: ) > MVCC: implement deadlock detector > - > > Key: IGNITE-9322 > URL: https://issues.apache.org/jira/browse/IGNITE-9322 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Ivan Pavlukhin >Priority: Major > Labels: MakeTeamcityGreenAgain > > Deadlocks are not uncommon during SQL execution. > We need to implement distributed deadlock detection protocol for MVCC. > Essentially, nodes should exchange some map of tx wait lists, and try to find > a loop. If loop is found, then one of problematic transactions should be > rolled back. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10582) MVCC: Error on txLog initialization.
[
https://issues.apache.org/jira/browse/IGNITE-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10582:
Labels: Muted_test (was: )
> MVCC: Error on txLog initialization.
>
>
> Key: IGNITE-10582
> URL: https://issues.apache.org/jira/browse/IGNITE-10582
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: Muted_test
>
> A sporadic error occurs during {{txLog}} initialization. Reproducer:
> {{IgnitePdsCacheAssignmentNodeRestartsTest#testAssignmentAfterRestarts}}.
> This error may be the result of the test settings. We need to check it more
> carefully.
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to complete exchange process.
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCaches(IgniteKernal.java:3068)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsCacheAssignmentNodeRestartsTest.testAssignmentAfterRestarts(IgnitePdsCacheAssignmentNodeRestartsTest.java:148)
> 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:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to complete
> exchange process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3041)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3069)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3151)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2748)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:138)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2556)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1807)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:145)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:340)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3294)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.ja
[jira] [Commented] (IGNITE-10673) Prepare instructions for ASC and SHA512 verification
[ https://issues.apache.org/jira/browse/IGNITE-10673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720438#comment-16720438 ] Dmitriy Pavlov commented on IGNITE-10673: - Could you please place it to Apache Ignite wiki? > Prepare instructions for ASC and SHA512 verification > > > Key: IGNITE-10673 > URL: https://issues.apache.org/jira/browse/IGNITE-10673 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > > Prepare instructions for ASC and SHA512 verification -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5003) Parallel write&evict same key in CacheWriteBehindStore
[ https://issues.apache.org/jira/browse/IGNITE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5003: --- Description: Now GridCacheWriteBehindStore.updateCache wait for writeLock in StatefulValue and, moreover, waitForFlush() if value is in pending (flushing) state. We need to remove waiting. was:Now GridCacheWriteBehindStore.updateCache wait for writeLock in StatefulValue and, moreover, waitForFlush() if value is in pending (flushing) state. We need to remove waiting. > Parallel write&evict same key in CacheWriteBehindStore > -- > > Key: IGNITE-5003 > URL: https://issues.apache.org/jira/browse/IGNITE-5003 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Alexander Belyak >Assignee: Andrey Aleksandrov >Priority: Major > > Now GridCacheWriteBehindStore.updateCache wait for writeLock in StatefulValue > and, moreover, waitForFlush() if value is in pending (flushing) state. > We need to remove waiting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10677) [TC Bot] Include build failure on metric & exit code into critical failures
[ https://issues.apache.org/jira/browse/IGNITE-10677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10677: Ignite Flags: (was: Docs Required) > [TC Bot] Include build failure on metric & exit code into critical failures > --- > > Key: IGNITE-10677 > URL: https://issues.apache.org/jira/browse/IGNITE-10677 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > It is necessary to setup dev.list notifications for _License&Headers_ failure > and for Inspections: Core failures notification -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10677) [TC Bot] Include build failure on metric & exit code into critical failures
Dmitriy Pavlov created IGNITE-10677: --- Summary: [TC Bot] Include build failure on metric & exit code into critical failures Key: IGNITE-10677 URL: https://issues.apache.org/jira/browse/IGNITE-10677 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov It is necessary to setup dev.list notifications for _License&Headers_ failure and for Inspections: Core failures notification -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8983) .NET long-running suite fails in master
[
https://issues.apache.org/jira/browse/IGNITE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8983:
---
Labels: MakeTeamcityGreenAgain (was: )
> .NET long-running suite fails in master
> ---
>
> Key: IGNITE-8983
> URL: https://issues.apache.org/jira/browse/IGNITE-8983
> Project: Ignite
> Issue Type: Test
>Affects Versions: 2.6
>Reporter: Alexey Goncharuk
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> One of the following changes triggered the fails:
> {code}
> IGNITE-8681 Using ExpiryPolicy with persistence causes significant slowdown
> - Fixes #4285.
> IGNITE-7149 : Gradient boosting for decision tree
> IGNITE-8746 EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the
> coordinator IGNITE-8821 Reduced amount of logs for BPlusTreeSelfTest
> put/remove family tests - Fixes #4218.
> IGNITE-8203 Handle ClosedByInterruptionException in FilePageStore - Fixes
> #4211.
> IGNITE-8857 new IgnitePredicate filtering credential attribute
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6205) Stability testing on CI server
[ https://issues.apache.org/jira/browse/IGNITE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720305#comment-16720305 ] Dmitriy Pavlov commented on IGNITE-6205: [~vveider] For me, it seems it is not relevant. We still have an idea of adding multiple-trigger to TC Bot. But it is needed not so often. Contributors prepare their own PRs with for(int i;) > Stability testing on CI server > -- > > Key: IGNITE-6205 > URL: https://issues.apache.org/jira/browse/IGNITE-6205 > Project: Ignite > Issue Type: Task >Affects Versions: 2.1 >Reporter: Sergey Kozlov >Assignee: Peter Ivanov >Priority: Major > > CI server shows many sporadic failures and the communty spend significant > efforts to fix them. > We should to avoid such cases by adding the task on teamcity where new or > modified tests wil run 100 times. Once it will be done the "100 times run" > can become the part/requirement of review procedure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9532) Binary mode for Ignite Queue
[ https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720187#comment-16720187 ] Dmitriy Pavlov commented on IGNITE-9532: Retriggered: https://ci.ignite.apache.org/viewQueued.html?itemId=2539366 Comment should appear here later > Binary mode for Ignite Queue > > > Key: IGNITE-9532 > URL: https://issues.apache.org/jira/browse/IGNITE-9532 > Project: Ignite > Issue Type: New Feature > Components: binary, data structures >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Add binary mode (withKeepBinary) to Data Structures Queue. > This will allow retrieving values in binary format when needed or when class > is not available, and will allow implementing the structures in other > platforms (.NET, C++). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9211) Remove IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9211:
---
Summary: Remove IgniteExamplesJ8SelfTestSuite (was: Uncomment 19 test
classes in IgniteExamplesJ8SelfTestSuite)
> Remove IgniteExamplesJ8SelfTestSuite
>
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9211) Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
[
https://issues.apache.org/jira/browse/IGNITE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-9211:
---
Fix Version/s: 2.8
> Uncomment 19 test classes in IgniteExamplesJ8SelfTestSuite
> --
>
> Key: IGNITE-9211
> URL: https://issues.apache.org/jira/browse/IGNITE-9211
> Project: Ignite
> Issue Type: Sub-task
> Components: examples
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.8
>
>
> {code}
> //suite.addTest(new TestSuite(ContinuationExamplesSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesSelfTest.class));
> //suite.addTest(new TestSuite(DeploymentExamplesSelfTest.class));
> //suite.addTest(new TestSuite(LifecycleExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MemcacheRestExamplesSelfTest.class));
> //suite.addTest(new TestSuite(MonteCarloExamplesSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesSelfTest.class));
> //suite.addTest(new TestSuite(SpringBeanExamplesSelfTest.class));
> //suite.addTest(new TestSuite(IgfsExamplesSelfTest.class));
> //suite.addTest(new TestSuite(CheckpointExamplesSelfTest.class));
> //suite.addTest(new TestSuite(HibernateL2CacheExampleSelfTest.class));
> //suite.addTest(new TestSuite(ClusterGroupExampleSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuationExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(ContinuousMapperExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(DeploymentExamplesMultiNodeSelfTest.class));
> //suite.addTest(new TestSuite(TaskExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MemcacheRestExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(MonteCarloExamplesMultiNodeSelfTest.class));
> //suite.addTest(new
> TestSuite(HibernateL2CacheExampleMultiNodeSelfTest.class));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9532) Binary mode for Ignite Queue
[ https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720064#comment-16720064 ] Dmitriy Pavlov commented on IGNITE-9532: [~avinogradov] because we had just 2 tests which may be flaky, we can omit this stage to get an absolutely green visa. > Binary mode for Ignite Queue > > > Key: IGNITE-9532 > URL: https://issues.apache.org/jira/browse/IGNITE-9532 > Project: Ignite > Issue Type: New Feature > Components: binary, data structures >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Add binary mode (withKeepBinary) to Data Structures Queue. > This will allow retrieving values in binary format when needed or when class > is not available, and will allow implementing the structures in other > platforms (.NET, C++). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10577) ignite-kubernetes is missing jackson-annotations dependency
[
https://issues.apache.org/jira/browse/IGNITE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10577:
Fix Version/s: 2.8
> ignite-kubernetes is missing jackson-annotations dependency
> ---
>
> Key: IGNITE-10577
> URL: https://issues.apache.org/jira/browse/IGNITE-10577
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
> Fix For: 2.8
>
>
> When starting 2.7 with the ignite-kubernetes option I get the following
> exception on startup:
>
> {code}
> [13:44:34,605][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView
> at
> com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector.(JacksonAnnotationIntrospector.java:37)
> at
> com.fasterxml.jackson.databind.ObjectMapper.(ObjectMapper.java:291)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:151)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1848)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1049)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:910)
> {code}
>
> It's clearly missing a dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10639) Proof of concept for internal description for packages
[ https://issues.apache.org/jira/browse/IGNITE-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717697#comment-16717697 ] Dmitriy Pavlov commented on IGNITE-10639: - [~agoncharuk], could you please approve concept https://github.com/apache/ignite/pull/5642 so I will continue to add README.md files wherever applicable. > Proof of concept for internal description for packages > -- > > Key: IGNITE-10639 > URL: https://issues.apache.org/jira/browse/IGNITE-10639 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > Need to test opportunities for documenting packages structure using > package-info/readme.txt/readme.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10431) Make tests independent of page size
[
https://issues.apache.org/jira/browse/IGNITE-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10431:
Ignite Flags: (was: Docs Required)
> Make tests independent of page size
> ---
>
> Key: IGNITE-10431
> URL: https://issues.apache.org/jira/browse/IGNITE-10431
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergi Vladykin
>Priority: Major
>
> The following tests were added to Page Compression suite and they fail
> because page size there increased to 8k.
> {code:java}
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…g.apache.ignite.internal.processors.cache.persistence.db.wal
> (4)
> IgniteWALTailIsReachedDuringIterationOverArchiveTest.testStandAloneIterator
> IgniteWalFormatFileFailoverTest.testFailureHandlerTriggered
> IgniteWalFormatFileFailoverTest.testFailureHandlerTriggeredFsync
> IgniteWalIteratorExceptionDuringReadTest.test
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…e.ignite.internal.processors.cache.persistence.db.wal.reader
> (9)
> IgniteWalReaderTest.testCheckBoundsIterator
> IgniteWalReaderTest.testFillWalAndReadRecords
> IgniteWalReaderTest.testFillWalForExactSegmentsCount
> IgniteWalReaderTest.testFillWalWithDifferentTypes
> IgniteWalReaderTest.testPutAllTxIntoTwoNodes
> IgniteWalReaderTest.testRemoveOperationPresentedForDataEntry
> IgniteWalReaderTest.testRemoveOperationPresentedForDataEntryForAtomic
> IgniteWalReaderTest.testTxFillWalAndExtractDataRecords
> IgniteWalReaderTest.testTxRecordsReadWoBinaryMeta
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…ache.ignite.internal.processors.cache.persistence.wal.reader
> (2)
> StandaloneWalRecordsIteratorTest.testCorrectClosingFileDescriptors
> StandaloneWalRecordsIteratorTest.testStrictBounds
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-1587) [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows agents
[ https://issues.apache.org/jira/browse/IGNITE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-1587. Resolution: Invalid > [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows > agents > --- > > Key: IGNITE-1587 > URL: https://issues.apache.org/jira/browse/IGNITE-1587 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Critical > Labels: Muted_test > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1587) [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows agents
[ https://issues.apache.org/jira/browse/IGNITE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717372#comment-16717372 ] Dmitriy Pavlov commented on IGNITE-1587: Ticket description is empty. Could you please provide more description about failure context. You can also try to unmute tests and check if it is failing now. > [Test Failed] Timeouted IgniteCacheAtomicNodeRestartTest.* at TC Windows > agents > --- > > Key: IGNITE-1587 > URL: https://issues.apache.org/jira/browse/IGNITE-1587 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Critical > Labels: Muted_test > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10573) [ML] Consistent API for Ensemble training
[ https://issues.apache.org/jira/browse/IGNITE-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717294#comment-16717294 ] Dmitriy Pavlov commented on IGNITE-10573: - Please fill ticket description > [ML] Consistent API for Ensemble training > - > > Key: IGNITE-10573 > URL: https://issues.apache.org/jira/browse/IGNITE-10573 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-3157) WebSession: genuine session is not always propagated to Ignite sessin.
[ https://issues.apache.org/jira/browse/IGNITE-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-3157. Resolution: Invalid The ticket is missing a description. This is an obstacle for a community member to come and fix the issue. I suggest to add more info or resolve this as won't fix. > WebSession: genuine session is not always propagated to Ignite sessin. > -- > > Key: IGNITE-3157 > URL: https://issues.apache.org/jira/browse/IGNITE-3157 > Project: Ignite > Issue Type: Task >Reporter: Vladimir Ozerov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-139) Remove Grid prefix from all classes
[ https://issues.apache.org/jira/browse/IGNITE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717297#comment-16717297 ] Dmitriy Pavlov commented on IGNITE-139: --- The ticket is missing a description, it is not clear should this prefix be replaced, would this change be harmful, etc. This is an obstacle for a community member to come and fix the issue. I suggest to add more info or resolve this as won't fix. > Remove Grid prefix from all classes > --- > > Key: IGNITE-139 > URL: https://issues.apache.org/jira/browse/IGNITE-139 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: sprint-1 >Reporter: Semen Boikov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-1119) Geospatial Documentation Missing
[ https://issues.apache.org/jira/browse/IGNITE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717298#comment-16717298 ] Dmitriy Pavlov commented on IGNITE-1119: The ticket is missing a description. This is an obstacle for a community member to come and fix the issue. I suggest to add more info or resolve this as won't fix. > Geospatial Documentation Missing > - > > Key: IGNITE-1119 > URL: https://issues.apache.org/jira/browse/IGNITE-1119 > Project: Ignite > Issue Type: Bug >Reporter: Suminda Dharmasena >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-18) Revisit logic for warmup closure, add tests and properly document
[ https://issues.apache.org/jira/browse/IGNITE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717296#comment-16717296 ] Dmitriy Pavlov commented on IGNITE-18: -- The ticket is missing a description. This is an obstacle for a community member to come and fix the issue. I suggest to add more info or resolve this as won't fix. > Revisit logic for warmup closure, add tests and properly document > - > > Key: IGNITE-18 > URL: https://issues.apache.org/jira/browse/IGNITE-18 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10481) [ML] Examples of stacking usage
[ https://issues.apache.org/jira/browse/IGNITE-10481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717295#comment-16717295 ] Dmitriy Pavlov commented on IGNITE-10481: - Please fill ticket description > [ML] Examples of stacking usage > --- > > Key: IGNITE-10481 > URL: https://issues.apache.org/jira/browse/IGNITE-10481 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Yury Babak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10644) CorruptedTreeException might occur after force node kill during transaction
[ https://issues.apache.org/jira/browse/IGNITE-10644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717275#comment-16717275 ] Dmitriy Pavlov commented on IGNITE-10644: - [~voropava] could you please fill ticket description? How contributor could possibly understand the context of the problem? > CorruptedTreeException might occur after force node kill during transaction > --- > > Key: IGNITE-10644 > URL: https://issues.apache.org/jira/browse/IGNITE-10644 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10639) Proof of concept for internal description for packages
Dmitriy Pavlov created IGNITE-10639: --- Summary: Proof of concept for internal description for packages Key: IGNITE-10639 URL: https://issues.apache.org/jira/browse/IGNITE-10639 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Need to test opportunities for documenting packages structure using package-info/readme.txt/readme.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716403#comment-16716403
]
Dmitriy Pavlov edited comment on IGNITE-7153 at 12/11/18 7:31 AM:
--
[~mcfongtw] a kindly reminder, could you please set PA if it is ready for
review?
was (Author: dpavlov):
[~mcfongtw] kindly remainder, could you please set PA if it is ready for review?
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Michael Fong
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protoc
[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716403#comment-16716403
]
Dmitriy Pavlov commented on IGNITE-7153:
[~mcfongtw] kindly remainder, could you please set PA if it is ready for review?
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Michael Fong
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcp
[jira] [Updated] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests
[ https://issues.apache.org/jira/browse/IGNITE-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10620: Ignite Flags: (was: Docs Required) > [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests > -- > > Key: IGNITE-10620 > URL: https://issues.apache.org/jira/browse/IGNITE-10620 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > Implement actual tests for tracked branches processing and issue detectors. > Skeletons: > org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector > org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor > The actual challenge is refactoring of configuration to use not singletons, > but some injected interfaces with mock-able alternatives, refactor scheduler, > and any other refactorings needed to cover issue detection by test. -- 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=16714751#comment-16714751 ] Dmitriy Pavlov commented on IGNITE-8227: The original commit was reverted https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=87510597f5f21d8a2913a6c61334bf2fe546fc13 Dev list thread https://lists.apache.org/thread.html/e0db80991af64f59d644e92369d9e8ee898a1e7a03dcdcc9ee071aaa@%3Cdev.ignite.apache.org%3E > 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 > > 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] [Reopened] (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:all-tabpanel ] Dmitriy Pavlov reopened IGNITE-8227: > 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 > > 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] [Updated] (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:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8227: --- Fix Version/s: (was: 2.8) > 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 > > 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] [Created] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests
Dmitriy Pavlov created IGNITE-10620: --- Summary: [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests Key: IGNITE-10620 URL: https://issues.apache.org/jira/browse/IGNITE-10620 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Implement actual tests for tracked branches processing and issue detectors. Skeletons: org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor The actual challenge is refactoring of configuration to use not singletons, but some injected interfaces with mock-able alternatives, refactor scheduler, and any other refactorings needed to cover issue detection by test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[ https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9542: --- Description: https://issues.apache.org/jira/browse/IGNITE-9376 works incorrectly without separation of test history for the base and for a shown branch. It is suggested to refactor provided data for the current and for the base branch. It will allow showing blockers based on statistics from any base branch without relation with the previous quering of data. was: https://issues.apache.org/jira/browse/IGNITE-9376 works incorrectly without separation of test history for the base and for a shown branch. It is suggested to refactor provided data for the current and for the base branch. It will allow showing blockers based on statistics from the base branch. > [TC bot] provide separated base/current branch history for PR page > -- > > Key: IGNITE-9542 > URL: https://issues.apache.org/jira/browse/IGNITE-9542 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://issues.apache.org/jira/browse/IGNITE-9376 > works incorrectly without separation of test history for the base and for a > shown branch. > It is suggested to refactor provided data for the current and for the base > branch. > It will allow showing blockers based on statistics from any base branch > without relation with the previous quering of data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov resolved IGNITE-10562.
-
Resolution: Fixed
Fixed with extended ID validation of builds.
Validation is enforced by FatBuildCompacted._ver = 5 -> 6
Old persistence calls not used anymore for fat builds.
V181206
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10577) ignite-kubernetes is missing jackson-annotations dependency
[
https://issues.apache.org/jira/browse/IGNITE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10577:
Ignite Flags: (was: Docs Required)
> ignite-kubernetes is missing jackson-annotations dependency
> ---
>
> Key: IGNITE-10577
> URL: https://issues.apache.org/jira/browse/IGNITE-10577
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 2.7
>Reporter: Stephen Darlington
>Assignee: Stephen Darlington
>Priority: Major
>
> When starting 2.7 with the ignite-kubernetes option I get the following
> exception on startup:
>
> {code}
> [13:44:34,605][SEVERE][main][IgniteKernal] Got exception while starting (will
> rollback startup routine).
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonView
> at
> com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector.(JacksonAnnotationIntrospector.java:37)
> at
> com.fasterxml.jackson.databind.ObjectMapper.(ObjectMapper.java:291)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:151)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1900)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1848)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1049)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:910)
> {code}
>
> It's clearly missing a dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10599) Add test for Scheduler Example test to LGPL Examples suite
[ https://issues.apache.org/jira/browse/IGNITE-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712936#comment-16712936 ] Dmitriy Pavlov commented on IGNITE-10599: - [~ilyak], could you please fill ticket description? well described issue has higher chance to find its contributor > Add test for Scheduler Example test to LGPL Examples suite > -- > > Key: IGNITE-10599 > URL: https://issues.apache.org/jira/browse/IGNITE-10599 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Priority: Major > Labels: test > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[ https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10203. - Resolution: Fixed Merged to master, and V181207 contains an additional fix for links in JIRA comments. [~zzzadruga] thank you for contribution > [TC Bot] Support for alternative configurations for PR testing > -- > > Key: IGNITE-10203 > URL: https://issues.apache.org/jira/browse/IGNITE-10203 > Project: Ignite > Issue Type: Task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > > Support for alternative configurations for PR testing (for example, > IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10203) [TC Bot] Support for alternative configurations for PR testing
[ https://issues.apache.org/jira/browse/IGNITE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10203: Ignite Flags: (was: Docs Required) > [TC Bot] Support for alternative configurations for PR testing > -- > > Key: IGNITE-10203 > URL: https://issues.apache.org/jira/browse/IGNITE-10203 > Project: Ignite > Issue Type: Task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > > Support for alternative configurations for PR testing (for example, > IgniteTests24Java8_RunMl) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9455) Total allocated size memory metric is always zero for metastore data region.
[ https://issues.apache.org/jira/browse/IGNITE-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711348#comment-16711348 ] Dmitriy Pavlov commented on IGNITE-9455: [~alex_pl], [~xtern] do we need an additional review here? > Total allocated size memory metric is always zero for metastore data region. > > > Key: IGNITE-9455 > URL: https://issues.apache.org/jira/browse/IGNITE-9455 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Fix For: 2.8 > > Attachments: Reproducer.java > > > Persistence enabled and metrics for all regions enabled, but total allocated > size is always zero for metastore data region > Even if we change NO_OP allocated page tracker to a real page tracker in > CacheStoreHolder this metric counts incorrectly, because this region is > recreated, > Reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.
[
https://issues.apache.org/jira/browse/IGNITE-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711344#comment-16711344
]
Dmitriy Pavlov commented on IGNITE-7309:
Hi [~guseinov], is there any news here? I can see the issue is open since Jun
2018, but it is not in Patch Available.
> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
> Issue Type: Bug
> Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
> Labels: newbie, pull-request-available
>
> User job can fails with confusing exception when server node is stopping and
> going to leave the grid.
> We should suppress InterruptedException. If node is stopping then user should
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl
> [ses=GridTaskSessionImpl
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register
> class.
> at
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
> at
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
> at
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
> ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
> at
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
> at
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContext
[jira] [Comment Edited] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711301#comment-16711301
]
Dmitriy Pavlov edited comment on IGNITE-10562 at 12/6/18 11:42 AM:
---
Some stat of inconsistent data in builds:
local/queued/659 -> 627
server/queued/6157 ->
was (Author: dpavlov):
Some stat of inconsistent data in builds:
builds: local/queued/659 -> 627
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8357) Recreated atomic sequence produces "Sequence was removed from cache"
[ https://issues.apache.org/jira/browse/IGNITE-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711326#comment-16711326 ] Dmitriy Pavlov commented on IGNITE-8357: [~pvinokurov] any news here? The issue is in progress since April. Is it reasonable to move to Open/unassigned? > Recreated atomic sequence produces "Sequence was removed from cache" > > > Key: IGNITE-8357 > URL: https://issues.apache.org/jira/browse/IGNITE-8357 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Attachments: RecreatingAtomicSequence.java > > > If a cluster has two or more nodes, recreated atomic sequence produces error > on incrementAndGet operation. > The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711301#comment-16711301
]
Dmitriy Pavlov edited comment on IGNITE-10562 at 12/6/18 11:20 AM:
---
Some stat of inconsistent data in builds:
builds: local/queued/659 -> 627
was (Author: dpavlov):
Some stat of inconsistent data:
local/queued/659 - builds
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711301#comment-16711301
]
Dmitriy Pavlov commented on IGNITE-10562:
-
Some stat of inconsistent data:
local/queued/659 - builds
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10562:
Description:
New Fat builds storage takes initial data from old cache "apache.builds":
String->JavaObject.
This cache contains a number of incorrect build ID->build mapping.
Example:
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
It is required to
- stop using deprecated persistent TC
- remove incorrect Fat Build entries (migration procedure or background task).
was:
New Fat builds storage takes initial data from old cache "apache.builds":
String->JavaObject.
This cache contains a number of incorrect build ID->build mapping.
Example:
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
It is required to stop using deprectated persistent TC
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to
> - stop using deprecated persistent TC
> - remove incorrect Fat Build entries (migration procedure or background task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
[
https://issues.apache.org/jira/browse/IGNITE-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10562:
Description:
New Fat builds storage takes initial data from old cache "apache.builds":
String->JavaObject.
This cache contains a number of incorrect build ID->build mapping.
Example:
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
It is required to stop using deprectated persistent TC
was:
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
> [TC Bot] DB contains invalid values for build references ID maps to value
> with other ID
> ---
>
> Key: IGNITE-10562
> URL: https://issues.apache.org/jira/browse/IGNITE-10562
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>
> New Fat builds storage takes initial data from old cache "apache.builds":
> String->JavaObject.
> This cache contains a number of incorrect build ID->build mapping.
> Example:
> {noformat}
>
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="4532"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
> href="/app/rest/latest/builds/id:2253798">
> projectId="IgniteTests24Java8" projectName="Ignite Tests 2.4+ (Java
> 8/9/10/11)" href="/app/rest/latest/buildTypes/id:IgniteTests24Java8_Cloud"/>
> 20181106T114741+0300
> 20181106T130017+0300
> 20181106T130156+0300
>
> buildTypeId="IgniteTests24Java8_BuildApacheIgnite"
> branchName="pull/4478/head" status="SUCCESS" state="finished" number="8100"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
> href="/app/rest/latest/builds/id:2253788"/>
>
> href="/app/rest/latest/testOccurrences?locator=build:(id:2253798)" count="2"
> passed="1" muted="1"/>
>
>
>
> version="6eda0197db2721620d0671c5f8a7e1712465dace" username="zzzadruga"
> date="20181106T114312+0300"
> webUrl="http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
> href="/app/rest/latest/changes/id:837621"/>
>
>
>
> href="/app/rest/latest/users/id:281"/>
> branchName="pull/4478/head" status="FAILURE" state="finished" number="6369"
> composite="true"
> webUrl="http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
> href="/app/rest/latest/builds/id:2253900"/>
>
>
> {noformat}
> It is required to stop using deprectated persistent TC
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
Dmitriy Pavlov created IGNITE-10562:
---
Summary: [TC Bot] DB contains invalid values for build references
ID maps to value with other ID
Key: IGNITE-10562
URL: https://issues.apache.org/jira/browse/IGNITE-10562
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798&buildTypeId=IgniteTests24Java8_Cloud";
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788&buildTypeId=IgniteTests24Java8_BuildApacheIgnite";
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621&personal=false";
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900&buildTypeId=IgniteTests24Java8_RunAll";
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
--
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] [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-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] [Updated] (IGNITE-10422) Make {{ignite_inspection.xml}} configuration default on the project level
[
https://issues.apache.org/jira/browse/IGNITE-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10422:
Fix Version/s: 2.8
> Make {{ignite_inspection.xml}} configuration default on the project level
> -
>
> Key: IGNITE-10422
> URL: https://issues.apache.org/jira/browse/IGNITE-10422
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
>
> IntelliJ IDEA can perform static code analysis by applying _inspections_ to
> the project code. The inspection analysis process can be easily run from both
> the IDE and the command line. The command line usage of IntelliJ IDEA
> inspections already configured as daily [Inspections(Core)
> TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv]
> suite. This approach has proven its convenience and efficiency as part of
> the _TC.Bot_.
> As for the next step, I propose to improve personal productivity of writing
> code by making *{{ignite_inspection.xml}}* configuration default on the
> project level.
> According to [IntelliJ IDEA
> documentation|https://www.jetbrains.com/help/idea/code-inspection.html], the
> inspection profile is recommended to be placed to
> *{{/.idea/inspectionProfiles}}* with name *{{Project_Default.xml}}*.
> This project profile will be shared and accessible for the team members via
> VCS by default.
> Note.
> The build and test procedure of Apache Ignite project will remain IDE
> independent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9859) add debug logging on refreshPartitions cause
[ https://issues.apache.org/jira/browse/IGNITE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707482#comment-16707482 ] Dmitriy Pavlov commented on IGNITE-9859: [~mshonichev] friendly remainder. I doubt that unassigned issue can be in a filter of all committers. > add debug logging on refreshPartitions cause > > > Key: IGNITE-9859 > URL: https://issues.apache.org/jira/browse/IGNITE-9859 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Max Shonichev >Priority: Major > Fix For: 2.8 > > Attachments: > IGNITE_9859__add_debug_logging_on_resendPartitions_cause.patch > > > Need some additional log messages for debugging PME issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10436) [TC Bot] Add ticket and PR links on report TC Bot page
[ https://issues.apache.org/jira/browse/IGNITE-10436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-10436. - Resolution: Fixed [~PetrovMikhail] thank you for the contribution, I appreciate you've added clickable JIRA to main PRs table and you've started JIRA integration refactoring to be a separate guice module > [TC Bot] Add ticket and PR links on report TC Bot page > --- > > Key: IGNITE-10436 > URL: https://issues.apache.org/jira/browse/IGNITE-10436 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-5759) IgniteCache 6 suite timed out by GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
[
https://issues.apache.org/jira/browse/IGNITE-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707360#comment-16707360
]
Dmitriy Pavlov edited comment on IGNITE-5759 at 12/3/18 3:25 PM:
-
Merged to master
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=66d8ac64dc0cd6f83bbfc45560cd08f38d8a92ff
Umuted test
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-7061194995222816963&tab=testDetails
[~akalashnikov] thank you for research and for finding that this failure is not
actual anymore.
was (Author: dpavlov):
Merged to master
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=66d8ac64dc0cd6f83bbfc45560cd08f38d8a92ff
Umuted test
https://ci.ignite.apache.org/viewLog.html?buildId=2450128&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache6#testNameId-7061194995222816963
[~akalashnikov] thank you for research and for finding that this failure is not
actual anymore.
> IgniteCache 6 suite timed out by
> GridCachePartitionEvictionDuringReadThroughSelfTest.testPartitionRent
> --
>
> Key: IGNITE-5759
> URL: https://issues.apache.org/jira/browse/IGNITE-5759
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Anton Kalashnikov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.8
>
> Attachments: threadDumpFromLogs.log
>
>
> Test history:
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests20&testNameId=-7061194995222816963&tab=testDetails
> There is no 'Test has been timed out' message in logs.
> Last 'Starting test:' message was
> GridCachePartitionEvictionDuringReadThroughSelfTest#testPartitionRent
> Latest exception from working test was as follows;
> {noformat}
> [23:19:11]W: [org.apache.ignite:ignite-core] [2017-07-14
> 20:19:11,392][ERROR][tcp-comm-worker-#8980%distributed.GridCachePartitionEvictionDuringReadThroughSelfTest4%][TcpCommunicationSpi]
> TcpCommunicationSpi failed to establish connection to node, node will be
> dropped from cluster [rmtNode=TcpDiscoveryNode
> [id=a93fce57-6b2d-4947-8c23-8a677b93, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1500063443391, loc=false, ver=2.1.0#19700101-sha1:,
> isClient=false]]
> [23:19:11]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node
> still alive?). Make sure that each ComputeTask and cache Transaction has a
> timeout set in order to prevent parties from waiting forever in case of
> network issues [nodeId=a93fce57-6b2d-4947-8c23-8a677b93,
> addrs=[/127.0.0.1:45273]]
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3173)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2757)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2649)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$5900(TcpCommunicationSpi.java:245)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:4065)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3891)
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [23:19:11]W: [org.apache.ignite:ignite-core]Suppressed:
> class org.apache.ignite.IgniteCheckedException: Failed to connect to address
> [addr=/127.0.0.1:45273, err=Connection refused]
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3178)
> [23:19:11]W: [org.apache.ignite:ignite-core]... 6
> more
> [23:19:11]W: [org.apache.ignite:ignite-core]Caused by:
> java.net.ConnectException: Connection refused
> [23:19:11]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> [23:19:11]W: [
[jira] [Updated] (IGNITE-10498) [TC Bot] Handle conflict error returned by TeamCity for some build problems
[
https://issues.apache.org/jira/browse/IGNITE-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10498:
Description:
{noformat}
java.lang.IllegalStateException: Invalid Response Code : 409:
Responding with error, status code: 409 (Conflict).
Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build
problem with id '2630' does not have an associated build.
Cannot process this request at this time. Repeat later.
at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192)
at
org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92)
at
org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31)
at
org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373)
at
org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454)
at
org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.IgnitePersistentTeamcity.getProblemsAndRegisterCritical(IgnitePersistentTeamcity.java:591)
at
org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.reloadBuild(ProactiveFatBuildSync.java:326)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.loadBuild(ProactiveFatBuildSync.java:271)
at
org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.lambda$doLoadBuilds$4(ProactiveFatBuildSync.java:217)
at java.lang.Iterable.forEach(Iterable.java:75)
at
org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:212)
at
org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:81)
at
org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.actualizeRecentBuildRefs(TeamcityIgnitedImpl.java:517)
at
org.apache.ignite.ci.di.scheduler.NamedTask.runIfNeeded(NamedTask.java:122)
at
org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$checkNamedTasks$2(TcBotScheduler.java:85)
at
java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1597)
at
org.apache.ignite.ci.di.scheduler.TcBotScheduler.checkNamedTasks(TcBotScheduler.java:83)
at
org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111)
at
org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$sheduleNamed$1(TcBotScheduler.java:70)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at
java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:308)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
java.lang.IllegalStateException: Invalid Response Code : 409:
Responding with error, status code: 409 (Conflict).
Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build
problem with id '2630' does not have an associated build.
Cannot process this request at this time. Repeat later.
at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192)
at
org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92)
at
org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31)
at
org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373)
at
org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454)
at
org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.IgnitePersistentTeamcity.getProblemsAndRegisterCritical(IgnitePersistentTeamcity.java:591)
at
org.apa
[jira] [Created] (IGNITE-10498) [TC Bot] Handle conflict error returned by TeamCity for some build problems
Dmitriy Pavlov created IGNITE-10498: --- Summary: [TC Bot] Handle conflict error returned by TeamCity for some build problems Key: IGNITE-10498 URL: https://issues.apache.org/jira/browse/IGNITE-10498 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov java.lang.IllegalStateException: Invalid Response Code : 409: Responding with error, status code: 409 (Conflict). Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build problem with id '2630' does not have an associated build. Cannot process this request at this time. Repeat later. at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192) at org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92) at org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31) at org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373) at org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454) at org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.IgnitePersistentTeamcity.getProblemsAndRegisterCritical(IgnitePersistentTeamcity.java:591) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.reloadBuild(ProactiveFatBuildSync.java:326) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.loadBuild(ProactiveFatBuildSync.java:271) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.lambda$doLoadBuilds$4(ProactiveFatBuildSync.java:217) at java.lang.Iterable.forEach(Iterable.java:75) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:212) at org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:81) at org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.actualizeRecentBuildRefs(TeamcityIgnitedImpl.java:517) at org.apache.ignite.ci.di.scheduler.NamedTask.runIfNeeded(NamedTask.java:122) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$checkNamedTasks$2(TcBotScheduler.java:85) at java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1597) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.checkNamedTasks(TcBotScheduler.java:83) at org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$sheduleNamed$1(TcBotScheduler.java:70) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:308) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) java.lang.IllegalStateException: Invalid Response Code : 409: Responding with error, status code: 409 (Conflict). Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build problem with id '2630' does not have an associated build. Cannot process this request at this time. Repeat later. at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192) at org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92) at org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31) at org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373) at org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454) at org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313) at org.apache.ignite.ci.di.AutoProfilingInterceptor.i
[jira] [Updated] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics
[ https://issues.apache.org/jira/browse/IGNITE-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10030: Ignite Flags: (was: Docs Required) > [TC Bot] Background upload of changes, problems, and statistics > --- > > Key: IGNITE-10030 > URL: https://issues.apache.org/jira/browse/IGNITE-10030 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > After the implementation of [IGNITE-9848] load time is still long because of > statistics and changes requires significant time to be loaded > Refs: > BuildChainProcessor#loadTestsAndProblems > TeamcityIgnitedImpl#reloadBuild -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10326) [Tc Bot] Add trusted suites
[ https://issues.apache.org/jira/browse/IGNITE-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10326: Ignite Flags: (was: Docs Required) > [Tc Bot] Add trusted suites > --- > > Key: IGNITE-10326 > URL: https://issues.apache.org/jira/browse/IGNITE-10326 > Project: Ignite > Issue Type: Task >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > > In trusted suites every new failure will be notified as critical. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10071) [TC Bot] Background upload of a build and simultaneous bot restart may result in a queued build persisted but actually build is finished
[ https://issues.apache.org/jira/browse/IGNITE-10071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10071: Ignite Flags: (was: Docs Required) > [TC Bot] Background upload of a build and simultaneous bot restart may result > in a queued build persisted but actually build is finished > > > Key: IGNITE-10071 > URL: https://issues.apache.org/jira/browse/IGNITE-10071 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > > TC bot new persistence based on continuous uploading builds from the TC > server may become outdated during bot server restart. > E.g. Run all which became completed in TC Bot's base may include > queued/running builds, which may lead to missed test failures (As running > build may not have these failures). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9298) control.sh does not support SSL (org.apache.ignite.internal.commandline.CommandHandler)
[ https://issues.apache.org/jira/browse/IGNITE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704774#comment-16704774 ] Dmitriy Pavlov commented on IGNITE-9298: [~ilyak], could we somehow enlist authorship and mention PRs in the text of commit? Probably we can revert current and add a new one. > control.sh does not support SSL > (org.apache.ignite.internal.commandline.CommandHandler) > --- > > Key: IGNITE-9298 > URL: https://issues.apache.org/jira/browse/IGNITE-9298 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.6 >Reporter: Paul Anderson >Assignee: Paul Anderson >Priority: Major > Fix For: 2.8 > > Attachments: Arguments.patch, CommandHandler.patch > > > We required SSL on the connector port and to use control.sh to work with the > baseline configuration. > This morning I added support, see attached patches against 2.6.0 for > org/apache/ignite/internal/commandline/CommandHandler.java > org/apache/ignite/internal/commandline/Arguments.java > No tests, no docs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9505) IGFS Hadoop wrapper v1 doesn't implement getScheme()
[ https://issues.apache.org/jira/browse/IGNITE-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703426#comment-16703426 ] Dmitriy Pavlov commented on IGNITE-9505: [~robgibbon] could you please assign the issue to yourself? > IGFS Hadoop wrapper v1 doesn't implement getScheme() > > > Key: IGNITE-9505 > URL: https://issues.apache.org/jira/browse/IGNITE-9505 > Project: Ignite > Issue Type: Bug > Components: igfs >Affects Versions: 2.6 >Reporter: Rob Gibbon >Priority: Major > Attachments: IGNITE-9473.patch > > > Ignite FS Hadoop wrapper v1 needs to override getScheme(), otherwise many > applications fail with an exception. I will upload a patch shortly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9504) Classpath cannot be customised
[ https://issues.apache.org/jira/browse/IGNITE-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703424#comment-16703424 ] Dmitriy Pavlov commented on IGNITE-9504: [~robgibbon] could you please assign the issue to yourself? > Classpath cannot be customised > -- > > Key: IGNITE-9504 > URL: https://issues.apache.org/jira/browse/IGNITE-9504 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Rob Gibbon >Priority: Minor > Attachments: IGNITE-9504.patch > > > ignite.sh doesn't have any option for the user to add custom libraries to the > classpath. This is essential when using IGFS as a write through cache for > Hadoop Filesystem API compliant remote storage backends. > I will add a patch to this ticket shortly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
