You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kevin Lu (JIRA)" <ji...@apache.org> on 2019/02/12 00:14:00 UTC
[jira] [Updated] (KAFKA-7236) Add --under-min-isr option to
describe topics command
[ https://issues.apache.org/jira/browse/KAFKA-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Lu updated KAFKA-7236:
----------------------------
Fix Version/s: 2.2.0
> Add --under-min-isr option to describe topics command
> -----------------------------------------------------
>
> Key: KAFKA-7236
> URL: https://issues.apache.org/jira/browse/KAFKA-7236
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Kevin Lu
> Assignee: Kevin Lu
> Priority: Minor
> Fix For: 2.2.0
>
>
> The "min.insync.replicas" configuration specifies the minimum number of insync replicas required for a partition to accept messages from the producer. If the insync replica count of a partition falls under the specified "min.insync.replicas", then the broker will reject messages for producers using acks=all. These producers will suffer unavailability as they will see a NotEnoughReplicas or NotEnoughReplicasAfterAppend exception.
> We currently have an UnderMinIsrPartitionCount metric which is useful for identifying when partitions fall under "min.insync.replicas", however it is still difficult to identify which topic partitions are affected and need fixing.
> We can leverage the describe topics command in TopicCommand to add an option "--under-minisr-partitions" to list out exactly which topic partitions are below "min.insync.replicas".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)