Hi Jianfeng, The reason we don't support ZK mode is because the ZK is going to be removed in v4.0.0, so we decided to only implement it in KRaft mode.
> I read the source code and seems kafka broker only updates the LogConfig and then invokes maybeUpdateRemoteLogComponents to cancel some tasks. So I want to know how if just update the log configs without a v5 stopReplicas v5 rpc from controller to broker in zk mode? The ZK mode is not completely implemented IIRC, and not being tested. So I'd suggest you upgrade to KRaft for it. Thank you. Luke On Mon, Oct 28, 2024 at 12:32 PM Jianfeng Lin <jianfeng....@shopee.com.invalid> wrote: > Hi kafka community, I read the KIP-950 > < > https://cwiki.apache.org/confluence/display/KAFKA/KIP-950%3A++Tiered+Storage+Disablement#KIP950:TieredStorageDisablement-Disablement-ZookeeperBackedCluster > > > which > describe the disablement of kafka tiered storage. It said that zk mode > won't be supported and I can't find out the reason, with confusion, I have > a question: > This KIP proposes an implement with stopReplicas v5 to let brokers know > which topic partitions should stop their remote storage functions when > "remote.log.copy.disable" is set to true, different from kraft mode, it > takes an extra rpc round. I read the source code and seems kafka broker > only updates the LogConfig and then invokes maybeUpdateRemoteLogComponents > to > cancel some tasks. So I want to know how if just update the log configs > without a v5 stopReplicas v5 rpc from controller to broker in zk mode? And > why zk mode is not supported to disable? > Really appreciate if Luke Chen<show...@gmail.com> could help to answer, > thanks in advance! > > > Jianfeng Lin from Shopee >
