Hi Avishek,
Unfortunately, disabling tiered storage only works under KRaft mode.
If you look closely at the KIP-950[1], you'll see this sentence (see the
underlined section):
> *Support for Both KRaft and Zookeeper-backed Clusters*: The tiered
storage disablement feature should be designed and implemented to support
both KRaft and Zookeeper-backed Kafka clusters, ensuring compatibility
across different cluster configurations. Updated: *We will implement for
KRaft only in v3.9.0.*
I agree that the KIP itself seems to state that it will work with both. But
in the end it was only implemented in KRaft mode. Also, one can see in the
documentation PR[2] that it only mentions how to disable it in KRaft mode.
Sorry this is not the answer you were looking for.
[1]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-950%3A++Tiered+Storage+Disablement
[2]: https://github.com/apache/kafka/pull/16836/changes
On Wed, Feb 18, 2026 at 1:53 PM Avishek Das via users <
users@kafka.apache.org> wrote:
> Hello Community,
>
> As part of our testing, I am validating the scenario where tiered storage
> is disabled on a topic where it was previously enabled.
>
> I attempted to alter the topic configuration using the following configs:
>
> remote.storage.enable=true
> remote.log.copy.disable=true
>
>
> However, this results in an exception stating that remote.log.copy.disable
> is not valid in ZooKeeper mode.
>
> Caused by: org.apache.kafka.common.errors.InvalidConfigurationException:
> It is invalid to set `remote.log.delete.on.disable` or
> `remote.log.copy.disable` under Zookeeper's mode.
>
>
> We are running Kafka v3.9.1 on a ZooKeeper-backed cluster, and based on the
> KIP-950
> <
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263424654#KIP950:TieredStorageDisablement-StateTransitions
> >
> documentation, these configurations appear to be available for
> ZooKeeper-based clusters as well.
>
> Am I missing any prerequisite or additional step required to disable Tiered
> Storage for an existing topic in this setup?
>
> Thanks!
>
> --
> Avishek Das
> SMTS | Salesforce
> Mobile: +917008383890
>
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Sr. Engineering Director, Streaming Services, *Aiven*
josep.prat@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/> <https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa, Kenneth Chen
Amtsgericht Charlottenburg, HRB 209739 B
Unfortunately, disabling tiered storage only works under KRaft mode.
If you look closely at the KIP-950[1], you'll see this sentence (see the
underlined section):
> *Support for Both KRaft and Zookeeper-backed Clusters*: The tiered
storage disablement feature should be designed and implemented to support
both KRaft and Zookeeper-backed Kafka clusters, ensuring compatibility
across different cluster configurations. Updated: *We will implement for
KRaft only in v3.9.0.*
I agree that the KIP itself seems to state that it will work with both. But
in the end it was only implemented in KRaft mode. Also, one can see in the
documentation PR[2] that it only mentions how to disable it in KRaft mode.
Sorry this is not the answer you were looking for.
[1]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-950%3A++Tiered+Storage+Disablement
[2]: https://github.com/apache/kafka/pull/16836/changes
On Wed, Feb 18, 2026 at 1:53 PM Avishek Das via users <
users@kafka.apache.org> wrote:
> Hello Community,
>
> As part of our testing, I am validating the scenario where tiered storage
> is disabled on a topic where it was previously enabled.
>
> I attempted to alter the topic configuration using the following configs:
>
> remote.storage.enable=true
> remote.log.copy.disable=true
>
>
> However, this results in an exception stating that remote.log.copy.disable
> is not valid in ZooKeeper mode.
>
> Caused by: org.apache.kafka.common.errors.InvalidConfigurationException:
> It is invalid to set `remote.log.delete.on.disable` or
> `remote.log.copy.disable` under Zookeeper's mode.
>
>
> We are running Kafka v3.9.1 on a ZooKeeper-backed cluster, and based on the
> KIP-950
> <
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263424654#KIP950:TieredStorageDisablement-StateTransitions
> >
> documentation, these configurations appear to be available for
> ZooKeeper-based clusters as well.
>
> Am I missing any prerequisite or additional step required to disable Tiered
> Storage for an existing topic in this setup?
>
> Thanks!
>
> --
> Avishek Das
> SMTS | Salesforce
> Mobile: +917008383890
>
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Sr. Engineering Director, Streaming Services, *Aiven*
josep.prat@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/> <https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa, Kenneth Chen
Amtsgericht Charlottenburg, HRB 209739 B
Comments
Post a Comment