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 15222200CA3 for ; Wed, 17 May 2017 17:35:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 139F2160BB5; Wed, 17 May 2017 15:35:11 +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 61825160BBA for ; Wed, 17 May 2017 17:35:10 +0200 (CEST) Received: (qmail 50578 invoked by uid 500); 17 May 2017 15:35:09 -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 50270 invoked by uid 99); 17 May 2017 15:35:08 -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; Wed, 17 May 2017 15:35:08 +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 C15A0C16CC for ; Wed, 17 May 2017 15:35:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wbTHeGkQOix2 for ; Wed, 17 May 2017 15:35:05 +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 93B2C5FBDF for ; Wed, 17 May 2017 15:35:05 +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 DAD33E0D90 for ; Wed, 17 May 2017 15:35:04 +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 48AD3263AE for ; Wed, 17 May 2017 15:35:04 +0000 (UTC) Date: Wed, 17 May 2017 15:35:04 +0000 (UTC) From: "Konstantin Smirnov (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5263) kakfa-clients consume 100% CPU with manual partition assignment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 17 May 2017 15:35:11 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014226#comment-16014226 ] Konstantin Smirnov commented on KAFKA-5263: ------------------------------------------- Sample code leading to the trouble: {code} public static void main(String[] args) { System.out.println("Starting consumer"); Properties props = new Properties(); props.put("bootstrap.servers", "localhost:9092"); props.put("group.id", "test12345"); props.put("reconnect.backoff.ms", "1000"); props.put("retry.backoff.ms", "1000"); props.put("session.timeout.ms", "10000"); props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer"); props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer"); try (KafkaConsumer consumer = new KafkaConsumer<>(props)) { String topic = "test-topic"; // consumer.subscribe(Arrays.asList(topic)); List partitions = new ArrayList<>(); for (PartitionInfo partition : consumer.partitionsFor(topic)) { partitions.add(new TopicPartition(topic, partition.partition())); } consumer.assign(partitions); for (;;) { ConsumerRecords records = consumer.poll(1000); if (!records.isEmpty()) { System.out.println("Records aren't empty!"); } records.forEach(System.out::println); } } } {code} > kakfa-clients consume 100% CPU with manual partition assignment > --------------------------------------------------------------- > > Key: KAFKA-5263 > URL: https://issues.apache.org/jira/browse/KAFKA-5263 > Project: Kafka > Issue Type: Bug > Components: clients > Affects Versions: 0.10.1.0, 0.10.1.1, 0.10.2.0, 0.10.2.1 > Reporter: Konstantin Smirnov > > Noticed that lose of the connection to Kafka broker leads kafka-clients to consume 100% CPU. The bug only appears when the manual partition assignmet is used. It appears since the version 0.10.1.0. The bug is quite similar to KAFKA-1642. -- This message was sent by Atlassian JIRA (v6.3.15#6346)