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 B16CD200CAB for ; Sun, 18 Jun 2017 19:50:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AFF88160BE3; Sun, 18 Jun 2017 17:50:03 +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 01FD9160BD1 for ; Sun, 18 Jun 2017 19:50:02 +0200 (CEST) Received: (qmail 3259 invoked by uid 500); 18 Jun 2017 17:50:02 -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 3248 invoked by uid 99); 18 Jun 2017 17:50:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Jun 2017 17:50:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B00DE1A07ED for ; Sun, 18 Jun 2017 17:50:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YSy559U0eu23 for ; Sun, 18 Jun 2017 17:50: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 C27AC5FAC5 for ; Sun, 18 Jun 2017 17:50: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 4C289E00A3 for ; Sun, 18 Jun 2017 17:50: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 07FBE21E14 for ; Sun, 18 Jun 2017 17:50:00 +0000 (UTC) Date: Sun, 18 Jun 2017 17:50:00 +0000 (UTC) From: "Divya (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-5467) setting offset retention minutes to a lower value is not reflecting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 18 Jun 2017 17:50:03 -0000 Divya created KAFKA-5467: ---------------------------- Summary: setting offset retention minutes to a lower value is not reflecting Key: KAFKA-5467 URL: https://issues.apache.org/jira/browse/KAFKA-5467 Project: Kafka Issue Type: Bug Components: offset manager Affects Versions: 0.10.1.1 Reporter: Divya We have been observing offsets to be unknown and saw that our offset retention time was lesser than the log retention period. Inorder to recreate the same in test environment, we set the offset.retention.minutes to 1 minute and the log retention time to 168 hours. There were no events written for more than an hour but still the offsets were not turning to unknown. (The offset clean interval was 10 minutes.) I would like to know the reason on why the offset did not turn to unknown in an hour. -- This message was sent by Atlassian JIRA (v6.4.14#64029)