Who is this feature for?
Ops
What problem are they facing today?
When a Topic with a large amount of data shortens the TTL or is deleted, the concurrent deletion of a large number of Objects will cause S3 to be rate-limited.
Why is solving this impactful?
Proposed solution
Control deletion concurrency:
- For ordinary Objects, control 1000 per batch with a total of 8 concurrencies.
- For Composite Objects, DELETE / DEEP_DELETE ?
Additional notes
No response