From dev-return-96672-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Thu Aug 2 09:42:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D19BC180629 for ; Thu, 2 Aug 2018 09:42:03 +0200 (CEST) Received: (qmail 60992 invoked by uid 500); 2 Aug 2018 07:42:02 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 60981 invoked by uid 99); 2 Aug 2018 07:42:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2018 07:42:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E9D69C0BF0 for ; Thu, 2 Aug 2018 07:42:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id o0yismFR81Bw for ; Thu, 2 Aug 2018 07:42:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id ED66E5F29A for ; Thu, 2 Aug 2018 07:42:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8179CE2072 for ; Thu, 2 Aug 2018 07:42:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 26E292775E for ; Thu, 2 Aug 2018 07:42:00 +0000 (UTC) Date: Thu, 2 Aug 2018 07:42:00 +0000 (UTC) From: "Kevin Lu (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-7236) Add --critical-partitions option to describe topics command MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Kevin Lu created KAFKA-7236: ------------------------------- Summary: Add --critical-partitions option to describe topics c= ommand 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 A topic partition can be in one of four states (assuming replication factor= of 3): =C2=A0 (ISR =3D in sync replica) =C2=A0 3/3 ISRs: OK 2/3 ISRs: WARNING (under-replicated partition) 1/3 ISRs: CRITICAL (under-replicated partition) 0/3 ISRs: FATAL (offline/unavailable partition) =C2=A0 TopicCommand already has the --under-replicated-partitions and --unavailabl= e-partitions flags, but it would be beneficial to include an additional --c= ritical-partitions option that specifically lists out partitions in CRITICA= L state (only one remaining ISR left). =C2=A0 With this new option, Kafka users can use this option to identify the exact= topic partitions that are critical and need immediate repartitioning. Kafk= a users can also set up critical alerts to trigger when the output of this = command contains partitions. =C2=A0 A couple cases where identifying this CRITICAL state is useful in alerting: * Users that have a large amount of topics in a single cluster, making it = incredibly hard to manually repartition all topics that have under-replicat= ed partitions, so they only take action when it hits CRITICAL state * Users with a high replication-factor that can tolerate some broker failu= res and only take action when it hits CRITICAL state -- This message was sent by Atlassian JIRA (v7.6.3#76005)