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 DEE6D200CE9 for ; Sat, 19 Aug 2017 11:07:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DD46E16B83A; Sat, 19 Aug 2017 09:07:05 +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 2EE3A16B828 for ; Sat, 19 Aug 2017 11:07:05 +0200 (CEST) Received: (qmail 35260 invoked by uid 500); 19 Aug 2017 09:07: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 35248 invoked by uid 99); 19 Aug 2017 09:07:04 -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; Sat, 19 Aug 2017 09:07:04 +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 A1AC6C0385 for ; Sat, 19 Aug 2017 09:07:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id rthm1RdVK9Fg for ; Sat, 19 Aug 2017 09:07:03 +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 CF38A5FDBC for ; Sat, 19 Aug 2017 09:07:02 +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 4A11CE01BE for ; Sat, 19 Aug 2017 09:07:02 +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 5C30821409 for ; Sat, 19 Aug 2017 09:07:00 +0000 (UTC) Date: Sat, 19 Aug 2017 09:07:00 +0000 (UTC) From: "Pengwei (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-5752) Delete topic and re-create topic immediate will delete the new topic's timeindex MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 19 Aug 2017 09:07:06 -0000 Pengwei created KAFKA-5752: ------------------------------ Summary: Delete topic and re-create topic immediate will delete the new topic's timeindex Key: KAFKA-5752 URL: https://issues.apache.org/jira/browse/KAFKA-5752 Project: Kafka Issue Type: Bug Affects Versions: 0.11.0.0, 0.10.2.0 Reporter: Pengwei When we delete the topic and re-create the topic with the same name, we will find after the async delete topic is finished, async delete will remove the newly created topic's time index. This is because in the LogManager's asyncDelete, it will change the log and index's file pointer to the renamed log and index, but missing the time index. So will cause this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)