Hello, There is a dataset scheduled to run every hour which has not got error messages in the last 3 months. however, recently I start getting to the below: anyone knows how to resolve the issue ?
there is no change to the query or running schedule. sometimes, manually re-run fails and sometimes re-run works. it works perfectly in athena. This error we only got from QS:
[Simba]AthenaJDBC An error has been thrown from the AWS Athena client. Amazon Athena experienced an internal error while executing this query. Please try submitting the query again and if the issue reoccurs, contact AWS support for further assistance. We apologize for the inconvenience. [Execution ID: 3d046ba4-0911-418f-a29c-02e9f065790f]
Hi @JLLLL - For detail analysis of this kind of issues, we need logs and there is not much details in the message. Please raise a ticket to AWS Customer support team and provide the execution ID so that they can track it. To raise the request, please follow the link - Creating support cases and case management - AWS Support
Hello @JLLLL, I have a few questions for you about this issue. When you refresh, are you running an incrementel refresh or a full refresh? Also, are multiple dataset refreshes scheduled to run at the same time?
You could be running into a possible Athena timeout issue if many refreshes are happening at once. What is the average refresh time you are getting when the refresh is successful?
When you refresh, are you running an incrementel refresh or a full refresh? Also, are multiple dataset refreshes scheduled to run at the same time?
it is always 00:06 per hour
full refresh
no multiple dataset run at that time
You could be running into a possible Athena timeout issue if many refreshes are happening at once. What is the average refresh time you are getting when the refresh is successful?
it is always between 10-13mins.
and after the failure what I mentioned above, everytime I re-refresh only last 3mins and the outcome is reduced significantly (which should not produce such small number of rows).
strange thing is that from 9/28, it comes back to 10-12mins and outcome is back to normal
Hello @JLLLL, so it is back to functioning as expected? I would say if it starts happening again, it would probably be best to follow @Sanjeeb2022’s guidance in regards to opening an internal ticket. With the responses you sent me, I am leaning towards this issue being a bug not a problem with your refreshes or dataset. Also, if something similar pops up again, feel free to post a new topic in the community with some Screenshots and we can dig into it some more. Good luck!