[
https://issues.apache.org/jira/browse/IGNITE-28442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072073#comment-18072073
]
Ignite TC Bot commented on IGNITE-28442:
----------------------------------------
{panel:title=Branch: [pull/12993/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12993/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8991864&buildTypeId=IgniteTests24Java8_RunAll]
> [Java Thin Client] Introduce default values for handshake and request timeouts
> ------------------------------------------------------------------------------
>
> 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
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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.
> The same situation for the operation request timeout.
> It is proposed to set
> handshake timeout to 10 seconds
> request timeout to 60 seconds
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
