You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by av...@apache.org on 2020/11/09 11:25:21 UTC
[ignite] branch master updated: IGNITE-13662 : Describe soLinger
setting in TCP Discovery and SSL issues. (#8430)
This is an automated email from the ASF dual-hosted git repository.
av pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/master by this push:
new 6b14606 IGNITE-13662 : Describe soLinger setting in TCP Discovery and SSL issues. (#8430)
6b14606 is described below
commit 6b14606f227bd11f4a876f28cc023d7358eb7788
Author: Vladsz83 <vl...@gmail.com>
AuthorDate: Mon Nov 9 14:24:52 2020 +0300
IGNITE-13662 : Describe soLinger setting in TCP Discovery and SSL issues. (#8430)
---
docs/_docs/clustering/network-configuration.adoc | 1 +
docs/_docs/security/ssl-tls.adoc | 6 ++++++
2 files changed, 7 insertions(+)
diff --git a/docs/_docs/clustering/network-configuration.adoc b/docs/_docs/clustering/network-configuration.adoc
index d656b0c..9d9c904 100644
--- a/docs/_docs/clustering/network-configuration.adoc
+++ b/docs/_docs/clustering/network-configuration.adoc
@@ -56,6 +56,7 @@ You can find the complete list of properties in the javadoc:org.apache.ignite.sp
| `localPort` | The port that the node binds to. If set to a non-default value, other cluster nodes must know this port to be able to discover the node. | `47500`
| `localPortRange`| If the `localPort` is busy, the node attempts to bind to the next port (incremented by 1) and continues this process until it finds a free port. The `localPortRange` property defines the number of ports the node will try (starting from `localPort`).
| `100`
+| `soLinger`| Setting linger-on-close can help with socket deadlocks of SSL issues like JDK-8219658. But costs longer detection of node failure. | `0`
| `reconnectCount` | The number of times the node tries to (re)establish connection to another node. |`10`
| `networkTimeout` | The maximum network timeout in milliseconds for network operations. |`5000`
| `socketTimeout` | The socket operations timeout. This timeout is used to limit connection time and write-to-socket time. |`5000`
diff --git a/docs/_docs/security/ssl-tls.adoc b/docs/_docs/security/ssl-tls.adoc
index bf5a90e..a5edc0b 100644
--- a/docs/_docs/security/ssl-tls.adoc
+++ b/docs/_docs/security/ssl-tls.adoc
@@ -32,6 +32,12 @@ To enable SSL/TLS for cluster nodes, configure an `SSLContext` factory in the no
You can use the `org.apache.ignite.ssl.SslContextFactory`, which is the default factory that uses a configurable keystore to initialize the SSL context.
//You can also implement your own `SSLContext` factory.
+[NOTE]
+====
+There are known socket deadlock issue on various JRE when SSL enabled. Example: JDK-8219658. It is recommended to use
+the latest versions of your JRE. Or you can enable linger options like `TcpDiscoverySpi.soLinger`.
+====
+
Below is an example of `SslContextFactory` configuration:
[tabs]