Quicksight Datasets are failing more often with ‘SOURCE_RESOURCE_LIMIT_EXCEEDED’ error

Q&A
, ,
1

We are using Quick Sight extensively for our reporting use cases. In recent past (last 1 Month) we have seen increase in error during SPICE ingestion and more often its related with SOURCE_RESOURCE_LIMIT_EXCEEDED error.
We are using Athena as back-end Datasource.
We wanted to understand about this error in particular and any way we can avoid it.
Also one more thing we have seen that Ingestion auto-triggers after sometime if it fails with SOURCE_RESOURCE_LIMIT_EXCEEDED error, so its not blocking us however if in case it gets retried automatically then is there is a way to suppress notifications for this specific error type only asking as it increases effort for our engineers.

2

Hi @sachaa - Thanks for posting the question. I do not think auto retry option is available to refresh SPICE in case of error happened. User needs to retry manually. However did you find the root cause of the issue. From error it looks like Athena is highly utilized or trying access huge amount of data. Not sure about your athena set up but can you please raise a ticket to AWS Customer support team to understand the root cause of this problem. This way you can fix the issue in first place.

Regards - Sanjeeb

3

Thanks for the reply @Sanjeeb2022 - So as per error it seems to be associated with our Data Source (which is Athena). we are looking into it separately , however what we have seen that in such cases there is an automatic retry on Quicksight end, where we see a new Ingestion getting created after a gap of ~5 Mins. So we were curious that if Quicksight has automatic retry as default behavior. because if that’s the case then we can look into setting up some mechanism for our monitoring process, but if not then we have to deep dive further in our code, since we are triggering ingestion programmatically.

4

Hi @sachaa - Possibly you are correct. To understand default behavior it is better to submit a ticket to AWS Customer support team and have a discussion with them. To raise the ticket, please follow the below link - Creating support cases and case management - AWS Support

Regards - Sanjeeb