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

Pavel Tupitsyn commented on IGNITE-20573:
-----------------------------------------

Merged to main: a5a8b835ca149d4d5141c91248d3c664fdf1c61e

> Java thin 3.0: Introduce configurable operation timeout
> -------------------------------------------------------
>
>                 Key: IGNITE-20573
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20573
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently we have *IgniteClientConfiguration.connectTimeout* which is only 
> used for handshake and heartbeats, which means we use it to check if the 
> server and network are responsive.
> However, other operations (put, get, compute, etc) can take any amount of 
> time.
> Investigate if a general operation timeout can be useful.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to