garbage collection doesn't work well

[DavidHe1127]

Hey friends

I try to run gc command against my asset bucket ~476.8mb. It's reporting progress correctly at the beginning. However, it's making no progress and stuck forever when it's nearly finishing scanning & tagging all assets - see logs below. Does anyone have experience with this command? I don't find much information about people using it.

[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.
[99.33%] 2649 files scanned: 2646 assets (475.56 MiB) tagged, 0 assets (0.00 MiB) deleted.

The command I run:

cdk gc aws://1234567891011/us-east-1 --unstable=gc --type=s3 --rollback-buffer-days=90 --created-buffer-days=30

cdk cli version:

aws-cdk@2.177.0

[DavidHe1127]

Bump it to draw some attentions

[DavidHe1127]

Seems the hang is now resolved with 2.1003.0. Close it for now.