Frequent "CONNECTION_FAILURE" Error in QuickSight – I/O Error While Sending to Backend

Question & Answer
, ,
1

I’m frequently encountering the following error while trying to refresh my dataset in Amazon QuickSight:

Error type: CONNECTION_FAILURE
Details: “An I/O error occurred while sending to the backend.”

This seems to happen randomly, even when the data source is accessible otherwise. I’ve verified the database credentials and network access, and the data source test connection succeeds in the QuickSight console.

  • What could be causing this recurring issue?
  • Are there any best practices to prevent such backend I/O failures in QuickSight?
  • Does QuickSight provide more detailed logs for this ingestion failure?

Thanks in advance for any guidance or troubleshooting tips.

1 Like
2

Hello @agni_04, what is the database that you are connecting to in QuickSight? Also, even though the errors are seemingly random, is there anything similar between the instances? Is the error happening at a similar time, weekday, or day of the month? Maybe there is something scheduled within the database itself that is causing the error to happen in QuickSight.

Alternatively, from the QuickSight side, what do the refresh times look like for the datasets and is there ever a scenario where you are running multiple dataset refreshes at once?

With some more information about the issue, I can help guide you towards a solution. Thank you!

3

I am using postgres for connection. and the failure part is random.

4

Hi @agni_04, is your database located in the same account with QuickSight? If they are in different accounts then incorrect peering could cause random connection issues. Only a person with admin access to both accounts can resolve an issue like this.

1 Like
5

Hello @agni_04, does the previous comment describe the situation you are facing at all? Is the postgres database in a different account than QuickSight? Maybe if you describe some more information about how you set up the connection between the 2, we could figure out a resolution to the issue.

If we do not hear back from you in 3 days, we will close out this topic. Thank you!

6

Hello @agni_04, since we have not heard back from you with any follow-up questions, I will close out this topic. If you need further assistance, please post a new question in the community and include a link to this topic to provide relevant information. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. Thank you!