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 2017/07/12 17:33:00 UTC

[jira] [Closed] (TINKERPOP-1714) Gremlin Server scriptEvaluationTimeout should take into account request arrival time

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

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

> Gremlin Server scriptEvaluationTimeout should take into account request arrival time
> ------------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-1714
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1714
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.2.5
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>             Fix For: 3.2.6
>
>
> Currently the {{GremlinExecutor}} tries to timeout a eval after the job has started execution in the thread pool, when the likely user expectation is that it begin the timeout testing from the time the eval was invoked. While the current approach works (though not in line with what users probably are thinking is happening), an overloaded server using {{GremlinExecutor}} will have a more difficult time clearing the queue of jobs (if it can clear it at all). 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)