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
Who is this for and what problem do they have today?
In a transaction heavy environment, kafka_internal/tx tends to grow and eats the disk space.
What are the success criteria?
Support TS for the internal topics
Make the topic conf live updatable
Why is solving this problem impactful?
If we support Tiered Storage for the internal topics, it will save the disk space much. Besides, having an ability being able to live-update the topic properties helps operations in the field. Currently we have a cluster wide config transaction_coordinator_delete_retention_ms but it applies only upon the topic creation.
Additional notes
The text was updated successfully, but these errors were encountered:
Who is this for and what problem do they have today?
In a transaction heavy environment,
kafka_internal/tx
tends to grow and eats the disk space.What are the success criteria?
Why is solving this problem impactful?
If we support Tiered Storage for the internal topics, it will save the disk space much. Besides, having an ability being able to live-update the topic properties helps operations in the field. Currently we have a cluster wide config
transaction_coordinator_delete_retention_ms
but it applies only upon the topic creation.Additional notes
The text was updated successfully, but these errors were encountered: