[
https://issues.apache.org/jira/browse/KAFKA-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765456#comment-16765456
]
ASF GitHub Bot commented on KAFKA-7236:
---------------------------------------
vahidhashemian commented on pull request #6224: KAFKA-7236: Add --under-min-isr
option to describe topics command (KIP-351)
URL: https://github.com/apache/kafka/pull/6224
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
