[
https://issues.apache.org/jira/browse/KAFKA-17405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877932#comment-17877932
]
Chia-Ping Tsai edited comment on KAFKA-17405 at 9/2/24 3:12 AM:
----------------------------------------------------------------
the summary: https://github.com/apache/kafka/pull/16873#discussion_r1735472015
Dear all, do we reach the consensus on any approach to validate MV for tier
storage?
# RPC version check: works with dynamical MV but cannot do fail-fast
# RLM initialization check: good at fail-fast but cannot check dynamic MV after
initialization. BTW, there was an issue
(https://issues.apache.org/jira/browse/KAFKA-16790) used to change the
initialization order of RLM and metadata publisher.
# Set min MV to 3.6 when RLM is enabled. Good at fail-fast and dynamic MV
check. However, it is a bit weird to change the min MV by the
non-feature-version.
# Ship tier storage to feature version? Too large to be in 3.9
# Let it go. We have announced the requirement of tier storage, so users should
be aware of that!
was (Author: chia7712):
the summary: https://github.com/apache/kafka/pull/16873#discussion_r1735472015
> how to enforce the MV 3.5 when enabling tiered storage? maybe: enforce it
> once at the feature version level
> -----------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17405
> URL: https://issues.apache.org/jira/browse/KAFKA-17405
> Project: Kafka
> Issue Type: Wish
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Major
>
> see discussion:
> [https://github.com/apache/kafka/pull/16873#discussion_r1725621368]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
