[jira] [Commented] (IGNITE-11974) infinite loop and 100% cpu in GridDhtPartitionsEvictor: Eviction in progress ...

[ https://issues.apache.org/jira/browse/IGNITE-11974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185283#comment-17185283 ] Igor Kamyshnikov commented on IGNITE-11974: --- Hi [~Arroyo], Unfortunately, we

[jira] [Comment Edited] (IGNITE-7913) Current implementation of Internal Diagnostics may cause OOM on server nodes.

[ https://issues.apache.org/jira/browse/IGNITE-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024440#comment-17024440 ] Igor Kamyshnikov edited comment on IGNITE-7913 at 1/27/20 3:43 PM: ---

[jira] [Commented] (IGNITE-7913) Current implementation of Internal Diagnostics may cause OOM on server nodes.

[ https://issues.apache.org/jira/browse/IGNITE-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024440#comment-17024440 ] Igor Kamyshnikov commented on IGNITE-7913: -- The same on Ignite 2.7.6. At least

[jira] [Updated] (IGNITE-12335) IgniteDataStreamer flush cannot be really interrupted

[ https://issues.apache.org/jira/browse/IGNITE-12335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-12335: -- Description: IgniteDataStreamer flush operation cannot be interrupted: 1) datastreame

[jira] [Created] (IGNITE-12335) IgniteDataStreamer flush cannot be really interrupted

Igor Kamyshnikov created IGNITE-12335: - Summary: IgniteDataStreamer flush cannot be really interrupted Key: IGNITE-12335 URL: https://issues.apache.org/jira/browse/IGNITE-12335 Project: Ignite

[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

[ https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906975#comment-16906975 ] Igor Kamyshnikov commented on IGNITE-7791: -- Added for history indexing purposes

[jira] [Updated] (IGNITE-11974) infinite loop and 100% cpu in GridDhtPartitionsEvictor: Eviction in progress ...

[ https://issues.apache.org/jira/browse/IGNITE-11974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11974: -- Attachment: server-node-restarts-1.png > infinite loop and 100% cpu in GridDhtPartiti

[jira] [Updated] (IGNITE-11974) infinite loop and 100% cpu in GridDhtPartitionsEvictor: Eviction in progress ...

[ https://issues.apache.org/jira/browse/IGNITE-11974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11974: -- Description: Note: RCA was not done: Sometimes ignite server nodes fall into infinit

[jira] [Created] (IGNITE-11974) infinite loop and 100% cpu in GridDhtPartitionsEvictor: Eviction in progress ...

Igor Kamyshnikov created IGNITE-11974: - Summary: infinite loop and 100% cpu in GridDhtPartitionsEvictor: Eviction in progress ... Key: IGNITE-11974 URL: https://issues.apache.org/jira/browse/IGNITE-11974

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Attachment: PrimaryBackupTest.java > 3rd-party persistence: Backup and primary partit

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Description: 1) run 2 ignite servers on different machines (this is important because

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Description: 1) run 2 ignite servers on different machines (this is important because

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Attachment: (was: PrimaryBackupTest.java) > 3rd-party persistence: Backup and pri

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Attachment: PrimaryBackupTest.java > 3rd-party persistence: Backup and primary partit

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavi

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Summary: 3rd-party persistence: Backup and primary partitions data differ after a sin

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore and Ig

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Summary: 3rd-party persistence: Backup and primary partitions data differ after a sin

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavi

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Description: 1) run 2 ignite servers on different machines (this is important because

[jira] [Updated] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavi

[ https://issues.apache.org/jira/browse/IGNITE-11296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-11296: -- Description: 1) run 2 ignite servers on different machines (this is important because

[jira] [Created] (IGNITE-11296) 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavi

Igor Kamyshnikov created IGNITE-11296: - Summary: 3rd-party persistence: Backup and primary partitions data differ after a single IgniteCache.get that loaded data from the persistent store which breaks skipStore behavior Key:

[jira] [Updated] (IGNITE-10469) TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity

[ https://issues.apache.org/jira/browse/IGNITE-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-10469: -- Attachment: 2.6.0.txt > TcpCommunicationSpi does not break tcp connection after IdleC

[jira] [Updated] (IGNITE-10469) TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity

[ https://issues.apache.org/jira/browse/IGNITE-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kamyshnikov updated IGNITE-10469: -- Description: TcpCommunicationSpi does not close TCP connections after they have been

[jira] [Created] (IGNITE-10469) TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity

Igor Kamyshnikov created IGNITE-10469: - Summary: TcpCommunicationSpi does not break tcp connection after IdleConnectionTimeout seconds of inactivity Key: IGNITE-10469 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (IGNITE-8788) Getting NullPointerException during commit into cassandra, after reconnecting to ignite server

[ https://issues.apache.org/jira/browse/IGNITE-8788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632961#comment-16632961 ] Igor Kamyshnikov commented on IGNITE-8788: -- There is one other aspect of this i