awslabs / awslabs/amazon-redshift-utils
How to avoid timeouts on Automation Module
Open
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Given lambda's 15 minute execution limit, how can i use the automation module if running vacuum/analyze on a single large table can take over 45 minutes in some cases?
Contributor guide
Research direction
Start by reading the Automation Module's Lambda entry point and the workflow that runs vacuum/analyze on a single large table. Determine how the 15-minute Lambda limit affects the reported use case and what an acceptable way to complete work exceeding 45 minutes would look like; the issue does not define a specific implementation or completion test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100