[ 
https://issues.apache.org/jira/browse/IGNITE-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145900#comment-18145900
 ] 

Ignite TC Bot commented on IGNITE-20973:
----------------------------------------

The required documentation is merged in [PR 
#13840|https://github.com/apache/ignite/pull/13840] (commit 
[b9d4d940|https://github.com/apache/ignite/commit/b9d4d94006c233ac3aa5d1046d4378f08fbba8bc]).
 It documents the separate Java thin-client handshake and request timeouts. 
Docs Required has been cleared; Release Notes Required is retained.

> Split java thin client timeout to handshake and request timeouts
> ----------------------------------------------------------------
>
>                 Key: IGNITE-20973
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20973
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 2.16, 2.17
>            Reporter: Egor Fomin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: 2.18-review, ise
>             Fix For: 2.18
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> Ignite thin client currently uses the same timeout value for request timeout 
> and connection timeout. 
> Connection timeout should be small enough(several seconds) while request 
> timeout should be able to handle long running requests. This makes Ignite 
> timeout unusable.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to