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
Describe the bug
Even if I set the Lambda timeout to the maximum of 900 seconds, I get an internal TimeLimitExceededException.
To Reproduce
Steps to reproduce the behavior:
Deploy a connector with 900 second timeout that is connected to a data set with at least 1,000,000 vertices
Run a general query that would return 1,000,000 vertices, but use LIMIT 10 in the Athena query
After about 60 seconds, you will see a TimeLimitExceededException error.
Expected behavior
If the Lambda timeout is configured to be 900 seconds, I would expect the internal client to also allow for up to 900 seconds for a query to complete.
Screenshots / Exceptions / Errors
Full Error Output:
GENERIC_USER_ERROR: Encountered an exception[java.util.concurrent.CompletionException] from your LambdaFunction[arn:aws:lambda:us-east-2:766014253713:function:asset-library-catalog] executed in context[S3SpillLocation{bucket='aws-athena-query-results-us-east-2-766014253713', key='athena-neptune-spill/0b2ba32d-c233-4db3-83d5-7c0c639f4485/0d3219a4-09af-422b-9ccb-e2b093203cca', directory=true}] with message[org.apache.tinkerpop.gremlin.driver.exception.ResponseException: {"detailedMessage":"A timeout occurred within the script during evaluation.","code":"TimeLimitExceededException","requestId":"260b6287-321d-4e1d-b2f4-9c4094a680c5"}]
Connector Details (please complete the following information):
Describe the bug
Even if I set the Lambda timeout to the maximum of 900 seconds, I get an internal
TimeLimitExceededException
.To Reproduce
Steps to reproduce the behavior:
LIMIT 10
in the Athena queryTimeLimitExceededException
error.Expected behavior
If the Lambda timeout is configured to be 900 seconds, I would expect the internal client to also allow for up to 900 seconds for a query to complete.
Screenshots / Exceptions / Errors
Full Error Output:
Connector Details (please complete the following information):
Additional context
The error is being thrown from
org.apache.tinkerpop.gremlin.driver
In the engine builder, there is a timeout option https://tinkerpop.apache.org/javadocs/3.3.5/full/org/apache/tinkerpop/gremlin/groovy/engine/GremlinExecutor.Builder.html#scriptEvaluationTimeout-long-
Maybe this can be set according to the lambda timeout configuration? Or separately via an environment variable?
The text was updated successfully, but these errors were encountered: