You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To prevent a user from submitting a query that can run arbitrarily long, we now provide three configurations of timeout, namely
Gremlin timeout: Corresponding to the official timeout parameters of Tinkerpop
RPC timeout: Compiler submits a job to pegasus via RPC. Thus, RPC timeout measures timeout regarding the timeout between compiler submitting a join and pegasus returning the first batch of results.
Pegasus timeout: A Pegasus internal configuration of timeout from running a job.
These timeout configurations are very confused, and are not suitable for being delegated to users directly.
Thus, can we unify these three timeout into one single query timeout, and make it the only configuration to the users (and automatically configure the above three timeouts).
The text was updated successfully, but these errors were encountered:
<!--
Thanks for your contribution! please review
https://github.com/alibaba/GraphScope/blob/main/CONTRIBUTING.md before
opening an issue.
-->
## What do these changes do?
Unify gremlin timeout configurations. By this pr, the console will
output like this if gremlin query execution timeout is set to 2000ms.
<img width="1627" alt="image"
src="https://github.com/alibaba/GraphScope/assets/22363306/922d0702-1a7f-4904-814c-0e9ebd6e7102">
Timeout can be set by two ways:
1. system configuration, set `query.execution.timeout.ms: 2000` in
`conf/ir.compiler.properties`
2. set per query in gremlin query `g.with(ARGS_EVAL_TIMEOUT, 2000).V()`
or `g.with(Tokens.ARGS_EVAL_TIMEOUT, 2000).V()`. if timeout value is of
long type, suffix with 'L'
<!-- Please give a short brief about these changes. -->
## Related issue number
<!-- Are there any issues opened that will be resolved by merging this
change? -->
Fixes#2854
---------
Co-authored-by: Longbin Lai <longbin.lailb@alibaba-inc.com>
To prevent a user from submitting a query that can run arbitrarily long, we now provide three configurations of timeout, namely
These timeout configurations are very confused, and are not suitable for being delegated to users directly.
Thus, can we unify these three timeout into one single query timeout, and make it the only configuration to the users (and automatically configure the above three timeouts).
The text was updated successfully, but these errors were encountered: