[jira] [Commented] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.

[ https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475159#comment-16475159 ] Alexandr Kuramshin commented on IGNITE-8085: [~ivanan.fed], Yes, right. > Flaky failures in

[jira] [Commented] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.

[ https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474550#comment-16474550 ] Alexandr Kuramshin commented on IGNITE-8085: [~dpavlov], remote process startup procedure

[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process

[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448578#comment-16448578 ] Alexandr Kuramshin commented on IGNITE-4111: Hi [~dpavlov], actually I don't know >

[jira] [Assigned] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop

[ https://issues.apache.org/jira/browse/IGNITE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7152: -- Assignee: (was: Alexandr Kuramshin) > Failure detection timeout don't

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1640#comment-1640 ] Alexandr Kuramshin commented on IGNITE-5798: [~ivanan.fed], as you wish. > Logging Ignite

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409378#comment-16409378 ] Alexandr Kuramshin commented on IGNITE-5798: [~ivanan.fed], Earlier I've said that the every

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409073#comment-16409073 ] Alexandr Kuramshin commented on IGNITE-5798: [~ivanan.fed], current implementation rely on

[jira] [Assigned] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7788: -- Assignee: Alexey Goncharuk > Data loss after cold restart with PDS and cache

[jira] [Updated] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7788: --- Attachment: IgnitePdsCacheRestoreTest.java > Data loss after cold restart with PDS

[jira] [Updated] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7788: --- Attachment: (was: IgnitePdsCacheRestoreTest.java) > Data loss after cold restart

[jira] [Comment Edited] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372617#comment-16372617 ] Alexandr Kuramshin edited comment on IGNITE-7788 at 2/22/18 10:03 AM:

[jira] [Commented] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372617#comment-16372617 ] Alexandr Kuramshin commented on IGNITE-7788: Changing group on both caches (c1 and c2) causes

[jira] [Updated] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

[ https://issues.apache.org/jira/browse/IGNITE-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7788: --- Attachment: IgnitePdsCacheRestoreTest.java > Data loss after cold restart with PDS

[jira] [Created] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

Alexandr Kuramshin created IGNITE-7788: -- Summary: Data loss after cold restart with PDS and cache group change Key: IGNITE-7788 URL: https://issues.apache.org/jira/browse/IGNITE-7788 Project:

[jira] [Commented] (IGNITE-7723) Data loss after node restart with PDS

[ https://issues.apache.org/jira/browse/IGNITE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371212#comment-16371212 ] Alexandr Kuramshin commented on IGNITE-7723: Attached updated test which shows all problems

[jira] [Updated] (IGNITE-7723) Data loss after node restart with PDS

[ https://issues.apache.org/jira/browse/IGNITE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7723: --- Attachment: IgnitePdsDataLossTest.java > Data loss after node restart with PDS >

[jira] [Updated] (IGNITE-7723) Data loss after node restart with PDS

[ https://issues.apache.org/jira/browse/IGNITE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7723: --- Attachment: IgnitePdsDataLossTest.java > Data loss after node restart with PDS >

[jira] [Created] (IGNITE-7723) Data loss after node restart with PDS

Alexandr Kuramshin created IGNITE-7723: -- Summary: Data loss after node restart with PDS Key: IGNITE-7723 URL: https://issues.apache.org/jira/browse/IGNITE-7723 Project: Ignite Issue

[jira] [Created] (IGNITE-7634) Wrong NodeStoppingException on destroying cache

Alexandr Kuramshin created IGNITE-7634: -- Summary: Wrong NodeStoppingException on destroying cache Key: IGNITE-7634 URL: https://issues.apache.org/jira/browse/IGNITE-7634 Project: Ignite

[jira] [Created] (IGNITE-7633) Multiple errors on accessing page store while destroying cache

Alexandr Kuramshin created IGNITE-7633: -- Summary: Multiple errors on accessing page store while destroying cache Key: IGNITE-7633 URL: https://issues.apache.org/jira/browse/IGNITE-7633 Project:

[jira] [Created] (IGNITE-7632) NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics()

Alexandr Kuramshin created IGNITE-7632: -- Summary: NPE in IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.updateIgfsMetrics() Key: IGNITE-7632 URL: https://issues.apache.org/jira/browse/IGNITE-7632

[jira] [Created] (IGNITE-7631) Failed to clear page memory with AssertionError: Release pinned page

Alexandr Kuramshin created IGNITE-7631: -- Summary: Failed to clear page memory with AssertionError: Release pinned page Key: IGNITE-7631 URL: https://issues.apache.org/jira/browse/IGNITE-7631

[jira] [Created] (IGNITE-7630) NPE in SchemaIndexCacheVisitorImpl.processKey()

Alexandr Kuramshin created IGNITE-7630: -- Summary: NPE in SchemaIndexCacheVisitorImpl.processKey() Key: IGNITE-7630 URL: https://issues.apache.org/jira/browse/IGNITE-7630 Project: Ignite

[jira] [Created] (IGNITE-7629) NPE when Finished indexes rebuilding for cache

Alexandr Kuramshin created IGNITE-7629: -- Summary: NPE when Finished indexes rebuilding for cache Key: IGNITE-7629 URL: https://issues.apache.org/jira/browse/IGNITE-7629 Project: Ignite

[jira] [Commented] (IGNITE-7579) NPE in GridDhtLocalPartition.cacheMapHolder()

[ https://issues.apache.org/jira/browse/IGNITE-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352223#comment-16352223 ] Alexandr Kuramshin commented on IGNITE-7579: The same exception occurs on finishing exchange

[jira] [Created] (IGNITE-7579) NPE in GridDhtLocalPartition.cacheMapHolder()

Alexandr Kuramshin created IGNITE-7579: -- Summary: NPE in GridDhtLocalPartition.cacheMapHolder() Key: IGNITE-7579 URL: https://issues.apache.org/jira/browse/IGNITE-7579 Project: Ignite

[jira] [Created] (IGNITE-7383) Failed to restore memory after cluster restart and activating from outdated node

Alexandr Kuramshin created IGNITE-7383: -- Summary: Failed to restore memory after cluster restart and activating from outdated node Key: IGNITE-7383 URL: https://issues.apache.org/jira/browse/IGNITE-7383

[jira] [Assigned] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7135: -- Assignee: Alexandr Kuramshin > IgniteCluster.startNodes() returns successful

[jira] [Commented] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319693#comment-16319693 ] Alexandr Kuramshin commented on IGNITE-7135: Two improvements was done: 1) control remote

[jira] [Assigned] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7135: -- Assignee: (was: Semen Boikov) > IgniteCluster.startNodes() returns

[jira] [Assigned] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7135: -- Assignee: Semen Boikov (was: Alexandr Kuramshin) >

[jira] [Comment Edited] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303606#comment-16303606 ] Alexandr Kuramshin edited comment on IGNITE-7135 at 12/26/17 7:32 AM:

[jira] [Updated] (IGNITE-6433) We need to cancel eviction instead of waiting it when we should own a partition because we had lost it

[ https://issues.apache.org/jira/browse/IGNITE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6433: --- Priority: Critical (was: Major) > We need to cancel eviction instead of waiting it

[jira] [Commented] (IGNITE-6433) We need to cancel eviction instead of waiting it when we should own a partition because we had lost it

[ https://issues.apache.org/jira/browse/IGNITE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287418#comment-16287418 ] Alexandr Kuramshin commented on IGNITE-6433: The following thread deadlock occurs frequently

[jira] [Created] (IGNITE-7163) Validate connection from a pre-previous node

Alexandr Kuramshin created IGNITE-7163: -- Summary: Validate connection from a pre-previous node Key: IGNITE-7163 URL: https://issues.apache.org/jira/browse/IGNITE-7163 Project: Ignite

[jira] [Created] (IGNITE-7162) Control discovery messages processing time

Alexandr Kuramshin created IGNITE-7162: -- Summary: Control discovery messages processing time Key: IGNITE-7162 URL: https://issues.apache.org/jira/browse/IGNITE-7162 Project: Ignite

[jira] [Created] (IGNITE-7161) Detect self-freeze on remote node related operations with timeout

Alexandr Kuramshin created IGNITE-7161: -- Summary: Detect self-freeze on remote node related operations with timeout Key: IGNITE-7161 URL: https://issues.apache.org/jira/browse/IGNITE-7161

[jira] [Resolved] (IGNITE-7134) Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()

[ https://issues.apache.org/jira/browse/IGNITE-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin resolved IGNITE-7134. Resolution: Won't Fix Fix Version/s: (was: 2.4) None

[jira] [Created] (IGNITE-7160) Ignore messages from not alive and failed nodes

Alexandr Kuramshin created IGNITE-7160: -- Summary: Ignore messages from not alive and failed nodes Key: IGNITE-7160 URL: https://issues.apache.org/jira/browse/IGNITE-7160 Project: Ignite

[jira] [Created] (IGNITE-7158) TCP discovery improvement

Alexandr Kuramshin created IGNITE-7158: -- Summary: TCP discovery improvement Key: IGNITE-7158 URL: https://issues.apache.org/jira/browse/IGNITE-7158 Project: Ignite Issue Type:

[jira] [Commented] (IGNITE-7134) Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()

[ https://issues.apache.org/jira/browse/IGNITE-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283436#comment-16283436 ] Alexandr Kuramshin commented on IGNITE-7134: Actual infinite timeout reason. > Never-ending

[jira] [Updated] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop

[ https://issues.apache.org/jira/browse/IGNITE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7152: --- Attachment: testFailureDetectionOnReceiptError.patch Simple reproducer > Failure

[jira] [Assigned] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop

[ https://issues.apache.org/jira/browse/IGNITE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7152: -- Assignee: Alexandr Kuramshin > Failure detection timeout don't work on

[jira] [Created] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop

Alexandr Kuramshin created IGNITE-7152: -- Summary: Failure detection timeout don't work on permanent send message errors causing infinite loop Key: IGNITE-7152 URL:

[jira] [Assigned] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[ https://issues.apache.org/jira/browse/IGNITE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7135: -- Assignee: Alexandr Kuramshin > IgniteCluster.startNodes() returns successful

[jira] [Assigned] (IGNITE-7134) Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()

[ https://issues.apache.org/jira/browse/IGNITE-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-7134: -- Assignee: Alexandr Kuramshin > Never-ending timeout in

[jira] [Created] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

Alexandr Kuramshin created IGNITE-7135: -- Summary: IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails Key: IGNITE-7135 URL:

[jira] [Updated] (IGNITE-7095) JdbcConnection hard linked in IgniteH2Indexing preventing old connections from closing

[ https://issues.apache.org/jira/browse/IGNITE-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-7095: --- Attachment: IndexClientTest.java IndexTest.java Simple reproducer.

[jira] [Created] (IGNITE-7095) JdbcConnection hard linked in IgniteH2Indexing preventing old connections from closing

Alexandr Kuramshin created IGNITE-7095: -- Summary: JdbcConnection hard linked in IgniteH2Indexing preventing old connections from closing Key: IGNITE-7095 URL:

[jira] [Commented] (IGNITE-4912) Fix testDeployCalledAfterCacheStart and testDeployCalledBeforeCacheStart tests

[ https://issues.apache.org/jira/browse/IGNITE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16260336#comment-16260336 ] Alexandr Kuramshin commented on IGNITE-4912: Actually

[jira] [Updated] (IGNITE-6967) PME deadlock on reassigning service deployment

[ https://issues.apache.org/jira/browse/IGNITE-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6967: --- Description: With a service deployment when topology change occurs the discovery

[jira] [Created] (IGNITE-6967) PME deadlock on reassigning service deployment

Alexandr Kuramshin created IGNITE-6967: -- Summary: PME deadlock on reassigning service deployment Key: IGNITE-6967 URL: https://issues.apache.org/jira/browse/IGNITE-6967 Project: Ignite

[jira] [Updated] (IGNITE-6965) affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left

[ https://issues.apache.org/jira/browse/IGNITE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6965: --- Attachment:

[jira] [Updated] (IGNITE-6965) affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left

[ https://issues.apache.org/jira/browse/IGNITE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6965: --- Attachment: (was:

[jira] [Updated] (IGNITE-6965) affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left

[ https://issues.apache.org/jira/browse/IGNITE-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6965: --- Attachment:

[jira] [Created] (IGNITE-6965) affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left

Alexandr Kuramshin created IGNITE-6965: -- Summary: affinityCall() with key mapping may not be successful with AlwaysFailoverSpi when node left Key: IGNITE-6965 URL:

[jira] [Assigned] (IGNITE-6827) Configurable rollback for long running transactions before partition exchange

[ https://issues.apache.org/jira/browse/IGNITE-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6827: -- Assignee: Alexandr Kuramshin > Configurable rollback for long running

[jira] [Commented] (IGNITE-4939) Receive event before cache initialized

[ https://issues.apache.org/jira/browse/IGNITE-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248934#comment-16248934 ] Alexandr Kuramshin commented on IGNITE-4939: Was reproduced recently on TC

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[ https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-79: - Fix Version/s: 2.4 > Illegal state exception in affinity assignment cache >

[jira] [Assigned] (IGNITE-79) Illegal state exception in affinity assignment cache

[ https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-79: Assignee: Stanilovsky Evgeny > Illegal state exception in affinity assignment cache

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[ https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-79: - Attachment: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log > Illegal state

[jira] [Commented] (IGNITE-79) Illegal state exception in affinity assignment cache

[ https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248925#comment-16248925 ] Alexandr Kuramshin commented on IGNITE-79: -- Recently reproduced with

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[ https://issues.apache.org/jira/browse/IGNITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-79: - Affects Version/s: 2.3 > Illegal state exception in affinity assignment cache >

[jira] [Created] (IGNITE-6860) Lack of context information upon serializing and marshalling (writeObject and writeFields)

Alexandr Kuramshin created IGNITE-6860: -- Summary: Lack of context information upon serializing and marshalling (writeObject and writeFields) Key: IGNITE-6860 URL:

[jira] [Created] (IGNITE-6858) Wait for exchange inside GridReduceQueryExecutor.query which never finishes due to opened transaction

Alexandr Kuramshin created IGNITE-6858: -- Summary: Wait for exchange inside GridReduceQueryExecutor.query which never finishes due to opened transaction Key: IGNITE-6858 URL:

[jira] [Assigned] (IGNITE-6700) Node considered as failed can cause failure of others nodes

[ https://issues.apache.org/jira/browse/IGNITE-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6700: -- Assignee: Alexandr Kuramshin (was: Semen Boikov) > Node considered as failed

[jira] [Commented] (IGNITE-6519) Race in SplitAwareTopologyValidator on activator and server node join

[ https://issues.apache.org/jira/browse/IGNITE-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215010#comment-16215010 ] Alexandr Kuramshin commented on IGNITE-6519: Testing done with success. Please review > Race

[jira] [Assigned] (IGNITE-6519) Race in SplitAwareTopologyValidator on activator and server node join

[ https://issues.apache.org/jira/browse/IGNITE-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6519: -- Assignee: Semen Boikov (was: Alexandr Kuramshin) > Race in

[jira] [Created] (IGNITE-6636) BinaryStream position integer overflow

Alexandr Kuramshin created IGNITE-6636: -- Summary: BinaryStream position integer overflow Key: IGNITE-6636 URL: https://issues.apache.org/jira/browse/IGNITE-6636 Project: Ignite Issue

[jira] [Assigned] (IGNITE-6521) Review default JVM options for better performance

[ https://issues.apache.org/jira/browse/IGNITE-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6521: -- Assignee: Dmitriy Govorukhin (was: Alexandr Kuramshin) > Review default JVM

[jira] [Commented] (IGNITE-6507) Commit can be lost in network split scenario

[ https://issues.apache.org/jira/browse/IGNITE-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201815#comment-16201815 ] Alexandr Kuramshin commented on IGNITE-6507: I've found that after

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196668#comment-16196668 ] Alexandr Kuramshin commented on IGNITE-5798: Hi, [~ivanan.fed] 1. I think we should use

[jira] [Created] (IGNITE-6536) NPE on registerClassName() with MappedName

Alexandr Kuramshin created IGNITE-6536: -- Summary: NPE on registerClassName() with MappedName Key: IGNITE-6536 URL: https://issues.apache.org/jira/browse/IGNITE-6536 Project: Ignite

[jira] [Created] (IGNITE-6521) Review default JVM options for better performance

Alexandr Kuramshin created IGNITE-6521: -- Summary: Review default JVM options for better performance Key: IGNITE-6521 URL: https://issues.apache.org/jira/browse/IGNITE-6521 Project: Ignite

[jira] [Created] (IGNITE-6519) Race in SplitAwareTopologyValidator on activator and server node join

Alexandr Kuramshin created IGNITE-6519: -- Summary: Race in SplitAwareTopologyValidator on activator and server node join Key: IGNITE-6519 URL: https://issues.apache.org/jira/browse/IGNITE-6519

[jira] [Updated] (IGNITE-6499) Compact NULL fields binary representation

[ https://issues.apache.org/jira/browse/IGNITE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6499: --- Description: Current compact footer implementation writes offset for the every field

[jira] [Updated] (IGNITE-6499) Compact NULL fields binary representation

[ https://issues.apache.org/jira/browse/IGNITE-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-6499: --- Description: Current compact footer implementation writes offset for the every field

[jira] [Created] (IGNITE-6499) Compact NULL fields binary representation

Alexandr Kuramshin created IGNITE-6499: -- Summary: Compact NULL fields binary representation Key: IGNITE-6499 URL: https://issues.apache.org/jira/browse/IGNITE-6499 Project: Ignite Issue

[jira] [Updated] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[ https://issues.apache.org/jira/browse/IGNITE-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-4865: --- Fix Version/s: (was: 2.3) > Non-informative error message on using

[jira] [Updated] (IGNITE-5026) getOrCreateCaches() hangs if any exception in GridDhtPartitionsExchangeFuture.init()

[ https://issues.apache.org/jira/browse/IGNITE-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-5026: --- Fix Version/s: (was: 2.3) > getOrCreateCaches() hangs if any exception in >

[jira] [Updated] (IGNITE-5251) Some JVM implementations may return null from getClassLoader()

[ https://issues.apache.org/jira/browse/IGNITE-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-5251: --- Fix Version/s: (was: 2.3) > Some JVM implementations may return null from

[jira] [Updated] (IGNITE-5798) Logging Ignite configuration at startup

[ https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin updated IGNITE-5798: --- Fix Version/s: (was: 2.3) > Logging Ignite configuration at startup >

[jira] [Created] (IGNITE-6491) Race in TopologyValidator.validate() and EVT_NODE_LEFT listener calls (split-brain activator)

Alexandr Kuramshin created IGNITE-6491: -- Summary: Race in TopologyValidator.validate() and EVT_NODE_LEFT listener calls (split-brain activator) Key: IGNITE-6491 URL:

[jira] [Commented] (IGNITE-6200) org.dom4j.QName can't be serialized

[ https://issues.apache.org/jira/browse/IGNITE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167737#comment-16167737 ] Alexandr Kuramshin commented on IGNITE-6200: TC looks good, please review > org.dom4j.QName

[jira] [Assigned] (IGNITE-6200) org.dom4j.QName can't be serialized

[ https://issues.apache.org/jira/browse/IGNITE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6200: -- Assignee: Andrey Gura (was: Alexandr Kuramshin) > org.dom4j.QName can't be

[jira] [Assigned] (IGNITE-6200) org.dom4j.QName can't be serialized

[ https://issues.apache.org/jira/browse/IGNITE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-6200: -- Assignee: Alexandr Kuramshin > org.dom4j.QName can't be serialized >

[jira] [Commented] (IGNITE-6200) org.dom4j.QName can't be serialized

[ https://issues.apache.org/jira/browse/IGNITE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164385#comment-16164385 ] Alexandr Kuramshin commented on IGNITE-6200: When writing a serializable object by the

[jira] [Created] (IGNITE-6347) Exception in GridDhtPartitionMap.readExternal

Alexandr Kuramshin created IGNITE-6347: -- Summary: Exception in GridDhtPartitionMap.readExternal Key: IGNITE-6347 URL: https://issues.apache.org/jira/browse/IGNITE-6347 Project: Ignite

[jira] [Assigned] (IGNITE-5889) Exception message confused when double cache configuration by some mistake.

[ https://issues.apache.org/jira/browse/IGNITE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-5889: -- Assignee: Ilya Lantukh (was: Alexandr Kuramshin) > Exception message

[jira] [Assigned] (IGNITE-5889) Exception message confused when double cache configuration by some mistake.

[ https://issues.apache.org/jira/browse/IGNITE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-5889: -- Assignee: Alexandr Kuramshin > Exception message confused when double cache

[jira] [Commented] (IGNITE-5889) Exception message confused when double cache configuration by some mistake.

[ https://issues.apache.org/jira/browse/IGNITE-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161175#comment-16161175 ] Alexandr Kuramshin commented on IGNITE-5889: [~v.pyatkov], Actually you won't get an error

[jira] [Commented] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)

[ https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101602#comment-16101602 ] Alexandr Kuramshin commented on IGNITE-4767: Hi, [~dpavlov], Suppressed exceptions will be

[jira] [Created] (IGNITE-5798) Logging Ignite configuration at startup

Alexandr Kuramshin created IGNITE-5798: -- Summary: Logging Ignite configuration at startup Key: IGNITE-5798 URL: https://issues.apache.org/jira/browse/IGNITE-5798 Project: Ignite Issue

[jira] [Commented] (IGNITE-5750) Format of uptime for metrics

[ https://issues.apache.org/jira/browse/IGNITE-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16093424#comment-16093424 ] Alexandr Kuramshin commented on IGNITE-5750: LGFM. Have you made a test or check that uses of

[jira] [Created] (IGNITE-5750) Format of uptime for metrics

Alexandr Kuramshin created IGNITE-5750: -- Summary: Format of uptime for metrics Key: IGNITE-5750 URL: https://issues.apache.org/jira/browse/IGNITE-5750 Project: Ignite Issue Type: Bug

[jira] [Commented] (IGNITE-5026) getOrCreateCaches() hangs if any exception in GridDhtPartitionsExchangeFuture.init()

[ https://issues.apache.org/jira/browse/IGNITE-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039218#comment-16039218 ] Alexandr Kuramshin commented on IGNITE-5026: [~Alexey Kuznetsov], please, look at the branch

[jira] [Assigned] (IGNITE-4496) Review all logging for sensitive data leak

[ https://issues.apache.org/jira/browse/IGNITE-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-4496: -- Assignee: Semen Boikov (was: Alexandr Kuramshin) Fix

[jira] [Assigned] (IGNITE-5251) Some JVM implementations may return null from getClassLoader()

[ https://issues.apache.org/jira/browse/IGNITE-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-5251: -- Assignee: Alexey Dmitriev > Some JVM implementations may return null from

[jira] [Created] (IGNITE-5251) Some JVM implementations may return null from getClassLoader()

Alexandr Kuramshin created IGNITE-5251: -- Summary: Some JVM implementations may return null from getClassLoader() Key: IGNITE-5251 URL: https://issues.apache.org/jira/browse/IGNITE-5251 Project:

[jira] [Assigned] (IGNITE-5227) StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

[ https://issues.apache.org/jira/browse/IGNITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-5227: -- Assignee: Alexandr Kuramshin (was: Alexey Goncharuk) > StackOverflowError in

  1   2   >