You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/05/03 10:48:00 UTC

[jira] [Closed] (TINKERPOP-2203) Bind the console timeout to the request timeout

     [ https://issues.apache.org/jira/browse/TINKERPOP-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-2203.
---------------------------------------
    Resolution: Done

> Bind the console timeout to the request timeout
> -----------------------------------------------
>
>                 Key: TINKERPOP-2203
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2203
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: console
>    Affects Versions: 3.3.6
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>             Fix For: 3.4.2
>
>
> {{:remote config timeout x}} sets a client side timeout but doesn't override the timeout on the server so if the timeout on the client is shorter than what's on the server then the server will keep processing even though the client is long done waiting. On the flip side, if the server is shorter than the client it will timeout sooner than expected. 
> In 3.4.0 we introduced some changes to the driver API which would make this work better, allowing the timeout to be easily set from the client side. Simply need to use that to make the server aware of the timeout the client is using.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)