Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Internal timeout not configurable with connector athena-neptune #2132

Open
swcloudgenie opened this issue Aug 2, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@swcloudgenie
Copy link

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:

  1. Deploy a connector with 900 second timeout that is connected to a data set with at least 1,000,000 vertices
  2. Run a general query that would return 1,000,000 vertices, but use LIMIT 10 in the Athena query
  3. 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):

  • Version: 2024.25.1
  • Name neptune
  • Athena Query IDs [if applicable]

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?

@swcloudgenie swcloudgenie added the bug Something isn't working label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant