You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When client apps leak queues, i.e. they declare queues but won't (always) delete them, queue TTL can be a handy feature to auto delete queues that haven't been "used".
Classic queues and quorum queues support queue TTL where "used" means having online consumers.
Streams do not support queue TTL.
Describe the solution you'd like
Each chunk stores a timestamp.
Therefore, by reading the last chunk header of a given stream, a CLI tool can output "last write" activity to a Stream.
Such a command would be helpful for platform teams do identify potential orphaned Streams.
(Instead of a separate CLI command, it could also be an additional column in an existing CLI command or an HTTP API endpoint.)
Note that this timestamp denotes only "last write", i.e. publishes or consumers writing their offset tracking. It won't include consumers without offset tracking.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When client apps leak queues, i.e. they declare queues but won't (always) delete them, queue TTL can be a handy feature to auto delete queues that haven't been "used".
Classic queues and quorum queues support queue TTL where "used" means having online consumers.
Streams do not support queue TTL.
Describe the solution you'd like
Each chunk stores a timestamp.
Therefore, by reading the last chunk header of a given stream, a CLI tool can output "last write" activity to a Stream.
Such a command would be helpful for platform teams do identify potential orphaned Streams.
(Instead of a separate CLI command, it could also be an additional column in an existing CLI command or an HTTP API endpoint.)
Note that this timestamp denotes only "last write", i.e. publishes or consumers writing their offset tracking. It won't include consumers without offset tracking.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: