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

Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2025/12/29 03:13:00 UTC

[jira] [Resolved] (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 ]

Chia-Ping Tsai resolved KAFKA-19858.
------------------------------------
    Fix Version/s: 4.3.0
       Resolution: Fixed

> 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
>              Labels: need-kip
>             Fix For: 4.3.0
>
>
> 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)