You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jorge Esteban Quilcate Otoya (Jira)" <ji...@apache.org> on 2023/11/23 19:43:00 UTC
[jira] [Comment Edited] (KAFKA-15132) Implement disable & re-enablement for Tiered Storage
[ https://issues.apache.org/jira/browse/KAFKA-15132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789243#comment-17789243 ]
Jorge Esteban Quilcate Otoya edited comment on KAFKA-15132 at 11/23/23 7:42 PM:
--------------------------------------------------------------------------------
Just realized that the current behavior allows updating this configuration and silently logs a warning[1] that disabling is not supported.
Is this the expected behavior or should be treated as a bug until KIP-950 is supported? As a user, I'd expect the config update to actually fail if a feature is not supported instead of getting into an unsupported state.
cc [~satishd] [~showuon]
[1] [https://github.com/apache/kafka/blob/6c232b542cff9db3ecc1d0bdf6e9174960c93798/core/src/main/scala/kafka/server/ConfigHandler.scala#L73-L91]
was (Author: jeqo):
Just realized that the current behavior allows updating this configuration and silently logs a warning[1] that disabling is not supported.
Is this the expected behavior or should be treated as a bug? As a user, I'd expect the config update to actually fail if a feature is not supported instead of getting into an unsupported state.
cc [~satishd] [~showuon]
[1] https://github.com/apache/kafka/blob/6c232b542cff9db3ecc1d0bdf6e9174960c93798/core/src/main/scala/kafka/server/ConfigHandler.scala#L73-L91
> Implement disable & re-enablement for Tiered Storage
> ----------------------------------------------------
>
> Key: KAFKA-15132
> URL: https://issues.apache.org/jira/browse/KAFKA-15132
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Reporter: Divij Vaidya
> Assignee: Divij Vaidya
> Priority: Major
> Labels: kip
> Fix For: 3.7.0
>
>
> KIP-405 [1] introduces the Tiered Storage feature in Apache Kafka. One of the limitations mentioned in the KIP is inability to re-enable TS on a topic after it has been disabled.
> {quote}Once tier storage is enabled for a topic, it can not be disabled. We will add this feature in future versions. One possible workaround is to create a new topic and copy the data from the desired offset and delete the old topic.
> {quote}
> This task will propose a new KIP which extends on KIP-405 to describe the behaviour on on disablement and re-enablement of tiering storage for a topic. The solution will apply for both Zk and KRaft variants.
> [1] KIP-405 - [https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)