[
https://issues.apache.org/jira/browse/KAFKA-15667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875163#comment-17875163
]
Luke Chen commented on KAFKA-15667:
-----------------------------------
I think so. It'd be better you do a simple test locally. I've assigned to you.
Thanks.
> preCheck the invalid configuration for tiered storage replication factor
> ------------------------------------------------------------------------
>
> Key: KAFKA-15667
> URL: https://issues.apache.org/jira/browse/KAFKA-15667
> Project: Kafka
> Issue Type: Improvement
> Components: Tiered-Storage
> Affects Versions: 3.6.0
> Reporter: Luke Chen
> Priority: Major
>
> `remote.log.metadata.topic.replication.factor` is a config to set the
> Replication factor of remote log metadata topic. For the
> `min.insync.replicas`, we'll use the broker config. Today, if the
> `remote.log.metadata.topic.replication.factor` < `min.insync.replicas` value,
> everything still works until new remote log metadata records created. We
> should be able to identify it when broker startup to notify users to fix the
> invalid config.
> ref:
> https://kafka.apache.org/documentation/#remote_log_metadata_manager_remote.log.metadata.topic.replication.factor
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
