-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(cli): cdk gc
for S3 gets stuck / runs indefinitely
#33441
Comments
Linking this as it's related #32742 |
Thank you for reporting this issue with the CDK garbage collection command. Since this is a new experimental feature (marked with --unstable flag), your feedback is valuable. Please note that the garbage collection feature is still experimental (hence the --unstable flag). We're actively working on improving its reliability and performance. |
Yep, I saw the other bug, but since this happened for S3 (the other ticket is for ECR), I filed a separate issue. Thanks! |
This works now! Thanks |
Comments on closed issues and PRs are hard for our team to see. |
Describe the bug
When running:
> yarn cdk gc --unstable gc --type=s3 --rollback-buffer-days=30 --created-buffer-days=10 --verbose
The progress seems to get stuck at 97.92% and doesn't seem to progress afterward. I've let this run for 12 hours and it never proceeds.
Regression Issue
Last Known Working CDK Version
N/A
Expected Behavior
I expect the progress to increase somewhat linearly and eventually complete.
Current Behavior
It seems to hang forever.
Reproduction Steps
Unfortunately, it's not possible for me to provide a repro case for this, since it's dependent on my account stacks, etc. However, here are the logs, which might provide some details:
logs.txt
I keep seeing
Before the apparent loop begins again.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.178.2 (build 89c49cc)
Framework Version
No response
Node.js Version
v20.18.0
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: