[
https://issues.apache.org/jira/browse/IGNITE-28442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28442:
------------------------------------
Description:
Currently, the handshake timeout for the thin client is 0 by default. This
means that the thin client will wait indefinitely for its completion. In some
cases, a network socket may stop responding after sending a HANDSHAKE request,
causing the HANDSHAKE operation to hang for a significant amount of time,
blocking other thin client operations, including the close operation.
It's proposed to always use timeout when waiting for handshake operation to
complete. While it can be set to large default, it will still help prevent
hanging for a significant amount of time.
was:
Currently, the handshake and request timeout for the thin client is 0 by
default. This means that the thin client will wait indefinitely for these
operations to complete. In some cases, a network socket may stop responding
after sending a HANDSHAKE request, causing the HANDSHAKE operation to hang for
a significant amount of time, blocking other thin client operations, including
the close operation.
It's proposed to always use timeouts when waiting for handshake and request
operations to complete. While they can be set to large defaults, it will still
help prevent indefinite hanging.
> [Java Thin Client] Introduce default values for handshake timeout
> -----------------------------------------------------------------
>
> Key: IGNITE-28442
> URL: https://issues.apache.org/jira/browse/IGNITE-28442
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
>
> Currently, the handshake timeout for the thin client is 0 by default. This
> means that the thin client will wait indefinitely for its completion. In some
> cases, a network socket may stop responding after sending a HANDSHAKE
> request, causing the HANDSHAKE operation to hang for a significant amount of
> time, blocking other thin client operations, including the close operation.
> It's proposed to always use timeout when waiting for handshake operation to
> complete. While it can be set to large default, it will still help prevent
> hanging for a significant amount of time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
