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 BEB85200CB5 for ; Wed, 12 Jul 2017 09:31:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BD44516827C; Wed, 12 Jul 2017 07:31:07 +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 0FE2D168279 for ; Wed, 12 Jul 2017 09:31:06 +0200 (CEST) Received: (qmail 36470 invoked by uid 500); 12 Jul 2017 07:31:06 -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 36459 invoked by uid 99); 12 Jul 2017 07:31:06 -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; Wed, 12 Jul 2017 07:31:06 +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 89F20195B50 for ; Wed, 12 Jul 2017 07:31:05 +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 Z3HcbUwAE4mb for ; Wed, 12 Jul 2017 07:31: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 4454C6243E for ; Wed, 12 Jul 2017 07:31: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 5F6E2E06CF for ; Wed, 12 Jul 2017 07:31: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 1E340246F9 for ; Wed, 12 Jul 2017 07:31:00 +0000 (UTC) Date: Wed, 12 Jul 2017 07:31:00 +0000 (UTC) From: "Jeff Widman (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References:

Subject: [jira] [Updated] (KAFKA-5584) Incorrect log size for topics larger than 2 GB MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 12 Jul 2017 07:31:07 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5584: ------------------------------- Description: The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow. For large topics (larger than 2 GB) this value overflows. This is easily observable in the reported metrics values of the path {{log.Log.partition.*.topic..Size}} (see attached screenshot). Moreover I think this breaks the size-based retention (via {{log.retention.bytes}} and {{retention.bytes}}) of large topics as well. I am not sure on the recommended workflow, should I open a pull request on github with a fix? was: The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow. For large topics (larger than 2 GB) this value overflows. This is easily observable in the reported metrics values of the path {{log.Log.partiion.*.topic..Size}} (see attached screenshot). Moreover I think this breaks the size-based retention (via {{log.retention.bytes}} and {{retention.bytes}}) of large topics as well. I am not sure on the recommended workflow, should I open a pull request on github with a fix? > Incorrect log size for topics larger than 2 GB > ---------------------------------------------- > > Key: KAFKA-5584 > URL: https://issues.apache.org/jira/browse/KAFKA-5584 > Project: Kafka > Issue Type: Bug > Components: log > Reporter: Gregor Uhlenheuer > Attachments: Screen Shot 2017-07-12 at 09.10.53.png > > > The {{size}} of a {{Log}} is calculated incorrectly due to an Integer overflow. For large topics (larger than 2 GB) this value overflows. > This is easily observable in the reported metrics values of the path {{log.Log.partition.*.topic..Size}} (see attached screenshot). > Moreover I think this breaks the size-based retention (via {{log.retention.bytes}} and {{retention.bytes}}) of large topics as well. > I am not sure on the recommended workflow, should I open a pull request on github with a fix? -- This message was sent by Atlassian JIRA (v6.4.14#64029)