[jira] [Commented] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802516#comment-16802516 ] Vasiliy Sisko commented on IGNITE-11283: # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that marked for 2.8 version. > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802516#comment-16802516 ] Vasiliy Sisko edited comment on IGNITE-11283 at 3/27/19 7:40 AM: - # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that is marked for 2.8 version. was (Author: vsisko): # Disabled fields for PersistentStoreConfiguration. # transactionConfiguration.setDeadlockTimeout - implemented in IGNITE-11029 that marked for 2.8 version. > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11347) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802518#comment-16802518 ] Alexey Goncharuk commented on IGNITE-11347: --- Ivan, changes look good to me, thanks! > DistributedMetaStoragePersistentTest.testUnstableTopology is flaky > -- > > Key: IGNITE-11347 > URL: https://issues.apache.org/jira/browse/IGNITE-11347 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > https://ci.ignite.apache.org/project.html?tab=testDetails&projectId=IgniteTests24Java8&testNameId=-976745117458855384&page=1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11347) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
[
https://issues.apache.org/jira/browse/IGNITE-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802528#comment-16802528
]
Ignite TC Bot commented on IGNITE-11347:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3418793]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3411549&buildTypeId=IgniteTests24Java8_RunAll]
> DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
> --
>
> Key: IGNITE-11347
> URL: https://issues.apache.org/jira/browse/IGNITE-11347
> Project: Ignite
> Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/project.html?tab=testDetails&projectId=IgniteTests24Java8&testNameId=-976745117458855384&page=1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11347) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802529#comment-16802529 ] Ivan Bessonov commented on IGNITE-11347: ZookeeperDiscoveryClientDisconnectTest.testReconnectServersRestart_3 hangs in master but bot can't show it due to strange TC behavior on that suite, probably a bug in TC. > DistributedMetaStoragePersistentTest.testUnstableTopology is flaky > -- > > Key: IGNITE-11347 > URL: https://issues.apache.org/jira/browse/IGNITE-11347 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > https://ci.ignite.apache.org/project.html?tab=testDetails&projectId=IgniteTests24Java8&testNameId=-976745117458855384&page=1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11449) [ML] Umbrella: API for Feature/Label extracting (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov updated IGNITE-11449: - Summary: [ML] Umbrella: API for Feature/Label extracting (part 1) (was: [ML] Umbrella: API for Feature/Label extracting) > [ML] Umbrella: API for Feature/Label extracting (part 1) > > > Key: IGNITE-11449 > URL: https://issues.apache.org/jira/browse/IGNITE-11449 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Critical > Labels: stability > Time Spent: 1h 20m > Remaining Estimate: 0h > > Replace current lambdas with fixed API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11347) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802533#comment-16802533 ] Dmitriy Govorukhin commented on IGNITE-11347: - [~ibessonov] Thanks, merged to master. > DistributedMetaStoragePersistentTest.testUnstableTopology is flaky > -- > > Key: IGNITE-11347 > URL: https://issues.apache.org/jira/browse/IGNITE-11347 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > https://ci.ignite.apache.org/project.html?tab=testDetails&projectId=IgniteTests24Java8&testNameId=-976745117458855384&page=1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802536#comment-16802536 ] Vasiliy Sisko commented on IGNITE-11182: ++invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802536#comment-16802536 ] Vasiliy Sisko edited comment on IGNITE-11182 at 3/27/19 8:17 AM: - invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. See affinity in Affinity collocation section of cache configuration. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. was (Author: vsisko): ++invalidate/isInvalidate field available in General section for PARTITIONED TRANSACTIONAL cache. rebalanceThreadPoolSize was removed early. Moved to IgniteConfiguration#rebalanceThreadPoolSize transactionManagerLookupClassName was removed early. > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-11636: Labels: wizard (was: ) > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Priority: Major > Labels: wizard > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11636) Web console: incorrect value is restored after Refresh
Pavel Konstantinov created IGNITE-11636: --- Summary: Web console: incorrect value is restored after Refresh Key: IGNITE-11636 URL: https://issues.apache.org/jira/browse/IGNITE-11636 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Start two clusters with the same caches. Load some data in the first. Leave caches in the second cluster empty. Open SQL, select the first cluster, execute any select Press F5 to refresh the page Expected - the first cluster must be selected Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11182) Web console: Actualize grid configurator
[ https://issues.apache.org/jira/browse/IGNITE-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11182: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configurator > > > Key: IGNITE-11182 > URL: https://issues.apache.org/jira/browse/IGNITE-11182 > Project: Ignite > Issue Type: Improvement >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > WebConsoleConfigurationSelfTest has found the next difference: > Result for class: org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory > Missed > userNameMapper > Result for class: org.apache.ignite.ssl.SslContextFactory > Missed > cipherSuites > protocols > Result for class: org.apache.ignite.configuration.CacheConfiguration > Missed > cacheWriterFactory > expiryPolicyFactory > storeConcurrentLoadAllThreshold > sqlIndexMaxInlineSize > sqlOnheapCacheEnabled > interceptor > invalidate > diskPageCompression > storeByValue > sqlOnheapCacheMaxSize > eagerTtl > evictionPolicyFactory > encryptionEnabled > eventsDisabled > cacheLoaderFactory > keyConfiguration > cacheStoreSessionListenerFactories > diskPageCompressionLevel > maxQueryIteratorsCount > affinity > Deprecated > rebalanceThreadPoolSize > transactionManagerLookupClassName > Removed > isInvalidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-11636: --- Assignee: Andrey Novikov > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11283) Web console: Actualize grid configuration. Check deprecated fields
[ https://issues.apache.org/jira/browse/IGNITE-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-11283: -- Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web console: Actualize grid configuration. Check deprecated fields > -- > > Key: IGNITE-11283 > URL: https://issues.apache.org/jira/browse/IGNITE-11283 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: screenshot-1.png > > > Result for class: > org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction > Deprecated > backupFilter > Result for class: org.apache.ignite.configuration.PersistentStoreConfiguration > Deprecated > walBufferSize > writeThrottlingEnabled > checkpointWriteOrder > fileIOFactory > walMode > walAutoArchiveAfterInactivity > Result for class: org.apache.ignite.configuration.TransactionConfiguration > Missed > deadlockTimeout > useJtaSynchronization > txTimeoutOnPartitionMapExchange > Deprecated > txSerializableEnabled > txManagerLookupClassName > Result for class: org.apache.ignite.configuration.ConnectorConfiguration > Deprecated > sslContextFactory -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802572#comment-16802572
]
Ignite TC Bot commented on IGNITE-11606:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3411901&buildTypeId=IgniteTests24Java8_RunAll]
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11176) SQL: Support cancellation for native SQL commands and DDL
[ https://issues.apache.org/jira/browse/IGNITE-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11176: - Summary: SQL: Support cancellation for native SQL commands and DDL (was: support cancellation for native SQL commands and DDL) > SQL: Support cancellation for native SQL commands and DDL > - > > Key: IGNITE-11176 > URL: https://issues.apache.org/jira/browse/IGNITE-11176 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > Currently all native SQL commands and DDL partially don't support > cancellation. > There are at least commands, COPY, CREATE/DROP INDEX, ALTER TABLE > We need to add the ability -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11176) SQL: Support cancellation for native SQL commands and DDL
[ https://issues.apache.org/jira/browse/IGNITE-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11176: - Fix Version/s: (was: 2.8) > SQL: Support cancellation for native SQL commands and DDL > - > > Key: IGNITE-11176 > URL: https://issues.apache.org/jira/browse/IGNITE-11176 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > > Currently all native SQL commands and DDL partially don't support > cancellation. > There are at least commands, COPY, CREATE/DROP INDEX, ALTER TABLE > We need to add the ability -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11176) SQL: Support cancellation for native SQL commands and DDL
[ https://issues.apache.org/jira/browse/IGNITE-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11176: - Labels: iep-29 (was: ) > SQL: Support cancellation for native SQL commands and DDL > - > > Key: IGNITE-11176 > URL: https://issues.apache.org/jira/browse/IGNITE-11176 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > Currently all native SQL commands and DDL partially don't support > cancellation. > There are at least commands, COPY, CREATE/DROP INDEX, ALTER TABLE > We need to add the ability -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11176) SQL: Support cancellation for native SQL commands and DDL
[ https://issues.apache.org/jira/browse/IGNITE-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-11176: Assignee: (was: Yury Gerzhedovich) > SQL: Support cancellation for native SQL commands and DDL > - > > Key: IGNITE-11176 > URL: https://issues.apache.org/jira/browse/IGNITE-11176 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Fix For: 2.8 > > > Currently all native SQL commands and DDL partially don't support > cancellation. > There are at least commands, COPY, CREATE/DROP INDEX, ALTER TABLE > We need to add the ability -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11637) Remove class loader initilization in GridSpiAbstractTest
Ivan Fedotov created IGNITE-11637: - Summary: Remove class loader initilization in GridSpiAbstractTest Key: IGNITE-11637 URL: https://issues.apache.org/jira/browse/IGNITE-11637 Project: Ignite Issue Type: Improvement Reporter: Ivan Fedotov Assignee: Ivan Fedotov Investigate necessity of secondary class loader initilization in GridSpiAbstractTest. Initilization is secondary because the first is in GridAbstractTest. Now it seems that setting class loader in GridSpiAbstractTest should be removed. [1] [https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/spi/GridSpiAbstractTest.java#L151] [2] [https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/testframework/junits/GridAbstractTest.java#L558] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802590#comment-16802590
]
Eduard Shangareev commented on IGNITE-11606:
The situation happens if there was replace during logical recovery in the cache
which index.bin should be rebuilt or replace during index.bin rebuild.
It happens because there was not an explicit assumption that cache and pk index
are always synced.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802594#comment-16802594
]
Pavel Kuznetsov commented on IGNITE-11588:
--
Updated missed types in the example.
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11143) SQL: Warning about long query execution should be printed by timeout (now is printed after query finished)
[
https://issues.apache.org/jira/browse/IGNITE-11143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-11143:
-
Assignee: Taras Ledkov
> SQL: Warning about long query execution should be printed by timeout (now is
> printed after query finished)
> --
>
> Key: IGNITE-11143
> URL: https://issues.apache.org/jira/browse/IGNITE-11143
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
>
> Now the warning about the query execution time is too long is printed when
> the query is already finished. See
> {{IgniteH2Indexing#executeSqlQueryWithTimer}}.
> It looks strange: user has no information about really long query until it
> ends. In the worst case the info about infinite query is printed never.
> The warning should be printed by timeout.
> Additional info about query: lazy mode, distributed joins etc, should be
> printed with the warning.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11598) Add possibility to have different rebalance thread pool size for nodes in the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepachev Maksim reassigned IGNITE-11598: - Assignee: Stepachev Maksim > Add possibility to have different rebalance thread pool size for nodes in the > cluster > - > > Key: IGNITE-11598 > URL: https://issues.apache.org/jira/browse/IGNITE-11598 > Project: Ignite > Issue Type: Improvement >Reporter: Evgenii Zhuravlev >Assignee: Stepachev Maksim >Priority: Major > > It can be used for changing this property without downtime when rebalance is > slow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802600#comment-16802600
]
Igor Sapego commented on IGNITE-11588:
--
[~pkouznet] Reviewed suggested changes, looks good to me, merged them to
original branch.
Re-run TC:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&branch_IgniteTests24Java8=pull%2F6320%2Fhead
When it's complete, if there are no issues, I'll merge the changes to the
master.
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Igor Sapego
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-11638: Attachment: image.png > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Priority: Minor > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
Andrey Novikov created IGNITE-11638: --- Summary: Web console: 'Export All' in query result table doesn't work Key: IGNITE-11638 URL: https://issues.apache.org/jira/browse/IGNITE-11638 Project: Ignite Issue Type: Test Components: wizards Affects Versions: 2.8 Reporter: Andrey Novikov Attachments: image.png Execute any EXPLAIN Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-11638: --- Assignee: Andrey Novikov > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11639) GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity
Vyacheslav Koptilin created IGNITE-11639: Summary: GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity Key: IGNITE-11639 URL: https://issues.apache.org/jira/browse/IGNITE-11639 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: Vyacheslav Koptilin It seems GridCachePartitionedOptimisticTxNodeRestartTest is not cured by IGNITE-1090. The test still fails on TC. PFA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802613#comment-16802613 ] Andrey Novikov commented on IGNITE-11638: - Fixed broken code. [~vsisko], please review. > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11639) GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-11639: - Attachment: GridCachePartitionedOptimisticTxNodeRestartTestFailure.txt.zip > GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity > - > > Key: IGNITE-11639 > URL: https://issues.apache.org/jira/browse/IGNITE-11639 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Vyacheslav Koptilin >Priority: Major > Attachments: > GridCachePartitionedOptimisticTxNodeRestartTestFailure.txt.zip > > > It seems GridCachePartitionedOptimisticTxNodeRestartTest is not cured by > IGNITE-1090. The test still fails on TC. PFA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11634) SQL delete query failed to deserialize entryModifier
[
https://issues.apache.org/jira/browse/IGNITE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802623#comment-16802623
]
Ignite TC Bot commented on IGNITE-11634:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}_Javadoc_{color} [[tests 0 BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=3429920]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3429269&buildTypeId=IgniteTests24Java8_RunAll]
> SQL delete query failed to deserialize entryModifier
>
>
> Key: IGNITE-11634
> URL: https://issues.apache.org/jira/browse/IGNITE-11634
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Here is a stack trace
> {code:java}
> Exception in thread "main" javax.cache.CacheException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
> at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
> ... 5 more
> Caused by: java.sql.SQLException: Failed to deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.
[jira] [Commented] (IGNITE-11634) SQL delete query failed to deserialize entryModifier
[
https://issues.apache.org/jira/browse/IGNITE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802626#comment-16802626
]
Roman Guseinov commented on IGNITE-11634:
-
Javadoc issue is related to another commit :
{code:java}
[10:54:26] : [Step 2/2] 1 warning
[10:54:26]W: [Step 2/2] [WARNING] Javadoc Warnings
[10:54:26]W: [Step 2/2] [WARNING]
/data/teamcity/work/c182b70f2dfa6507/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/IgniteCacheDatabaseSharedManager.java:382:
warning - @Deprecated is an unknown tag -- same as a known tag except for case.
{code}
> SQL delete query failed to deserialize entryModifier
>
>
> Key: IGNITE-11634
> URL: https://issues.apache.org/jira/browse/IGNITE-11634
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Here is a stack trace
> {code:java}
> Exception in thread "main" javax.cache.CacheException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:635)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:574)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:356)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.deleteRow(JavaSqlClient.java:42)
> at org.gridgain.reproducers.sql.JavaSqlClient.run(JavaSqlClient.java:33)
> at
> org.gridgain.reproducers.sql.JavaSqlClient.main(JavaSqlClient.java:28)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:686)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:587)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1753)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1718)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2007)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2002)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2550)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:623)
> ... 5 more
> Caused by: java.sql.SQLException: Failed to deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.processPage(DmlBatchSender.java:225)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.sendBatch(DmlBatchSender.java:184)
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlBatchSender.flush(DmlBatchSender.java:135)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doDelete(DmlStatementsProcessor.java:668)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> deserialize object
> [typeName=org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor$ModifyingEntryProcessor]
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10045)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMessage.unmarshalCollection(GridCacheMessage.java:650)
> at
> org.apache.
[jira] [Commented] (IGNITE-8223) GridNearTxLocal.clearPrepareFuture does effectively nothing
[
https://issues.apache.org/jira/browse/IGNITE-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802640#comment-16802640
]
Ignite TC Bot commented on IGNITE-8223:
---
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3413675&buildTypeId=IgniteTests24Java8_RunAll]
> GridNearTxLocal.clearPrepareFuture does effectively nothing
> ---
>
> Key: IGNITE-8223
> URL: https://issues.apache.org/jira/browse/IGNITE-8223
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Rodion
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8
>
>
> It's unclear whether {{GridNearTxLocal.clearPrepareFuture}} is called at all,
> but the method does nothing, since its argument type is never used as target
> field value. Proposed change is to make the method no-op explicitly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802651#comment-16802651 ] Vasiliy Sisko commented on IGNITE-11638: Looks good. Checked. > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802651#comment-16802651 ] Vasiliy Sisko edited comment on IGNITE-11638 at 3/27/19 10:46 AM: -- Looks good. Tested. was (Author: vsisko): Looks good. Checked. > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802657#comment-16802657 ] Vasiliy Sisko commented on IGNITE-11636: Changes looks good. > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11493) Test CheckpointFreeListTest#testFreeListRestoredCorrectly always fails in DiskCompression suite
[
https://issues.apache.org/jira/browse/IGNITE-11493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802666#comment-16802666
]
Sergey Chugunov commented on IGNITE-11493:
--
[~akalashnikov],
Fix looks simple, as long as it doesn't introduce any new test failures I think
we could proceed with merging.
> Test CheckpointFreeListTest#testFreeListRestoredCorrectly always fails in
> DiskCompression suite
> ---
>
> Key: IGNITE-11493
> URL: https://issues.apache.org/jira/browse/IGNITE-11493
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Anton Kalashnikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test fails with the following NullPointerException in logs:
> {code}
> [2019-03-06
> 16:05:24,353][ERROR][exchange-worker-#94%client%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteCheckedException:
> null]]
> class org.apache.ignite.IgniteCheckedException: null
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7323)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:260)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:209)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2948)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2769)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheCompressionManager.start0(CacheCompressionManager.java:55)
> at
> org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.initCacheContext(GridCacheProcessor.java:2534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:2344)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:2270)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:2141)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$5(GridCacheProcessor.java:2094)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:2138)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:2093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:2039)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:951)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:810)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2920)
> ... 3 more
> {code}
> Root cause of it is that CacheManager when initializing CacheContext on
> client tries to start GridCompressionManager which doesn't make sense on
> client node.
> We should either exclude compression manager from cache context on client or
> not start it during initialization phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802674#comment-16802674 ] Alexey Kuznetsov commented on IGNITE-11636: --- Looks good to me. > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11639) GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-11639: - Labels: MakeTeamcityGreenAgain (was: ) > GridCachePartitionedOptimisticTxNodeRestartTest hangs on TeamCity > - > > Key: IGNITE-11639 > URL: https://issues.apache.org/jira/browse/IGNITE-11639 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Vyacheslav Koptilin >Priority: Major > Labels: MakeTeamcityGreenAgain > Attachments: > GridCachePartitionedOptimisticTxNodeRestartTestFailure.txt.zip > > > It seems GridCachePartitionedOptimisticTxNodeRestartTest is not cured by > IGNITE-1090. The test still fails on TC. PFA. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11636: -- Fix Version/s: 2.8 > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802674#comment-16802674 ] Alexey Kuznetsov edited comment on IGNITE-11636 at 3/27/19 11:33 AM: - Looks good to me. Merged to master. was (Author: kuaw26): Looks good to me. > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11636) Web console: incorrect value is restored after Refresh
[ https://issues.apache.org/jira/browse/IGNITE-11636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11636: -- Ignite Flags: (was: Docs Required) > Web console: incorrect value is restored after Refresh > -- > > Key: IGNITE-11636 > URL: https://issues.apache.org/jira/browse/IGNITE-11636 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov >Priority: Major > Labels: wizard > Time Spent: 10m > Remaining Estimate: 0h > > Start two clusters with the same caches. > Load some data in the first. > Leave caches in the second cluster empty. > Open SQL, select the first cluster, execute any select > Press F5 to refresh the page > Expected - the first cluster must be selected > Actual - the second cluster is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11449) [ML] Umbrella: API for Feature/Label extracting (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802693#comment-16802693 ] Yury Babak commented on IGNITE-11449: - Reviewed by [~dmitrievanthony], [~zaleslaw] and [~chief] > [ML] Umbrella: API for Feature/Label extracting (part 1) > > > Key: IGNITE-11449 > URL: https://issues.apache.org/jira/browse/IGNITE-11449 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Critical > Labels: stability > Time Spent: 1h 20m > Remaining Estimate: 0h > > Replace current lambdas with fixed API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager
[
https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802697#comment-16802697
]
Alexey Goncharuk commented on IGNITE-11127:
---
Changes look good to me. [~slava.koptilin] can you take a second look?
> GridDhtInvalidPartitionException not handled by GridCacheTtlManager
> ---
>
> Key: IGNITE-11127
> URL: https://issues.apache.org/jira/browse/IGNITE-11127
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4, 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Roman Shtykh
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Leading to either message processing problems:
> {code}
> [2019-01-27 16:57:45,474][ERROR][sys-stripe-2-#3][GridCacheIoManager] Failed
> to process message [senderId=4839b5a2-a295-44cf-8a44-f0cb932b689e,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest]
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=381, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=381, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=818, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=818, minorTopVer=0]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:917)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:952)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:943)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1047)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:835)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1066)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> or unhandled unspecified exceptions in user code (possibly violating JCache):
> {code}
> [2019-01-27 10:23:35,451][ERROR][pub-#840058][ComputeJobProcess] class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=485, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=485, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=815, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=815, minorTopVer=0]]]
> at
> org.apache.ignite
[jira] [Created] (IGNITE-11640) IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop
Vyacheslav Koptilin created IGNITE-11640: Summary: IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop Key: IGNITE-11640 URL: https://issues.apache.org/jira/browse/IGNITE-11640 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Vyacheslav Koptilin Assignee: Vyacheslav Koptilin Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10949) org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE
[ https://issues.apache.org/jira/browse/IGNITE-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10949: -- Ignite Flags: (was: Docs Required) > org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE > -- > > Key: IGNITE-10949 > URL: https://issues.apache.org/jira/browse/IGNITE-10949 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.7 >Reporter: Alexand Polyakov >Assignee: Andrey Kalinin >Priority: Major > Labels: newbie > Time Spent: 10m > Remaining Estimate: 0h > > method entrySet return null then generates NullPointerException in method > hashCode, toString and all classes that use an instance of this object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11449) [ML] Umbrella: API for Feature/Label extracting (part 1)
[ https://issues.apache.org/jira/browse/IGNITE-11449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak resolved IGNITE-11449. - Resolution: Done Fix Version/s: 2.8 merged > [ML] Umbrella: API for Feature/Label extracting (part 1) > > > Key: IGNITE-11449 > URL: https://issues.apache.org/jira/browse/IGNITE-11449 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Critical > Labels: stability > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Replace current lambdas with fixed API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10997) Add new property to DataRegionMetrics: empty pages count in reuseList.
[ https://issues.apache.org/jira/browse/IGNITE-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802739#comment-16802739 ] Ivan Rakov commented on IGNITE-10997: - Javadoc suite is broken by the patch. Fixed under the following commit: IGNITE-10997 Fixed @deprecated tag in javadoc Ivan Rakov 27.03.2019 15:46 70f952c5461b768ab9cc7c793e897d2c55cafa76 > Add new property to DataRegionMetrics: empty pages count in reuseList. > -- > > Key: IGNITE-10997 > URL: https://issues.apache.org/jira/browse/IGNITE-10997 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinskiy >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > In order to estimate available space in data region, new property should be > added in dataregions metrics -- empty pages count from > org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList#emptyDataPages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager
[
https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802765#comment-16802765
]
Andrey Gura commented on IGNITE-11127:
--
[~roman_s] Looks good to me too.
> GridDhtInvalidPartitionException not handled by GridCacheTtlManager
> ---
>
> Key: IGNITE-11127
> URL: https://issues.apache.org/jira/browse/IGNITE-11127
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4, 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Roman Shtykh
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Leading to either message processing problems:
> {code}
> [2019-01-27 16:57:45,474][ERROR][sys-stripe-2-#3][GridCacheIoManager] Failed
> to process message [senderId=4839b5a2-a295-44cf-8a44-f0cb932b689e,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest]
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=381, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=381, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=818, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=818, minorTopVer=0]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:917)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:952)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:943)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1047)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:835)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1066)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> or unhandled unspecified exceptions in user code (possibly violating JCache):
> {code}
> [2019-01-27 10:23:35,451][ERROR][pub-#840058][ComputeJobProcess] class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=485, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=485, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=815, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=815, minorTopVer=0]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridD
[jira] [Commented] (IGNITE-9812) Explicit tests with expired SSL certificates
[ https://issues.apache.org/jira/browse/IGNITE-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802772#comment-16802772 ] Andrey Gura commented on IGNITE-9812: - [~ilyak] LGTM! Please proceed with merge. > Explicit tests with expired SSL certificates > > > Key: IGNITE-9812 > URL: https://issues.apache.org/jira/browse/IGNITE-9812 > Project: Ignite > Issue Type: Test > Components: clients, security >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Labels: test > Time Spent: 10m > Remaining Estimate: 0h > > It came to our attention that we have no test which checks that expired SSL > certificates do not work indeed. > Should get such old certificate from git, check if it will fail to join > cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11641) Server node copies a lot of WAL files in WAL archive after restart
[
https://issues.apache.org/jira/browse/IGNITE-11641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin updated IGNITE-11641:
Fix Version/s: 2.8
> Server node copies a lot of WAL files in WAL archive after restart
> --
>
> Key: IGNITE-11641
> URL: https://issues.apache.org/jira/browse/IGNITE-11641
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Pre-condition: PDS is enabled, wal_path and wal_archive_path are set in
> config file.
> 1. Cluster is up and running. Some data uploaded into caches.
> 2. Start load to generate a lot of files in wal archive (more than files in
> wal directory).
> 3. Stop some node and delete all files from wal archive.
> 4. Start node.
> In this case node copies WAL files from WAL dir into wal archive dir again
> and again until the amount of files will be the same it was in wal archive
> before stop.
> Here is information from server node log
> {code}
> 10:10:17,054][INFO][main][GridCacheDatabaseSharedManager] Restoring partition
> state for local groups.
> [10:10:18,522][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal]
> [10:10:18,523][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=1, segIdx=1,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
> [10:10:20,631][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
> [10:10:20,632][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=2, segIdx=2,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
> [10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
> [10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=3, segIdx=3,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
> [10:10:23,995][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
> [10:10:23,996][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=4, segIdx=4,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
> [10:10:24,644][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
> [10:10:24,645][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=5, segIdx=5,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
> [10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
> [10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=6, segIdx=6,
> origFile=/storage/ssd/avolkov/wal
[jira] [Created] (IGNITE-11641) Server node copies a lot of WAL files in WAL archive after restart
Dmitriy Govorukhin created IGNITE-11641:
---
Summary: Server node copies a lot of WAL files in WAL archive
after restart
Key: IGNITE-11641
URL: https://issues.apache.org/jira/browse/IGNITE-11641
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Govorukhin
Pre-condition: PDS is enabled, wal_path and wal_archive_path are set in config
file.
1. Cluster is up and running. Some data uploaded into caches.
2. Start load to generate a lot of files in wal archive (more than files in wal
directory).
3. Stop some node and delete all files from wal archive.
4. Start node.
In this case node copies WAL files from WAL dir into wal archive dir again and
again until the amount of files will be the same it was in wal archive before
stop.
Here is information from server node log
{code}
10:10:17,054][INFO][main][GridCacheDatabaseSharedManager] Restoring partition
state for local groups.
[10:10:18,522][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal]
[10:10:18,523][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=1, segIdx=1,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
[10:10:20,631][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
[10:10:20,632][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=2, segIdx=2,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
[10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
[10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=3, segIdx=3,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
[10:10:23,995][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
[10:10:23,996][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=4, segIdx=4,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
[10:10:24,644][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
[10:10:24,645][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=5, segIdx=5,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
[10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
[10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Starting to copy WAL segment [absIdx=6, segIdx=6,
origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0006.wal,
dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0006.wal]
[10:10:26,043][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
Copied file
[src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0006.wal,
dst=/storage/ssd/avolkov/wal_archive/node
[jira] [Assigned] (IGNITE-11641) Server node copies a lot of WAL files in WAL archive after restart
[
https://issues.apache.org/jira/browse/IGNITE-11641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin reassigned IGNITE-11641:
---
Assignee: Dmitriy Govorukhin
> Server node copies a lot of WAL files in WAL archive after restart
> --
>
> Key: IGNITE-11641
> URL: https://issues.apache.org/jira/browse/IGNITE-11641
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> Pre-condition: PDS is enabled, wal_path and wal_archive_path are set in
> config file.
> 1. Cluster is up and running. Some data uploaded into caches.
> 2. Start load to generate a lot of files in wal archive (more than files in
> wal directory).
> 3. Stop some node and delete all files from wal archive.
> 4. Start node.
> In this case node copies WAL files from WAL dir into wal archive dir again
> and again until the amount of files will be the same it was in wal archive
> before stop.
> Here is information from server node log
> {code}
> 10:10:17,054][INFO][main][GridCacheDatabaseSharedManager] Restoring partition
> state for local groups.
> [10:10:18,522][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/.wal]
> [10:10:18,523][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=1, segIdx=1,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
> [10:10:20,631][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0001.wal]
> [10:10:20,632][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=2, segIdx=2,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
> [10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0002.wal]
> [10:10:23,276][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=3, segIdx=3,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
> [10:10:23,995][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0003.wal]
> [10:10:23,996][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=4, segIdx=4,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
> [10:10:24,644][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0004.wal]
> [10:10:24,645][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segment [absIdx=5, segIdx=5,
> origFile=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
>
> dstFile=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
> [10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Copied file
> [src=/storage/ssd/avolkov/wal/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal,
>
> dst=/storage/ssd/avolkov/wal_archive/node00-83c9db32-fee5-4f3e-8a1c-559221817759/0005.wal]
> [10:10:25,301][INFO][wal-file-archiver%null-#64][FileWriteAheadLogManager]
> Starting to copy WAL segmen
[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager
[
https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802810#comment-16802810
]
Roman Shtykh commented on IGNITE-11127:
---
[~agoncharuk] [~agura] Thank you, guys!
I will merge tomorrow if there are no objections (or additions from
Vyacheslav's side).
> GridDhtInvalidPartitionException not handled by GridCacheTtlManager
> ---
>
> Key: IGNITE-11127
> URL: https://issues.apache.org/jira/browse/IGNITE-11127
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4, 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Roman Shtykh
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Leading to either message processing problems:
> {code}
> [2019-01-27 16:57:45,474][ERROR][sys-stripe-2-#3][GridCacheIoManager] Failed
> to process message [senderId=4839b5a2-a295-44cf-8a44-f0cb932b689e,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest]
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=381, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=381, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=818, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=818, minorTopVer=0]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:917)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:952)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:943)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1047)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:835)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1066)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> or unhandled unspecified exceptions in user code (possibly violating JCache):
> {code}
> [2019-01-27 10:23:35,451][ERROR][pub-#840058][ComputeJobProcess] class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=485, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=485, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=815, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=81
[jira] [Updated] (IGNITE-11452) KILL QUERY for not cancellable queries should return error
[ https://issues.apache.org/jira/browse/IGNITE-11452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11452: - Ignite Flags: (was: Docs Required) > KILL QUERY for not cancellable queries should return error > -- > > Key: IGNITE-11452 > URL: https://issues.apache.org/jira/browse/IGNITE-11452 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > User should be aware that a query can't be cancelled and receive Exception > with description about it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11606:
-
Component/s: sql
persistence
cache
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6587) Ignite watchdog service
[
https://issues.apache.org/jira/browse/IGNITE-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802823#comment-16802823
]
Ignite TC Bot commented on IGNITE-6587:
---
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395254]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395256]]
* ZookeeperDiscoverySpiTest.testDisconnectOnServersLeft_3 (last started)
{color:#d04437}Client Nodes{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395258]]
* IgniteClientRejoinTest.testClientsReconnect (last started)
{color:#d04437}Cache 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395266]]
* IgniteCacheGroupsTest.testRestartsAndCacheCreateDestroy (last started)
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 Exit Code , Failure
on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3395274]]
{color:#d04437}Hibernate 5.3{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395282]]
{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395280]]
{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395286]]
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395290]]
{color:#d04437}Spring (Data){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3395294]]
{color:#d04437}Cache 1{color} [[tests
11|https://ci.ignite.apache.org/viewLog.html?buildId=3395262]]
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testTwoClientsAllowOverwrite
- 0,0% fails in last 405 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testOneClientAllowOverwrite
- 0,0% fails in last 405 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testTwoClients - 0,0% fails
in last 405 master runs.
* IgniteBinaryCacheTestSuite:
DataStreamerClientReconnectAfterClusterRestartTest.testOneClient - 0,0% fails
in last 405 master runs.
{color:#d04437}Queries 1{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=3395260]]
* IgniteBinaryCacheQueryTestSuite:
SchemaExchangeSelfTest.testServerRestartWithNewTypes - 0,0% fails in last 409
master runs.
{color:#d04437}PDS (Indexing){color} [[tests 4 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3395264]]
* IgnitePdsWithIndexingCoreTestSuite:
IgniteLogicalRecoveryTest.testRecoveryOnJoinToDifferentBlt - 0,0% fails in last
398 master runs.
* IgnitePdsWithIndexingCoreTestSuite:
IgniteLogicalRecoveryTest.testRecoveryOnDynamicallyStartedCaches - 0,0% fails
in last 398 master runs.
* IgnitePdsWithIndexingCoreTestSuite:
IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite - 0,0% fails in last
398 master runs.
* IgniteLogicalRecoveryTest.testRecoveryOnDynamicallyStartedCaches (last
started)
{color:#d04437}Queries 2{color} [[tests
14|https://ci.ignite.apache.org/viewLog.html?buildId=3395268]]
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalReplicatedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicPartitionedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexPartitionedTransactionalConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testClientReconnectWithNonDynamicCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentTransactionalPartitionedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
IgniteCacheQueryNodeRestartSelfTest2.testRestarts - 0,0% fails in last 0 master
runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testClientReconnectWithNonDynamicCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIndexReplicatedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testClientReconnectWithCacheRestart
- 0,0% fails in last 414 master runs.
* IgniteBinaryCacheQueryTestSuite2:
DynamicIn
[jira] [Comment Edited] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802830#comment-16802830
]
Vladimir Ozerov edited comment on IGNITE-11606 at 3/27/19 2:08 PM:
---
[~EdShangGG], I have a concern about changes in {{GridH2Table}}. We added
{{Atomic.get()}} on a very hot path (update). While I do not expect any
critical problems with it, but I'd prefer to use {{volatile +
AtomicFieldUpdater}} instead. Looks good otherwise.
was (Author: vozerov):
[~EdShangGG], I have a concern about changes in {{GridH2Table}}. We added
{{Atomic.get()}} on a very hot path (update). While I do not expect any
critical problems with it, but I'd prefer to use {{volatile +
AtomicFieldUpdater}} instead.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802830#comment-16802830
]
Vladimir Ozerov commented on IGNITE-11606:
--
[~EdShangGG], I have a concern about changes in {{GridH2Table}}. We added
{{Atomic.get()}} on a very hot path (update). While I do not expect any
critical problems with it, but I'd prefer to use {{volatile +
AtomicFieldUpdater}} instead.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11481) [ML] Prototype of DatasetRow for Vectorizer
[ https://issues.apache.org/jira/browse/IGNITE-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov resolved IGNITE-11481. -- Resolution: Won't Fix > [ML] Prototype of DatasetRow for Vectorizer > --- > > Key: IGNITE-11481 > URL: https://issues.apache.org/jira/browse/IGNITE-11481 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Major > Labels: stability > > Vectorizer shold produce DatasetRow object that can contains columns with > different types (double, string, etc.). It needs for preprocessors working > with non-double values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11642) [ML] Umbrella: API for Feature/Label extracting (part 2)
Alexey Platonov created IGNITE-11642: Summary: [ML] Umbrella: API for Feature/Label extracting (part 2) Key: IGNITE-11642 URL: https://issues.apache.org/jira/browse/IGNITE-11642 Project: Ignite Issue Type: Improvement Components: ml Reporter: Alexey Platonov Assignee: Alexey Platonov Fix For: 2.8 Replace current lambdas with fixed API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11642) [ML] Umbrella: API for Feature/Label extracting (part 2)
[ https://issues.apache.org/jira/browse/IGNITE-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov reassigned IGNITE-11642: Assignee: (was: Alexey Platonov) > [ML] Umbrella: API for Feature/Label extracting (part 2) > > > Key: IGNITE-11642 > URL: https://issues.apache.org/jira/browse/IGNITE-11642 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Platonov >Priority: Critical > Labels: stability > Fix For: 2.8 > > > Replace current lambdas with fixed API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802852#comment-16802852
]
Ivan Pavlukhin edited comment on IGNITE-11606 at 3/27/19 2:24 PM:
--
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is rebuildIsMeaning *less* and it is better to
indicate in what cases method returns {{true}} in javadoc.
was (Author: pavlukhin):
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is rebuildIsMeaning*less* and it is better to
indicate in what cases method returns {{true}} in javadoc.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802852#comment-16802852
]
Ivan Pavlukhin edited comment on IGNITE-11606 at 3/27/19 2:24 PM:
--
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is rebuildIsMeaning*less* and it is better to
indicate in what cases method returns {{true}} in javadoc.
was (Author: pavlukhin):
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is _rebuildIsMeaning*less*_ and it is better to
indicate in what cases method returns {{true}} in javadoc.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802852#comment-16802852
]
Ivan Pavlukhin commented on IGNITE-11606:
-
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is _rebuildIsMeaning*less*_ and it is better to
indicate in what cases method returns {{true}} in javadoc.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11552) ODBC: Error while trying to get params meta for request with ODBC escape symbols
[ https://issues.apache.org/jira/browse/IGNITE-11552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802855#comment-16802855 ] Vladimir Ozerov commented on IGNITE-11552: -- Reviewed. Merged to master. > ODBC: Error while trying to get params meta for request with ODBC escape > symbols > > > Key: IGNITE-11552 > URL: https://issues.apache.org/jira/browse/IGNITE-11552 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > There is an error if one tries to get parameters meta for SQL with [ODBC > escape > symbols|https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/odbc-escape-sequences]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802852#comment-16802852
]
Ivan Pavlukhin edited comment on IGNITE-11606 at 3/27/19 2:26 PM:
--
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is _rebuildIsMeaning{color:red}less{color}_ and
it is better to indicate in what cases method returns {{true}} in javadoc.
was (Author: pavlukhin):
[~EdShangGG], a following code caught my attention
{code}
* @return False if index rebuild is meaningless.
*/
private boolean rebuildIsMeaningful(GridCacheContext cctx) {
{code}
It seems that method semantic is rebuildIsMeaning *less* and it is better to
indicate in what cases method returns {{true}} in javadoc.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11638) Web console: 'Export All' in query result table doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11638: -- Ignite Flags: (was: Docs Required) > Web console: 'Export All' in query result table doesn't work > > > Key: IGNITE-11638 > URL: https://issues.apache.org/jira/browse/IGNITE-11638 > Project: Ignite > Issue Type: Test > Components: wizards >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Andrey Novikov >Priority: Minor > Fix For: 2.8 > > Attachments: image.png > > > Execute any EXPLAIN > Try to 'Export All' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11605) Race between pending future and local metadata putting
[
https://issues.apache.org/jira/browse/IGNITE-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11605:
--
Ignite Flags: (was: Docs Required)
> Race between pending future and local metadata putting
> --
>
> Key: IGNITE-11605
> URL: https://issues.apache.org/jira/browse/IGNITE-11605
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage is flaky.
> {noformat}
> java.lang.AssertionError:
> Expected :1
> Actual :2
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.ignite.testframework.junits.JUnitAssertAware.assertEquals(JUnitAssertAware.java:94)
> at
> org.apache.ignite.internal.processors.cache.BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage(BinaryTypeRegistrationTest.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11605) Race between pending future and local metadata putting
[
https://issues.apache.org/jira/browse/IGNITE-11605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11605:
--
Fix Version/s: 2.8
> Race between pending future and local metadata putting
> --
>
> Key: IGNITE-11605
> URL: https://issues.apache.org/jira/browse/IGNITE-11605
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage is flaky.
> {noformat}
> java.lang.AssertionError:
> Expected :1
> Actual :2
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.ignite.testframework.junits.JUnitAssertAware.assertEquals(JUnitAssertAware.java:94)
> at
> org.apache.ignite.internal.processors.cache.BinaryTypeRegistrationTest.shouldSendOnlyOneMetadataMessage(BinaryTypeRegistrationTest.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2102)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9539) Add SQL column precision existence check if scale parameter is setted
[ https://issues.apache.org/jira/browse/IGNITE-9539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail reassigned IGNITE-9539: - Assignee: (was: PetrovMikhail) > Add SQL column precision existence check if scale parameter is setted > - > > Key: IGNITE-9539 > URL: https://issues.apache.org/jira/browse/IGNITE-9539 > Project: Ignite > Issue Type: Bug >Reporter: PetrovMikhail >Priority: Major > Labels: sql-engine > > We should handle situation when user sets only scale without precision in > decimal column constraints. According to > [http://www.h2database.com/html/datatypes.html#decimal_type] it's not valid > behavior. > Currently, we ignore it. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8223) GridNearTxLocal.clearPrepareFuture does effectively nothing
[
https://issues.apache.org/jira/browse/IGNITE-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802882#comment-16802882
]
Rodion commented on IGNITE-8223:
[~ivan.glukos], could you review, plz?
> GridNearTxLocal.clearPrepareFuture does effectively nothing
> ---
>
> Key: IGNITE-8223
> URL: https://issues.apache.org/jira/browse/IGNITE-8223
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Rodion
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8
>
>
> It's unclear whether {{GridNearTxLocal.clearPrepareFuture}} is called at all,
> but the method does nothing, since its argument type is never used as target
> field value. Proposed change is to make the method no-op explicitly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11643) Optimize GC pressure on GridDhtPartitionTopologyImpl#updateRebalanceVersion
Vladislav Pyatkov created IGNITE-11643:
--
Summary: Optimize GC pressure on
GridDhtPartitionTopologyImpl#updateRebalanceVersion
Key: IGNITE-11643
URL: https://issues.apache.org/jira/browse/IGNITE-11643
Project: Ignite
Issue Type: Improvement
Reporter: Vladislav Pyatkov
Have surplused HashMap in the method
{{GridDhtPartitionTopologyImpl#updateRebalanceVersion}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11640) IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop
[
https://issues.apache.org/jira/browse/IGNITE-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11640:
-
Description:
It seems that this hang can be explained as follows:
# 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
acquire the checkpoint read lock.
It is important to note that gateway lock for the corresponding cache is
already acquired.
Let's assume the checkpoint read lock cannot be acquired right now because
there are many dirty pages, and, therefore, the 'vacuum' has to wait for a next
checkpoint.
{noformat}
"vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
[0x7f5ee49eb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:146)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1565)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.cleanup(MvccProcessorImpl.java:2395)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.processPartition(MvccProcessorImpl.java:2270)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.body(MvccProcessorImpl.java:2188)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748){noformat}
# On the other hand, the checkpoint thread can be already stopped by
Ignition#stop(cancel = true)
In that case, scheduledCp.cpFinishFut is not completed (it seems to me, this is
definitely a bug) and leads to a deadlock:
{noformat}
"test-runner-#302%db.IgnitePdsPageEvictionDuringPartitionClearTest%" #388
prio=5 os_prio=0 tid=0x7f60f461b800 nid=0x1f954b waiting on condition
[0x7f60338fc000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x95fe0948> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:934)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1247)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.tryLock(ReentrantReadWriteLock.java:1115)
at
org.apache.ignite.internal.util.StripedCompositeReadWriteLock$WriteLock.tryLock(StripedCompositeReadWriteLock.java:219)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:315)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:1142)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2399)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
- locked <0x9cd5fcc8> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
at org.apache.ignite.Ignition.stop(Ignition.java:223){noformat}
> IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop
> --
>
> Key: IGNITE-11640
> URL: https://issues.apache.org/jira/browse/IGNITE-11640
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
>
> It seems that this hang can be explained as follows:
> # 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
> acquire the checkpoint read lock.
> It is important to note that gateway lock for the corresponding cache is
> already acquired.
> Let's assume the checkpoint read lock cannot be acquired right now because
> there are many dirty pages, and, therefore, the 'vacuum' has to wait for a
> next checkpoint.
> {noformat}
> "vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
> prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
> [0x7f5ee49eb000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSup
[jira] [Updated] (IGNITE-11640) IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop
[
https://issues.apache.org/jira/browse/IGNITE-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11640:
-
Description:
It seems that this hang can be explained as follows:
* 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
acquire the checkpoint read lock.
It is important to note that gateway lock for the corresponding cache is
already acquired.
Let's assume the checkpoint read lock cannot be acquired right now because
there are many dirty pages, and, therefore, the 'vacuum' has to wait for a next
checkpoint.
{noformat}
"vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
[0x7f5ee49eb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:146)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1565)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.cleanup(MvccProcessorImpl.java:2395)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.processPartition(MvccProcessorImpl.java:2270)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.body(MvccProcessorImpl.java:2188)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748){noformat}
* On the other hand, the checkpoint thread can be already stopped by
Ignition#stop(cancel = true)
In that case, scheduledCp.cpFinishFut is not completed (it seems to me, this
is definitely a bug) and leads to a deadlock:
{noformat}
"test-runner-#302%db.IgnitePdsPageEvictionDuringPartitionClearTest%" #388
prio=5 os_prio=0 tid=0x7f60f461b800 nid=0x1f954b waiting on condition
[0x7f60338fc000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x95fe0948> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:934)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1247)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.tryLock(ReentrantReadWriteLock.java:1115)
at
org.apache.ignite.internal.util.StripedCompositeReadWriteLock$WriteLock.tryLock(StripedCompositeReadWriteLock.java:219)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:315)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:1142)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2399)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
- locked <0x9cd5fcc8> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
at org.apache.ignite.Ignition.stop(Ignition.java:223){noformat}
was:
It seems that this hang can be explained as follows:
# 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
acquire the checkpoint read lock.
It is important to note that gateway lock for the corresponding cache is
already acquired.
Let's assume the checkpoint read lock cannot be acquired right now because
there are many dirty pages, and, therefore, the 'vacuum' has to wait for a next
checkpoint.
{noformat}
"vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
[0x7f5ee49eb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:146)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1565)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.cleanup(MvccProcessorImpl.java:2395)
at
org.a
[jira] [Updated] (IGNITE-11640) IgnitePdsPageEvictionDuringPartitionClearTest sometimes hangs on node stop
[
https://issues.apache.org/jira/browse/IGNITE-11640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11640:
-
Description:
It seems that this hang can be explained as follows:
* 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
acquire the checkpoint read lock.
It is important to note that gateway lock for the corresponding cache is
already acquired.
Let's assume the checkpoint read lock cannot be acquired right now because
there are many dirty pages, and, therefore, the 'vacuum' has to wait for a next
checkpoint.
{noformat}
"vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
[0x7f5ee49eb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:146)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1565)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.cleanup(MvccProcessorImpl.java:2395)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.processPartition(MvccProcessorImpl.java:2270)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.body(MvccProcessorImpl.java:2188)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748){noformat}
* On the other hand, the checkpoint thread can be already stopped by
{{Ignition#stop(cancel = true)}}
In that case, {{scheduledCp.cpFinishFut}} is not completed (it seems to me,
this is definitely a bug) and leads to a deadlock:
{noformat}
"test-runner-#302%db.IgnitePdsPageEvictionDuringPartitionClearTest%" #388
prio=5 os_prio=0 tid=0x7f60f461b800 nid=0x1f954b waiting on condition
[0x7f60338fc000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x95fe0948> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:934)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1247)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.tryLock(ReentrantReadWriteLock.java:1115)
at
org.apache.ignite.internal.util.StripedCompositeReadWriteLock$WriteLock.tryLock(StripedCompositeReadWriteLock.java:219)
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:315)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:1142)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2399)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2283)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2570)
- locked <0x9cd5fcc8> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2533)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:330)
at org.apache.ignite.Ignition.stop(Ignition.java:223){noformat}
was:
It seems that this hang can be explained as follows:
* 'vacuum-cleaner' thread tries to clean up a cache entry and so it needs to
acquire the checkpoint read lock.
It is important to note that gateway lock for the corresponding cache is
already acquired.
Let's assume the checkpoint read lock cannot be acquired right now because
there are many dirty pages, and, therefore, the 'vacuum' has to wait for a next
checkpoint.
{noformat}
"vacuum-cleaner-#484%db.IgnitePdsPageEvictionDuringPartitionClearTest0%" #587
prio=5 os_prio=0 tid=0x7f5e2c007800 nid=0x1f960e waiting on condition
[0x7f5ee49eb000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:146)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.checkpointReadLock(GridCacheDatabaseSharedManager.java:1565)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl$VacuumWorker.cleanup(MvccProcessorImpl.java:2395)
[jira] [Assigned] (IGNITE-11643) Optimize GC pressure on GridDhtPartitionTopologyImpl#updateRebalanceVersion
[
https://issues.apache.org/jira/browse/IGNITE-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov reassigned IGNITE-11643:
--
Assignee: Vladislav Pyatkov
> Optimize GC pressure on GridDhtPartitionTopologyImpl#updateRebalanceVersion
> ---
>
> Key: IGNITE-11643
> URL: https://issues.apache.org/jira/browse/IGNITE-11643
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Have surplused HashMap in the method
> {{GridDhtPartitionTopologyImpl#updateRebalanceVersion}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10138) Description is not provided for operations of org.apache.ignite.mxbean.TransactionMetricsMxBean
[ https://issues.apache.org/jira/browse/IGNITE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10138: -- Fix Version/s: (was: 2.5) 2.8 > Description is not provided for operations of > org.apache.ignite.mxbean.TransactionMetricsMxBean > --- > > Key: IGNITE-10138 > URL: https://issues.apache.org/jira/browse/IGNITE-10138 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Max Shonichev >Assignee: Andrey Kalinin >Priority: Minor > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Description mismatch for bean > 'TransactionMetrics.TransactionMetricsMxBeanImpl' > operation 'commitTime()': expected 'Last commit time.', actual 'Operation > exposed for management' > operation 'rollbackTime()': expected 'Last rollback time.', actual 'Operation > exposed for management' > operation 'txCommits()': expected 'Number of transaction commits.', actual > 'Operation exposed for management' > operation 'txRollbacks()': expected 'Number of transaction rollbacks.', > actual 'Operation exposed for management' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11086) IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of seconds.
[
https://issues.apache.org/jira/browse/IGNITE-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11086:
--
Fix Version/s: 2.8
> IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of
> seconds.
> --
>
> Key: IGNITE-11086
> URL: https://issues.apache.org/jira/browse/IGNITE-11086
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.7
>Reporter: Vitaliy Biryukov
>Assignee: Andrey Kalinin
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should be set in
> seconds.
> Can be fixed by multiplying this parameter by 1000 instead of 100 in
> GridRestProcessor's constructor:
> {code:java}
> sesTokTtl =
> IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT,
> DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7883) Cluster can have inconsistent affinity configuration
[
https://issues.apache.org/jira/browse/IGNITE-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802903#comment-16802903
]
Andrey Gura commented on IGNITE-7883:
-
[~a-polyakov] I've took a look ti the change and have some comments:
1. {{GridCacheUtils#validateAffinityKeyConfiguration(CacheKeyConfiguration[])}}
I think better name is {{validateKeyConfigiration}}.
Please fix message of {{IgniteCheckedException}}. At the moment it is too
verbose and unclear. I think it should be something like "Cache key
configuration contains conflicting definitions: [cacheGroup=<>, cache=<>,
typeName=<>, affKeyFieldName1=<>, affKeyFieldName2=<>]".
Javadoc should have more accurate formulation. E..g it's unclear words "items"
and "full". Proper comment will be "all fields are initialized and not empty".
Please rewrite javadoc.
2. {{GridCacheUtils#validateAffinityKeyConfiguration(String, UUID,
CacheKeyConfiguration[], CacheKeyConfiguration[])}}
I think better name is {{validateKeyConfigiration}}.
{{oldCacheKeyCfgs}} and {{newCacheKeyCfgs}} parameters should be renamed to
{{rmtCacheKeyCfgs}} and {{locCacheKeyCfgs}} respectively.
Please fix message of {{IgniteCheckedException}}. At the moment it is too
verbose and unclear. For example see message that generates
{{GridCacheUtils#checkAttributeMismatch}} method. Also note that it could be
exception or just log message at warning level (it depends on
{{IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK}} system property). Also see p. 1
above.
Format method's code properly.
Fix javadoc in order to properly describe method parameters after renaming.
3. {{CacheKeyConfiguration#equals}}
Use {{Objects.equals}} instead of too long expressions at the method end.
4. {{CacheAffinityKeyConfigurationMismatchTest}}
Please, rewrite javadoc o the class.
Reformat code. Comma should always be on the same line where previous method
parameter placed.
Rewrite test code. Framework has set of methods for getting ignite and cache
configuration. So methods like {getIgnite}} are redundant. See
{{GridAbstractTest#getConfiguration()}} and other ignite tests for example.
Add additional tests for teh following cases:
- testKeyConfigurationLengthMismatch - you test only case when we have key
configuration on one node and don't have on another. What about different key
configurations on nodes?
- testKeyConfigurationDuplicateTypeName - you test only case for one node. What
about conflicting defintions from different nodes?
It makes sense to add test cases for configurations that were constructed due
to using {{@AffinityKeyMapped}} annotation.
> Cluster can have inconsistent affinity configuration
> -
>
> Key: IGNITE-7883
> URL: https://issues.apache.org/jira/browse/IGNITE-7883
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexand Polyakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A cluster can have inconsistent affinity configuration if you created two
> nodes, one with affinity key configuration and other without it(in IgniteCfg
> or CacheCfg), both nodes will work fine with no exceptions, but in the same
> time they will apply different affinity rules to keys:
>
> {code:java}
> package affinity;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.CacheAtomicityMode;
> import org.apache.ignite.cache.CacheKeyConfiguration;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.affinity.Affinity;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import java.util.Arrays;
> public class Test {
> private static int id = 0;
> public static void main(String[] args) {
> Ignite ignite = Ignition.start(getConfiguration(true, false));
> Ignite ignite2 = Ignition.start(getConfiguration(false, false));
> Affinity affinity = ignite.affinity("TEST");
> Affinity affinity2 = ignite2.affinity("TEST");
> for (int i = 0; i < 1_000_000; i++) {
> AKey key = new AKey(i);
> if(affinity.partition(key) != affinity2.partition(key))
> System.out.println("FAILED for: " + key);
> }
> System.out.println("DONE");
> }
> private static IgniteConfiguration getConfiguration(boolean
> withAffinityCfg, boolean client) {
> IgniteConfiguration cfg = new IgniteConfiguration();
> TcpDiscoveryVmIpFinder finder = new TcpDis
[jira] [Commented] (IGNITE-11606) Index could not contain all values from cache after index full rebuild
[
https://issues.apache.org/jira/browse/IGNITE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802913#comment-16802913
]
Eduard Shangareev commented on IGNITE-11606:
[~vozerov], [~Pavlukhin], please, take a look.
> Index could not contain all values from cache after index full rebuild
> --
>
> Key: IGNITE-11606
> URL: https://issues.apache.org/jira/browse/IGNITE-11606
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If index.bin was deleted, we would rebuild it on node start.
> But it could cause to the situation when a key is in the cache but SQL query
> doesn't return it.
> {code}
> [18:29:07][:363] idle_verify check has finished, found 1194 conflict
> partitions: [counterConflicts=0, hashConflicts=1194]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11411) Remove tearDown, setUp from JUnit3TestLegacySupport
[ https://issues.apache.org/jira/browse/IGNITE-11411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802933#comment-16802933 ] Eduard Shangareev commented on IGNITE-11411: Looks good! Thank you for contribution. > Remove tearDown, setUp from JUnit3TestLegacySupport > --- > > Key: IGNITE-11411 > URL: https://issues.apache.org/jira/browse/IGNITE-11411 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: iep-30 > Time Spent: 10m > Remaining Estimate: 0h > > TearDown and setUp methods are deprecated for JUnit 4+ version. It is > necessary to replace them with appropriate methods, marked by @Before and > @After annotations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10814) Exceptions thrown in InitNewCoordinatorFuture.init() are ignored
[ https://issues.apache.org/jira/browse/IGNITE-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802959#comment-16802959 ] Alexey Goncharuk commented on IGNITE-10814: --- This has been fixed as a part of IGNITE-10815, closing. > Exceptions thrown in InitNewCoordinatorFuture.init() are ignored > > > Key: IGNITE-10814 > URL: https://issues.apache.org/jira/browse/IGNITE-10814 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > > Exceptions thrown by InitNewCoordinatorFuture.init() called from > GridDhtPartitionsExchangeFuture.onNodeLeft is ignored silently and may result > in cluster hang without cause seen in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10814) Exceptions thrown in InitNewCoordinatorFuture.init() are ignored
[ https://issues.apache.org/jira/browse/IGNITE-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-10814: -- Fix Version/s: 2.8 > Exceptions thrown in InitNewCoordinatorFuture.init() are ignored > > > Key: IGNITE-10814 > URL: https://issues.apache.org/jira/browse/IGNITE-10814 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > > Exceptions thrown by InitNewCoordinatorFuture.init() called from > GridDhtPartitionsExchangeFuture.onNodeLeft is ignored silently and may result > in cluster hang without cause seen in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10814) Exceptions thrown in InitNewCoordinatorFuture.init() are ignored
[ https://issues.apache.org/jira/browse/IGNITE-10814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-10814. --- Resolution: Invalid > Exceptions thrown in InitNewCoordinatorFuture.init() are ignored > > > Key: IGNITE-10814 > URL: https://issues.apache.org/jira/browse/IGNITE-10814 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > > Exceptions thrown by InitNewCoordinatorFuture.init() called from > GridDhtPartitionsExchangeFuture.onNodeLeft is ignored silently and may result > in cluster hang without cause seen in logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8588) .NET: Serialization issue when derived type hides base type member
[
https://issues.apache.org/jira/browse/IGNITE-8588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Shapkin reassigned IGNITE-8588:
Assignee: Alexandr Shapkin (was: Pavel Tupitsyn)
> .NET: Serialization issue when derived type hides base type member
> --
>
> Key: IGNITE-8588
> URL: https://issues.apache.org/jira/browse/IGNITE-8588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Alexandr Shapkin
>Priority: Major
> Labels: .NET
>
> The following class structure causes an exception that is hard to understand
> (when putting instance of B into Ignite cache):
> {code}
> public class A
> {
> public int bob;
> }
> public class B : A
> {
> public int bob;
> }
> {code}
> Exception:
> {code}
> Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field IDs
> [type=SubGridsRequestArgument, field1=Filters, field2=Filters,
> fieldId=-854547461]
> at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
> at
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type, Int32
> typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor desc)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFullTypeDescriptor desc)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)
> at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
> at
> Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.WriteWithPeerDeployment(BinaryWriter
> writer, Object o)
> at
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
> at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
> at
> Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1
> obj, BinaryWriter writer)
> at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)
> at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T o)
> at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob job,
> BinaryWriter writer)
> at
> Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.b__1a(BinaryWriter
> writer)
> at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1
> action, IBinaryStream stream, Marshaller marsh)
> at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type,
> Action`1 writeAction)
> at
> Apache.Ignite.Core.Impl.Compute.ComputeImpl.ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3
> task, IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount,
> Action`1 writeAction)
> --- End of inner exception stack trace ---
> at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean
> includeTaskCanceledExceptions)
> at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout,
> CancellationToken cancellationToken)
> at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)
> at VSS.TRex.GridFabric.Requests.SubGridRequestsProgressive`2.Execute() in
> C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\GridFabric\Requests\SubGridRequestsProgressive.cs:line
> 107
> at VSS.TRex.Pipelines.SubGridPipelineBase`3.Initiate() in
> C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Pipelines\SubGridPipelineBase.cs:line
> 241
> at VSS.TRex.Rendering.PlanViewTileRenderer.ExecutePipeline() in
> C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Rendering\PlanViewTileRenderer.cs:line
> 262
> ---> (Inner Exception #0) Apache.Ignite.Core.Binary.BinaryObjectException:
> Conflicting field IDs [type=SubGridsRequestArgument, field1=Filters,
> field2=Filters, fieldId=-854547461]
> at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type
> type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper,
> Boolean forceTimestamp)
> at
> Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration
> cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId,
> IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type, Int32
> typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor desc)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type,
> BinaryFull
[jira] [Commented] (IGNITE-9812) Explicit tests with expired SSL certificates
[ https://issues.apache.org/jira/browse/IGNITE-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802969#comment-16802969 ] Ilya Kasnacheev commented on IGNITE-9812: - [~agura] thank you for review, change is merged. > Explicit tests with expired SSL certificates > > > Key: IGNITE-9812 > URL: https://issues.apache.org/jira/browse/IGNITE-9812 > Project: Ignite > Issue Type: Test > Components: clients, security >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Labels: test > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > It came to our attention that we have no test which checks that expired SSL > certificates do not work indeed. > Should get such old certificate from git, check if it will fail to join > cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11588) The wrong result for Query
[
https://issues.apache.org/jira/browse/IGNITE-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kuznetsov reassigned IGNITE-11588:
Assignee: Pavel Kuznetsov (was: Igor Sapego)
> The wrong result for Query
> --
>
> Key: IGNITE-11588
> URL: https://issues.apache.org/jira/browse/IGNITE-11588
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
> Environment: Windows 10, Visual Studio 2010 Pro, Oracle JDK 8
>Reporter: Sergey Kozlov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Attachments: query-example-fix.xml, query_example.cpp
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I use modified C++ Query Example (see attached files) that verify the
> received result against expected one and print out message if they're
> different.
> Just copy *.cpp file in {{platforms/cpp/examples/query-example/src}} and
> build example project
> 1. Start two nodes {{bin\ignite.bat query-example-fix.xml -v}}
> 2. Run query-example.exe:
> {noformat}
> [13:35:48] Ignite node started OK (id=1e2c0f81)
> [13:35:48] Topology snapshot [ver=3, locNode=1e2c0f81, servers=3, clients=0,
> state=ACTIVE, CPUs=8, offheap=9.5GB, heap=2.9GB]
> >>> Cache query example started.
> Iteration 698. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 699. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 700. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 701. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 702. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 703. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 704. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 705. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
>
> Iteration 996. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 997. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 998. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> Iteration 999. Average salary for 'ApacheIgnite' employees, expected 1500,
> found: 2000
> [13:35:51] Ignite node stopped OK [uptime=00:00:02.652]
> >>> Example finished, press 'Enter' to exit ...
> {noformat}
> 3. All next runs have no failures
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11521) Lifecycle event just before joining the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803003#comment-16803003 ] Ilya Kasnacheev commented on IGNITE-11521: -- [~lukasp] do you still want this one accepted? On developers list you said that you don't. > Lifecycle event just before joining the cluster > --- > > Key: IGNITE-11521 > URL: https://issues.apache.org/jira/browse/IGNITE-11521 > Project: Ignite > Issue Type: New Feature >Reporter: Lukas Polacek >Priority: Major > > Add a new lifecycle event just before joining the cluster. At this point the > node is partially initialized and can already register event listeners, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11127) GridDhtInvalidPartitionException not handled by GridCacheTtlManager
[
https://issues.apache.org/jira/browse/IGNITE-11127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803035#comment-16803035
]
Ilya Kasnacheev commented on IGNITE-11127:
--
I went forward and merged this change! Thank you for fixing this! Also I added
check to make sure that test fails more often without this fix.
> GridDhtInvalidPartitionException not handled by GridCacheTtlManager
> ---
>
> Key: IGNITE-11127
> URL: https://issues.apache.org/jira/browse/IGNITE-11127
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.4, 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Roman Shtykh
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Leading to either message processing problems:
> {code}
> [2019-01-27 16:57:45,474][ERROR][sys-stripe-2-#3][GridCacheIoManager] Failed
> to process message [senderId=4839b5a2-a295-44cf-8a44-f0cb932b689e,
> messageType=class
> o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicFullUpdateRequest]
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=381, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=381, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=818, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=818, minorTopVer=0]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:917)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:952)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:943)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1047)
> at
> org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:835)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessageProcessed(GridCacheIoManager.java:1093)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1066)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> or unhandled unspecified exceptions in user code (possibly violating JCache):
> {code}
> [2019-01-27 10:23:35,451][ERROR][pub-#840058][ComputeJobProcess] class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=485, msg=Adding entry to partition that is concurrently evicted
> [grp=, part=485, shouldBeMoving=, belongs=false,
> topVer=AffinityTopologyVersion [topVer=815, minorTopVer=0],
> curTopVer=AffinityTopology
[jira] [Resolved] (IGNITE-8623) NPE during cache access
[ https://issues.apache.org/jira/browse/IGNITE-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk resolved IGNITE-8623. -- Resolution: Incomplete More information is needed. Resolving this for now. > NPE during cache access > --- > > Key: IGNITE-8623 > URL: https://issues.apache.org/jira/browse/IGNITE-8623 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Stelmak >Assignee: Alexey Stelmak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9759) CacheAsyncOperationsFailoverTxTest#testAsyncFailover test hangs up
[ https://issues.apache.org/jira/browse/IGNITE-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803064#comment-16803064 ] Alexey Goncharuk commented on IGNITE-9759: -- [~astelmak] do you have any updates? Can you unassign the issue if you are not working on this? > CacheAsyncOperationsFailoverTxTest#testAsyncFailover test hangs up > -- > > Key: IGNITE-9759 > URL: https://issues.apache.org/jira/browse/IGNITE-9759 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Stelmak >Assignee: Alexey Stelmak >Priority: Major > > The test stops, because not all futures completed correctly when nodes are > stopped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803074#comment-16803074
]
Alexey Goncharuk commented on IGNITE-4003:
--
[~ilantukh] are you still working on this? Can you please unassign the ticket
in case if you are not?
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Ilya Lantukh
>Priority: Critical
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloade
[jira] [Commented] (IGNITE-8877) PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads to OutOfMemoryError
[ https://issues.apache.org/jira/browse/IGNITE-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803085#comment-16803085 ] Alexey Goncharuk commented on IGNITE-8877: -- [~ilantukh] are you working on this? I am not sure if the test failure is relevant anymore, so maybe it makes sense to close the issue. > PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation > leads to OutOfMemoryError > > > Key: IGNITE-8877 > URL: https://issues.apache.org/jira/browse/IGNITE-8877 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > > TC history: > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7685795678405642188&branch=%3Cdefault%3E&tab=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh reassigned IGNITE-4003:
Assignee: (was: Ilya Lantukh)
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Priority: Critical
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.access$1000(GridDhtPreloader.java:81)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distribute
[jira] [Assigned] (IGNITE-8877) PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation leads to OutOfMemoryError
[ https://issues.apache.org/jira/browse/IGNITE-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-8877: Assignee: (was: Ilya Lantukh) > PartitionsExchangeOnDiscoveryHistoryOverflowTest.testDynamicCacheCreation > leads to OutOfMemoryError > > > Key: IGNITE-8877 > URL: https://issues.apache.org/jira/browse/IGNITE-8877 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Priority: Major > > TC history: > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7685795678405642188&branch=%3Cdefault%3E&tab=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4380) Cache invoke calls can be lost
[
https://issues.apache.org/jira/browse/IGNITE-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803120#comment-16803120
]
Alexey Goncharuk commented on IGNITE-4380:
--
[~NSAmelchev] are you planning to work on this issue? Can you please unassign
if not?
> Cache invoke calls can be lost
> --
>
> Key: IGNITE-4380
> URL: https://issues.apache.org/jira/browse/IGNITE-4380
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Semen Boikov
>Assignee: Amelchev Nikita
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> * Recently added test
> GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded fails on TC in
> various configurations with transactional cache.
> Example of failure
> GridCacheReplicatedOffHeapTieredMultiNodeFullApiSelfTest.testInvokeAllMultithreaded:
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<10868>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractFullApiSelfTest.testInvokeAllMultithreaded(GridCacheAbstractFullApiSelfTest.java:342)
> at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8223) GridNearTxLocal.clearPrepareFuture does effectively nothing
[
https://issues.apache.org/jira/browse/IGNITE-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803134#comment-16803134
]
Ivan Rakov commented on IGNITE-8223:
[~RodionVl], thanks, merged to master.
> GridNearTxLocal.clearPrepareFuture does effectively nothing
> ---
>
> Key: IGNITE-8223
> URL: https://issues.apache.org/jira/browse/IGNITE-8223
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Rodion
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8
>
>
> It's unclear whether {{GridNearTxLocal.clearPrepareFuture}} is called at all,
> but the method does nothing, since its argument type is never used as target
> field value. Proposed change is to make the method no-op explicitly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11644) Get rid of old exchange protocol
Alexey Goncharuk created IGNITE-11644: - Summary: Get rid of old exchange protocol Key: IGNITE-11644 URL: https://issues.apache.org/jira/browse/IGNITE-11644 Project: Ignite Issue Type: Improvement Reporter: Alexey Goncharuk Old (non-merging exchange protocol) is not used anymore and should be removed from the code to clean it up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
