You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "fujian (Jira)" <ji...@apache.org> on 2025/11/03 07:57:00 UTC

[jira] [Updated] (KAFKA-19858) Add configurable min.insync.replicas (default=2) for __remote_log_metadata topic

     [ https://issues.apache.org/jira/browse/KAFKA-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fujian updated KAFKA-19858:
---------------------------
    Issue Type: Bug  (was: Improvement)

> Add configurable min.insync.replicas (default=2) for __remote_log_metadata topic
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-19858
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19858
>             Project: Kafka
>          Issue Type: Bug
>          Components: Tiered-Storage
>            Reporter: fujian
>            Assignee: fujian
>            Priority: Minor
>
> The __remote_log_metadata internal topic currently lacks a configurable min.insync.replicas setting, relying on the broker-level default (typically 1). This creates a data loss risk in production environments, as writes may be acknowledged by only a single replica.
> This is inconsistent with __transaction_state, which explicitly sets min.insync.replicas=2 via the transaction.state.log.min.isr broker configuration. Both topics store critical metadata and should have equivalent durability guarantees.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)