- Newest
- Most votes
- Most comments
Hello,
please try this solution it will be helpful for you.
If your Amazon Redshift Serverless endpoint is stuck in the "Modifying" status for hours after changing the maximum query execution time, this behavior is unusual and indicates a potential issue.
check the AWS Health Dashboard to see if there are any ongoing service disruptions or maintenance events in your region.
review the CloudWatch logs for any errors or warnings related to your Redshift Serverless endpoint.
Ensure there are no active or long-running queries that might be blocking the modification.
If possible try canceling the current modification and reapplying the configuration change via the AWS Management Console or CLI.
please look at below AWS Document link.
https://docs.aws.amazon.com/redshift/latest/gsg/new-user-serverless.html
Relevant content
- asked 10 months ago
- asked 5 years ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks for your quick response! It is still in Modifying status have almost 24 hours of the change. I've checked the logs and nothing seems to be wrong or at least there are no errors. No disruptions or maintenance is currently happening on my region. I'm not able to check if there are long queries running since I'm not able to connect to the Query Editor due to the Modifying status. Is there anything else I can do? I cannot even able to delete it.