From jira-return-10433-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Mon Mar 5 22:02:06 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 AAC88180608 for ; Mon, 5 Mar 2018 22:02:05 +0100 (CET) Received: (qmail 42075 invoked by uid 500); 5 Mar 2018 21:02: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 42064 invoked by uid 99); 5 Mar 2018 21:02: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; Mon, 05 Mar 2018 21:02: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 4FFD11804E6 for ; Mon, 5 Mar 2018 21:02:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, 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 DNOBrjsupHCm for ; Mon, 5 Mar 2018 21:02: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 C7CA85F169 for ; Mon, 5 Mar 2018 21:02: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 94C7AE00A7 for ; Mon, 5 Mar 2018 21:02: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 1CAA92126B for ; Mon, 5 Mar 2018 21:02:00 +0000 (UTC) Date: Mon, 5 Mar 2018 21:02:00 +0000 (UTC) From: "dongyan li (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (KAFKA-6610) initial high watermark -1, used for truncation, cause "Cannot truncate to a negative offset" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-6610?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] dongyan li updated KAFKA-6610: ------------------------------ Comment: was deleted (was: Timeline:=C2=A0 {quote}3/5/2018 11:28:23 AM[2018-03-05 17:28:23,084] INFO Replica loaded fo= r TOPICNAME-0 with initial high watermark 0 (kafka.cluster.Replica) 3/5/2018 11:28:23 AM[2018-03-05 17:28:23,086] INFO Replica loaded for parti= tion TOPICNAME-0 with initial high watermark -1 (kafka.cluster.Replica) 3/5/2018 11:28:23 AM[2018-03-05 17:28:23,086] INFO Replica loaded for parti= tion TOPICNAME-0 with initial high watermark 0 (kafka.cluster.Replica){quot= e} Later: {quote}3/5/2018 11:28:23 AM[2018-03-05 17:28:23,305] WARN [ReplicaFetcherTh= read-0-1]: Based on follower's leader epoch, leader replied with an unknown= offset in cmdty_ifl_inbound_fix-0. High watermark -1 will be used for trun= cation. (kafka.server.ReplicaFetcherThread){quote} Then, error: (timestamp is not right, but the content is the same) {quote}3/5/2018 10:32:26 AMjava.lang.IllegalArgumentException: Cannot trunc= ate to a negative offset (-1). 3/5/2018 10:32:26 AM at kafka.log.Log.truncateTo(Log.scala:1377) 3/5/2018 10:32:26 AM at kafka.log.LogManager.$anonfun$truncateTo$2(LogManag= er.scala:330) 3/5/2018 10:32:26 AM at kafka.log.LogManager.$anonfun$truncateTo$2$adapted(= LogManager.scala:321) 3/5/2018 10:32:26 AM at scala.collection.TraversableLike$WithFilter.$anonfu= n$foreach$1(TraversableLike.scala:789) 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.$anonfun$foreach$1= (HashMap.scala:138) 3/5/2018 10:32:26 AM at scala.collection.mutable.HashTable.foreachEntry(Has= hTable.scala:236) 3/5/2018 10:32:26 AM at scala.collection.mutable.HashTable.foreachEntry$(Ha= shTable.scala:229) 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.foreachEntry(HashM= ap.scala:40) 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.foreach(HashMap.sc= ala:138) 3/5/2018 10:32:26 AM at scala.collection.TraversableLike$WithFilter.foreach= (TraversableLike.scala:788) 3/5/2018 10:32:26 AM at kafka.log.LogManager.truncateTo(LogManager.scala:32= 1) 3/5/2018 10:32:26 AM at kafka.server.ReplicaFetcherThread.maybeTruncate(Rep= licaFetcherThread.scala:279) 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.$anonfun$maybeTr= uncate$2(AbstractFetcherThread.scala:133) 3/5/2018 10:32:26 AM at scala.runtime.java8.JFunction0$mcV$sp.apply(JFuncti= on0$mcV$sp.java:12) 3/5/2018 10:32:26 AM at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:213) 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.maybeTruncate(Ab= stractFetcherThread.scala:130) 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.doWork(AbstractF= etcherThread.scala:102) 3/5/2018 10:32:26 AM at kafka.utils.ShutdownableThread.run(ShutdownableThre= ad.scala:64){quote} =C2=A0 =C2=A0) > initial high watermark -1, used for truncation, cause "Cannot truncate to= a negative offset" > -------------------------------------------------------------------------= ------------------- > > Key: KAFKA-6610 > URL: https://issues.apache.org/jira/browse/KAFKA-6610 > Project: Kafka > Issue Type: Bug > Components: log, replication > Affects Versions: 0.11.0.2 > Reporter: dongyan li > Priority: Major > > Hello, > I got issue that cause the Kafka broker not in-sync with topics. When I c= heck the log, found one of the topic has "-1" highwatermark, then used as t= he offset for truncating and later caused exception:=C2=A0 > {quote}3/5/2018 10:32:26 AM[2018-03-05 16:32:26,576] ERROR [ReplicaFetche= rThread-0-1]: Error due to (kafka.server.ReplicaFetcherThread) > 3/5/2018 10:32:26 AMjava.lang.IllegalArgumentException: Cannot truncate = to a negative offset (-1). > 3/5/2018 10:32:26 AM at kafka.log.Log.truncateTo(Log.scala:1377) > 3/5/2018 10:32:26 AM at kafka.log.LogManager.$anonfun$truncateTo$2(LogMa= nager.scala:330) > 3/5/2018 10:32:26 AM at kafka.log.LogManager.$anonfun$truncateTo$2$adapt= ed(LogManager.scala:321) > 3/5/2018 10:32:26 AM at scala.collection.TraversableLike$WithFilter.$ano= nfun$foreach$1(TraversableLike.scala:789) > 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.$anonfun$foreac= h$1(HashMap.scala:138) > 3/5/2018 10:32:26 AM at scala.collection.mutable.HashTable.foreachEntry(= HashTable.scala:236) > 3/5/2018 10:32:26 AM at scala.collection.mutable.HashTable.foreachEntry$= (HashTable.scala:229) > 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.foreachEntry(Ha= shMap.scala:40) > 3/5/2018 10:32:26 AM at scala.collection.mutable.HashMap.foreach(HashMap= .scala:138) > 3/5/2018 10:32:26 AM at scala.collection.TraversableLike$WithFilter.fore= ach(TraversableLike.scala:788) > 3/5/2018 10:32:26 AM at kafka.log.LogManager.truncateTo(LogManager.scala= :321) > 3/5/2018 10:32:26 AM at kafka.server.ReplicaFetcherThread.maybeTruncate(= ReplicaFetcherThread.scala:279) > 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.$anonfun$mayb= eTruncate$2(AbstractFetcherThread.scala:133) > 3/5/2018 10:32:26 AM at scala.runtime.java8.JFunction0$mcV$sp.apply(JFun= ction0$mcV$sp.java:12) > 3/5/2018 10:32:26 AM at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:21= 3) > 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.maybeTruncate= (AbstractFetcherThread.scala:130) > 3/5/2018 10:32:26 AM at kafka.server.AbstractFetcherThread.doWork(Abstra= ctFetcherThread.scala:102) > 3/5/2018 10:32:26 AM at kafka.utils.ShutdownableThread.run(ShutdownableT= hread.scala:64) > {quote} > I deleted the log directory of that topic but topic partition got re-crea= ted after restart, with same error after. I'm wondering how the `highwaterm= ark` get set to -1. I failed to trace the code flow from the `Replica` cons= tructor. Thank you. > =C2=A0 > Dongyan -- This message was sent by Atlassian JIRA (v7.6.3#76005)