Skip to content
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

Broker-side cleanup.policy should be DEFAULT_CONFIG, not DYNAMIC_TOPIC_CONFIG #2225

Closed
twmb opened this issue Sep 3, 2021 · 2 comments · Fixed by #17456
Closed

Broker-side cleanup.policy should be DEFAULT_CONFIG, not DYNAMIC_TOPIC_CONFIG #2225

twmb opened this issue Sep 3, 2021 · 2 comments · Fixed by #17456
Assignees
Labels
area/kafka kind/bug Something isn't working

Comments

@twmb
Copy link
Contributor

twmb commented Sep 3, 2021

DYNAMIC_TOPIC_CONFIG is meant for when the default is changed. If I create a topic without a cleanup policy, the default cleanup policy is as configured on the broker (for me, cleanup.policy=delete). Describing a topic's configs shows:

cleanup.policy          delete      DYNAMIC_TOPIC_CONFIG

when it should show

cleanup.policy                           delete               DEFAULT_CONFIG

Also related to #2176, in a way.

JIRA Link: CORE-727

@jcsp jcsp added area/kafka kind/bug Something isn't working labels Sep 15, 2021
@twmb
Copy link
Contributor Author

twmb commented Feb 7, 2024

cc @michael-redpanda

@michael-redpanda
Copy link
Contributor

Some analysis of cleanup.policy: https://github.com/redpanda-data/core-internal/issues/1066

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kafka kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants