From jira-return-10620-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Mon Mar 12 17:23:07 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 1C32018064D for ; Mon, 12 Mar 2018 17:23:06 +0100 (CET) Received: (qmail 41148 invoked by uid 500); 12 Mar 2018 16:23:05 -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 40842 invoked by uid 99); 12 Mar 2018 16:23: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; Mon, 12 Mar 2018 16:23: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 4DBF1C050E for ; Mon, 12 Mar 2018 16:23:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4ubscZj-K2bZ for ; Mon, 12 Mar 2018 16:23:03 +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 332E95F476 for ; Mon, 12 Mar 2018 16:23: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 45642E0294 for ; Mon, 12 Mar 2018 16:23:01 +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 A36A621479 for ; Mon, 12 Mar 2018 16:23:00 +0000 (UTC) Date: Mon, 12 Mar 2018 16:23:00 +0000 (UTC) From: "Manikumar (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KAFKA-6337) Error for partition [__consumer_offsets,15] to broker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6337. ------------------------------ Resolution: Cannot Reproduce Please reopen if you think the issue still exists > Error for partition [__consumer_offsets,15] to broker > ----------------------------------------------------- > > Key: KAFKA-6337 > URL: https://issues.apache.org/jira/browse/KAFKA-6337 > Project: Kafka > Issue Type: Bug > Affects Versions: 0.10.2.0 > Environment: Windows running Kafka(0.10.2.0) > 3 ZK Instances running on 3 different Windows Servers, 7 Kafka Broker nodes running on single windows machine with different disk for logs directory. > Reporter: Abhi > Priority: Blocker > Labels: windows > > Hello * > I am running Kafka(0.10.2.0) on windows from the past one year ... > But off late there has been unique Broker issues that I have observed 4-5 times in > last 4 months. > Kafka setup cofig... > 3 ZK Instances running on 3 different Windows Servers, 7 Kafka Broker nodes running on single windows machine with different disk for logs directory.... > My Kafka has 2 Topics with partition size 50 each , and replication factor of 3. > My partition logic selection: Each message has a unique ID and logic of selecting partition is ( unique ID % 50), and then calling Kafka producer API to route a specific message to a particular topic partition . > My Each Broker Properties look like this > {{broker.id=0 > port:9093 > num.network.threads=3 > num.io.threads=8 > socket.send.buffer.bytes=102400 > socket.receive.buffer.bytes=102400 > socket.request.max.bytes=104857600 > offsets.retention.minutes=360 > advertised.host.name=1.1.1.2 > advertised.port:9093 > ctories under which to store log files > log.dirs=C:\\kafka_2.10-0.10.2.0-SNAPSHOT\\data\\kafka-logs > num.partitions=1 > num.recovery.threads.per.data.dir=1 > log.retention.minutes=360 > log.segment.bytes=52428800 > log.retention.check.interval.ms=300000 > log.cleaner.enable=true > log.cleanup.policy=delete > log.cleaner.min.cleanable.ratio=0.5 > log.cleaner.backoff.ms=15000 > log.segment.delete.delay.ms=6000 > auto.create.topics.enable=false > zookeeper.connect=1.1.1.2:2181,1.1.1.3:2182,1.1.1.4:2183 > zookeeper.connection.timeout.ms=6000 > }} > But of-late there has been a unique case that's cropping out in Kafka broker nodes, > _[2017-12-02 02:47:40,024] ERROR [ReplicaFetcherThread-0-4], Error for partition [__consumer_offsets,15] to broker 4:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)_ > The entire server.log is filled with these logs, and its very huge too , please help me in understanding under what circumstances these can occur, and what measures I need to take.. > Please help me this is the third time in last three Saturdays i faced the similar issue. > Courtesy > Abhi > !wq -- This message was sent by Atlassian JIRA (v7.6.3#76005)