Unable to modify Redshift Zero-ETL database. Getting "No response received from connection manager"

0

I have deployed a Zero-ETL integration from a Postgres RDS to my Redshift Serverless data warehouse.

I discovered an issue while trying to reduce the refresh_interval. Running this command: ALTER DATABASE trading_app_zetl INTEGRATION SET REFRESH_INTERVAL 432000;

ERROR: Cannot refresh 3ea8a251-e263-44d8-a253-b3dc9256f5af: UnknownFailure: No response received from connection manager: {"failurereason":12} [ErrorId: 1-681aaed8-26dabd5d47eaaae76dc37288]

I get the same error message when trying to resync the tables with this command: ALTER DATABASE trading_app_zetl INTEGRATION REFRESH ALL TABLES;

If I try to query one of the ZETL tables I get this error message: ERROR: Zero-ETL database is not available for querying right now. See SVV_INTEGRATION for more information. [ErrorId: 1-681ab088-7503b19b3cdb43f75cef6216]

I then noticed by looking at the svv_integration table that I have no refresh rate set and many other parameters that I would expect to be there are now missing. I have also noticed that none of the tables are updating. This is perplexing because a few days ago the integration was working fine. It seems to have broken on it's own and there's no clear way to fix this without having to delete the whole thing and start over.

Is there a way to fix this without completely recreating the warehouse? Is there a way to avoid this occurring in the future?

1 Answer
-1

Hello,

I understand you are experiencing issues with your Zero-ETL integration between Postgres RDS and Redshift serverless, where the integration has stopped working unexpectedly. Specifically, you're unable to modify the refresh interval, cannot resync tables, and cannot query ZETL tables. The integration settings appear to be missing from the svv_integration table, and tables are no longer updating, despite the integration working correctly a few days ago.

Firstly, the error "UnknownFailure: No response received from connection manager: {"failurereason":12}" may be due to cluster-level issues. Therefore, it's necessary to examine the cluster parameters.

Secondly, the "Zero-ETL database is not available for querying right now" error usually occurs when zero-ETL integration becomes stuck in a recurring resync state. During this time, queries may not process properly.

Recommendations:

Check the current integration status: SELECT * FROM SVV_INTEGRATION WHERE integration_name = '<your_integration_name>'; If you see the state as CATCHING_UP or ERROR, that means the integration is still trying to sync

To help you further with troubleshooting regarding your error, please open a support case with AWS using the following link:

[+] https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

[+] https://support.console.aws.amazon.com/support/home#/case/create

References:

[+] https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_INTEGRATION.html

[+] https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.describing.html

I hope above information is helpful.

profile picture
answered 12 days ago
AWS
SUPPORT ENGINEER
revised 10 days ago
AWS
SUPPORT ENGINEER
revised 10 days ago
AWS
SUPPORT ENGINEER
revised 10 days ago
  • Nothing would have changed regarding network configuration or IAM roles from the time that it was working and the time that it broke. Would be useful if there was a way to get a more descriptive error message. Most of what is posted is above is from the documentation which I have already gone through. This error does not seem to be mentioned anywhere in the available AWS docs on ZETL.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions