From dev-return-95750-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Tue Jul 3 12:58:05 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 6DC61180632 for ; Tue, 3 Jul 2018 12:58:04 +0200 (CEST) Received: (qmail 69075 invoked by uid 500); 3 Jul 2018 10:58:03 -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 69063 invoked by uid 99); 3 Jul 2018 10:58:03 -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, 03 Jul 2018 10:58:03 +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 9CD69185A19 for ; Tue, 3 Jul 2018 10:58:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, 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 Xg7Ca9_DAEjo for ; Tue, 3 Jul 2018 10:58:01 +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 5A31360CF8 for ; Tue, 3 Jul 2018 10:58: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 9D820E0C54 for ; Tue, 3 Jul 2018 10:58: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 17EA2274EE for ; Tue, 3 Jul 2018 10:58:00 +0000 (UTC) Date: Tue, 3 Jul 2018 10:58:00 +0000 (UTC) From: "Karsten Schnitter (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-7130) EOFException after rolling log segment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Karsten Schnitter created KAFKA-7130: ---------------------------------------- Summary: EOFException after rolling log segment Key: KAFKA-7130 URL: https://issues.apache.org/jira/browse/KAFKA-7130 Project: Kafka Issue Type: Bug Components: replication Affects Versions: 1.1.0 Reporter: Karsten Schnitter When rolling a log segment one of our Kafka cluster got an immediate read e= rror on the same partition. This lead to a flood of log messages containing= the corresponding stacktraces. Data was still appended to the partition bu= t consumers were unable to read from that partition. Reason for the excepti= on is unclear. {noformat} [2018-07-02 23:53:32,732] INFO [Log partition=3Dingestion-3, dir=3D/var/vca= p/store/kafka] Rolled new log segment at offset 971865991 in 1 ms. (kafka.l= og.Log) [2018-07-02 23:53:32,739] INFO [ProducerStateManager partition=3Dingestion-= 3] Writing producer snapshot at offset 971865991 (kafka.log.ProducerStateMa= nager) [2018-07-02 23:53:32,739] INFO [Log partition=3Dingestion-3, dir=3D/var/vca= p/store/kafka] Rolled new log segment at offset 971865991 in 1 ms. (kafka.l= og.Log) [2018-07-02 23:53:32,750] ERROR [ReplicaManager broker=3D1] Error processin= g fetch operation on partition ingestion-3, offset 971865977 (kafka.server.= ReplicaManager) Caused by: java.io.EOFException: Failed to read `log header` from file chan= nel `sun.nio.ch.FileChannelImpl@2e0e8810`. Expected to read 17 bytes, but r= eached end of file after reading 0 bytes. Started read from position 214748= 3643. {noformat} We mitigated the issue by stopping the affected node and deleting the corre= sponding directory. Once the partition was recreated for the replica (we us= e replication-factor 2) the other replica experienced the same problem. We = mitigated likewise. To us it is unclear, what caused this issue. Can you help us in finding the= root cause of this problem? =C2=A0 =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)