[jira] [Updated] (IGNITE-11288) TcpDiscovery deadlock on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: Rootcause is java bug locking on SSLSocketImpl.close() on write lock: //we

[jira] [Updated] (IGNITE-11308) Add soLinger parameter support in TcpDiscoverySpi .NET configuration.

[ https://issues.apache.org/jira/browse/IGNITE-11308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11308: Description: NET client should support TcpDiscoverry.soLinger parameter. > Add soLinger

[jira] [Created] (IGNITE-11308) Add soLinger parameter support in TcpDiscoverySpi .NET configuration.

Pavel Voronkin created IGNITE-11308: --- Summary: Add soLinger parameter support in TcpDiscoverySpi .NET configuration. Key: IGNITE-11308 URL: https://issues.apache.org/jira/browse/IGNITE-11308

[jira] [Commented] (IGNITE-11288) TcpDiscovery locks forever on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767054#comment-16767054 ] Pavel Voronkin commented on IGNITE-11288: - Thanks > TcpDiscovery locks forever on

[jira] [Comment Edited] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created

[ https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768268#comment-16768268 ] Pavel Voronkin edited comment on IGNITE-9113 at 2/14/19 1:51 PM: -

[jira] [Commented] (IGNITE-9113) Allocate memory for a data region when first cache assigned to this region is created

[ https://issues.apache.org/jira/browse/IGNITE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768268#comment-16768268 ] Pavel Voronkin commented on IGNITE-9113: [~NIzhikov] i also observe that persistent(true) is

[jira] [Updated] (IGNITE-11288) TcpDiscovery deadlock on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Summary: TcpDiscovery deadlock on SSLSocket.close(). (was: Missing SO_LINGER in

[jira] [Updated] (IGNITE-11288) TcpDiscovery deadlock on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: Rootcause is we not set SO_TIMEOUT on discovery socket on retry:

[jira] [Updated] (IGNITE-11288) TcpDiscovery deadlock on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: Rootcause is we not set SO_TIMEOUT on discovery socket on retry:

[jira] [Assigned] (IGNITE-11288) TcpDiscovery deadlock on SSLSocket.close().

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-11288: --- Assignee: Pavel Voronkin > TcpDiscovery deadlock on SSLSocket.close(). >

[jira] [Created] (IGNITE-11221) Refactor timeout logic in TcpDiscovery

Pavel Voronkin created IGNITE-11221: --- Summary: Refactor timeout logic in TcpDiscovery Key: IGNITE-11221 URL: https://issues.apache.org/jira/browse/IGNITE-11221 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-6324) Transactional cache data partially available after crash.

[ https://issues.apache.org/jira/browse/IGNITE-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-6324: --- Summary: Transactional cache data partially available after crash. (was: Transactional

[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648.

[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11255: Description: We need to fix:   *

[jira] [Created] (IGNITE-11288) Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi causing SSLSocket.close() deadlock.

Pavel Voronkin created IGNITE-11288: --- Summary: Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi causing SSLSocket.close() deadlock. Key: IGNITE-11288 URL:

[jira] [Updated] (IGNITE-11288) Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi causing SSLSocket.close() deadlock.

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: According to java8 SSLSocketImpl: if (var1.isAlert((byte)0) &&

[jira] [Updated] (IGNITE-11288) Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi causing SSLSocket.close() deadlock.

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: According to java8 SSLSocketImpl: if (var1.isAlert((byte)0) &&

[jira] [Updated] (IGNITE-11288) Missing SO_LINGER in TcpDiscovery and TcpCommunicationSpi causing SSLSocket.close() deadlock.

[ https://issues.apache.org/jira/browse/IGNITE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11288: Description: According to java8 SSLSocketImpl: if (var1.isAlert((byte)0) &&

[jira] [Commented] (IGNITE-11016) RecoveryLastReceivedMessage(NEED_WAIT) fails with "Failed to encrypt data (SSL engine error)".

[ https://issues.apache.org/jira/browse/IGNITE-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750679#comment-16750679 ] Pavel Voronkin commented on IGNITE-11016: - I agree with that we need to add failure detection

[jira] [Updated] (IGNITE-11054) GridNioServer.processWrite() reordered socket.write and onMessageWritten callback.

[ https://issues.apache.org/jira/browse/IGNITE-11054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11054: Description: We have bug in processWrite() SessionWriteRequest.onMessageWritten() is

[jira] [Created] (IGNITE-11054) GridNioServer.processWrite() reordered socket.write and onMessageWritten callback.

Pavel Voronkin created IGNITE-11054: --- Summary: GridNioServer.processWrite() reordered socket.write and onMessageWritten callback. Key: IGNITE-11054 URL: https://issues.apache.org/jira/browse/IGNITE-11054

[jira] [Updated] (IGNITE-11054) GridNioServer.processWrite() reordered socket.write and onMessageWritten callback.

[ https://issues.apache.org/jira/browse/IGNITE-11054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11054: Description: We have bug in processWrite()     > GridNioServer.processWrite()

[jira] [Resolved] (IGNITE-11026) Support TcpCommunicationSpi.NeedWaitDelay, TcpCommunicationSpi.MaxNeedWaitDelay in .NET.

[ https://issues.apache.org/jira/browse/IGNITE-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin resolved IGNITE-11026. - Resolution: Won't Fix We decided no to introduce new parameters. > Support

[jira] [Updated] (IGNITE-11016) RecoveryLastReceivedMessage(NEED_WAIT) fails with "Failed to encrypt data (SSL engine error)".

[ https://issues.apache.org/jira/browse/IGNITE-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11016: Ignite Flags: (was: Docs Required) > RecoveryLastReceivedMessage(NEED_WAIT) fails with

[jira] [Updated] (IGNITE-11016) RecoveryLastReceivedMessage(NEED_WAIT) fails with "Failed to encrypt data (SSL engine error)".

[ https://issues.apache.org/jira/browse/IGNITE-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11016: Fix Version/s: 2.8 > RecoveryLastReceivedMessage(NEED_WAIT) fails with "Failed to

[jira] [Created] (IGNITE-11061) Сopyright still points out 2018

Pavel Voronkin created IGNITE-11061: --- Summary: Сopyright still points out 2018 Key: IGNITE-11061 URL: https://issues.apache.org/jira/browse/IGNITE-11061 Project: Ignite Issue Type: Bug

[jira] [Resolved] (IGNITE-11061) Сopyright still points out 2018

[ https://issues.apache.org/jira/browse/IGNITE-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin resolved IGNITE-11061. - Resolution: Invalid > Сopyright still points out 2018 >

[jira] [Comment Edited] (IGNITE-11061) Сopyright still points out 2018

[ https://issues.apache.org/jira/browse/IGNITE-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751194#comment-16751194 ] Pavel Voronkin edited comment on IGNITE-11061 at 1/24/19 2:38 PM: --

[jira] [Closed] (IGNITE-11061) Сopyright still points out 2018

[ https://issues.apache.org/jira/browse/IGNITE-11061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin closed IGNITE-11061. --- Ignite Flags: (was: Docs Required) Created ticket by mistake > Сopyright still points

[jira] [Updated] (IGNITE-11172) While handling duplicated connections we got exception on writing message to stale connection.

[ https://issues.apache.org/jira/browse/IGNITE-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11172: Summary: While handling duplicated connections we got exception on writing message to

[jira] [Created] (IGNITE-11172) On receiving duplicated connections we got exception.

Pavel Voronkin created IGNITE-11172: --- Summary: On receiving duplicated connections we got exception. Key: IGNITE-11172 URL: https://issues.apache.org/jira/browse/IGNITE-11172 Project: Ignite

[jira] [Updated] (IGNITE-11172) On receiving duplicated connections we got exception on writing message on stale connections.

[ https://issues.apache.org/jira/browse/IGNITE-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11172: Summary: On receiving duplicated connections we got exception on writing message on

[jira] [Resolved] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.

[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin resolved IGNITE-11201. - Resolution: Duplicate > ConnectorConfiguration and TransactionConfiguration toString

[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.

[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Description: Ignite configuration prints on startup, but ConnectorConfiguration and

[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented.

[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Summary: ConnectorConfiguration and TransactionConfiguration toString is not properly

[jira] [Created] (IGNITE-11201) ConnectorConfdiguration and TransactionConfiguration toString is not properly implemented.

Pavel Voronkin created IGNITE-11201: --- Summary: ConnectorConfdiguration and TransactionConfiguration toString is not properly implemented. Key: IGNITE-11201 URL:

[jira] [Updated] (IGNITE-11201) ConnectorConfiguration and TransactionConfiguration toString is not properly implemented

[ https://issues.apache.org/jira/browse/IGNITE-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11201: Summary: ConnectorConfiguration and TransactionConfiguration toString is not properly

[jira] [Assigned] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.

[ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-7648: -- Assignee: Pavel Voronkin (was: Alexei Scherbakov) > Fix

[jira] [Updated] (IGNITE-11126) Rework TcpCommunicationSpi.createShmemClient failure detection logic.

[ https://issues.apache.org/jira/browse/IGNITE-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11126: Description: We need to rework  > Rework TcpCommunicationSpi.createShmemClient failure

[jira] [Updated] (IGNITE-11126) Rework TcpCommunicationSpi.createShmemClient failure detection logic.

[ https://issues.apache.org/jira/browse/IGNITE-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11126: Description: We need to rework createShmemClient() logic, to support failure

[jira] [Created] (IGNITE-11126) Rework TcpCommunicationSpi.createShmemClient failure detection logic.

Pavel Voronkin created IGNITE-11126: --- Summary: Rework TcpCommunicationSpi.createShmemClient failure detection logic. Key: IGNITE-11126 URL: https://issues.apache.org/jira/browse/IGNITE-11126

[jira] [Assigned] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel

[ https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin reassigned IGNITE-10876: --- Assignee: Pavel Voronkin > "Affinity changes (coordinator) applied" can be

<    1   2   3