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 6530A200D35 for ; Tue, 7 Nov 2017 07:52:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 63B1E160BED; Tue, 7 Nov 2017 06:52:46 +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 A86461609C8 for ; Tue, 7 Nov 2017 07:52:45 +0100 (CET) Received: (qmail 9775 invoked by uid 500); 7 Nov 2017 06:52:44 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 9766 invoked by uid 99); 7 Nov 2017 06:52:44 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2017 06:52:44 +0000 Received: from mail-pf0-f174.google.com (mail-pf0-f174.google.com [209.85.192.174]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C0FD71A00A5 for ; Tue, 7 Nov 2017 06:52:43 +0000 (UTC) Received: by mail-pf0-f174.google.com with SMTP id i5so9638249pfe.6 for ; Mon, 06 Nov 2017 22:52:43 -0800 (PST) X-Gm-Message-State: AMCzsaUEsGGDDM/57ZqpUWBwZQDA3XT7TzoQCn2shJOnH2GebcUaU0Al LlJ94F59EO8lI3VfLHTaMAPC+DGJDEm/z1DYV0A= X-Google-Smtp-Source: ABhQp+QeMcWtuCjq4pHhTSyCKapaw3MLCEXV9ZHb1O+MVQLjpE7ARAnP81u+mzA+k4leUSRtulisKBI5qa4WPdcxaaE= X-Received: by 10.84.131.109 with SMTP id 100mr17607801pld.140.1510037563039; Mon, 06 Nov 2017 22:52:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.130.72 with HTTP; Mon, 6 Nov 2017 22:52:42 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= Date: Tue, 7 Nov 2017 07:52:42 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: KafkaSpout not committing to some kafka partitions and stop consuming To: user@storm.apache.org Content-Type: multipart/alternative; boundary="94eb2c1305908ae7a1055d5f048a" archived-at: Tue, 07 Nov 2017 06:52:46 -0000 --94eb2c1305908ae7a1055d5f048a Content-Type: text/plain; charset="UTF-8" Hi, There are a few bugs related to this in 1.1.0. One cause could be that the message is right, and you have some failed tuples that haven't been committed which are preventing the spout from progressing. You could also be hitting either of the issues fixed in https://github.com/apache/storm/pull/2156 and https://github.com/apache/storm/pull/2307/files. The second fix is only relevant if you're using topic compaction in Kafka. You might want to try checking out and building storm-kafka-client from one of these branches and see if that fixes your issue. You should be able to use the upgraded storm-kafka-client with your current Storm version. 2017-11-07 4:44 GMT+01:00 Zhechao Ma : > Hi > > We are using KafkaSpout to read messages from kafka servers. We've > frequently come across the situation that KafkaSpout stops consuming from > some kafka partitions. We check logs and find the following log. > > 2017-11-07 11:35:03.170 o.a.s.k.s.KafkaSpout Thread-11-spout-executor[121 > 121] [DEBUG] Not polling. [10000083] uncommitted offsets across all topic > partitions has reached the threshold of [10000000] > > When it reaches to the maxUncommittedOffsets (10000000), KafkaSpout stops > committing to > those partitions, and never consumes again. We also find that this issue > usually happens after partition reassignment. > > Storm 1.0.2 > storm-kafka-clients 1.1.0 > Kafka 0.10.1.1 > > Could anyone give me help? > > -- > Thanks > Zhechao Ma > --94eb2c1305908ae7a1055d5f048a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

There are a few bugs related to= this in 1.1.0. One cause could be that the message is right, and you have = some failed tuples that haven't been committed which are preventing the= spout from progressing. You could also be hitting either of the issues fix= ed in https://github.= com/apache/storm/pull/2156 and https://github.com/apache/storm/pull/2307/files. Th= e second fix is only relevant if you're using topic compaction in Kafka= .

You might want to try checking out and building storm-kafka-= client from one of these branches and see if that fixes your issue. You sho= uld be able to use the upgraded storm-kafka-client with your current Storm = version.

2017-11-07 4:44 GMT+01:00 Zhechao Ma <mazhechaomaillist@gmail.c= om>:
=
Hi

We are using KafkaSpout to read messages from kafka se= rvers. We've frequently come across the situation that KafkaSpout stops= consuming from some kafka partitions. We check logs and find the following= log.

2017-11-07 11:35:03.170 o.a.s.k.s.KafkaS= pout Thread-11-spout-executor[121 121] [DEBUG] Not polling. [10000083] unco= mmitted offsets across all topic partitions has reached the threshold of [1= 0000000]

When it reaches to the maxUncommittedOffse= ts (10000000), KafkaSpout stops committing to
t= hose partitions, and never consumes again. We also find that this issue usu= ally happens after partition reassignment.

Sto= rm 1.0.2
storm-kafka-clients 1.1.0
Kafka 0.10.1.1
=

Could anyone give me help?

--
Thanks
Zhechao Ma

--94eb2c1305908ae7a1055d5f048a--