Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 07B34200D16 for ; Tue, 10 Oct 2017 11:11:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 061CB160BE0; Tue, 10 Oct 2017 09:11:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4A1111609E5 for ; Tue, 10 Oct 2017 11:11:05 +0200 (CEST) Received: (qmail 71105 invoked by uid 500); 10 Oct 2017 09:11:04 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 71085 invoked by uid 99); 10 Oct 2017 09:11:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Oct 2017 09:11:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id BC372182FC6 for ; Tue, 10 Oct 2017 09:11:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ThBSzqj9Dd5P for ; Tue, 10 Oct 2017 09:11:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5DD385FE64 for ; Tue, 10 Oct 2017 09:11:01 +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 7B5A4E0635 for ; Tue, 10 Oct 2017 09:11: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 1115C21EE3 for ; Tue, 10 Oct 2017 09:11:00 +0000 (UTC) Date: Tue, 10 Oct 2017 09:11:00 +0000 (UTC) From: "Ismael Juma (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-6040) Expose topic size for monitoring MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Oct 2017 09:11:06 -0000 [ https://issues.apache.org/jira/browse/KAFKA-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198397#comment-16198397 ] Ismael Juma commented on KAFKA-6040: ------------------------------------ Retention is done on a partition, not topic, so the broker doesn't need to maintain a topic size at the moment. The partition size is exposed via a Log size metric > Expose topic size for monitoring > -------------------------------- > > Key: KAFKA-6040 > URL: https://issues.apache.org/jira/browse/KAFKA-6040 > Project: Kafka > Issue Type: New Feature > Reporter: Michael Andre Pearce > > Currently it seems there is no monitoring endpoint of topic size, even though the cluster must calculate such estimation to maintain retention.size > This is useful operationally to get understanding of actual topic usages, based on what the broker believes. > As interim it seems some scripts exist to get this, but it would be ideal to get the value the broker believes/calculates. > https://gist.github.com/kapkaev/ef633348dbecfedc0166 -- This message was sent by Atlassian JIRA (v6.4.14#64029)