[
https://issues.apache.org/jira/browse/IGNITE-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057795#comment-18057795
]
Ignite TC Bot commented on IGNITE-20973:
----------------------------------------
{panel:title=Branch: [pull/12710/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12710/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=8854704]]
* {color:#013220}ClientTestSuite:
TimeoutTest.testConnectionTimeoutIndependentOfRequest - PASSED{color}
* {color:#013220}ClientTestSuite:
TimeoutTest.testRequestTimeoutIndependentOfConnection - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8850631&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Time Spent: 4h 20m
> 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
(v8.20.10#820010)
