Return-Path: X-Original-To: apmail-kafka-users-archive@www.apache.org Delivered-To: apmail-kafka-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3931AE768 for ; Wed, 6 Feb 2013 01:41:30 +0000 (UTC) Received: (qmail 2061 invoked by uid 500); 6 Feb 2013 01:41:30 -0000 Delivered-To: apmail-kafka-users-archive@kafka.apache.org Received: (qmail 2006 invoked by uid 500); 6 Feb 2013 01:41:29 -0000 Mailing-List: contact users-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@kafka.apache.org Delivered-To: mailing list users@kafka.apache.org Received: (qmail 1997 invoked by uid 500); 6 Feb 2013 01:41:29 -0000 Delivered-To: apmail-incubator-kafka-users@incubator.apache.org Received: (qmail 1993 invoked by uid 99); 6 Feb 2013 01:41:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2013 01:41:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of manish@ooyala.com designates 209.85.217.181 as permitted sender) Received: from [209.85.217.181] (HELO mail-lb0-f181.google.com) (209.85.217.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2013 01:41:23 +0000 Received: by mail-lb0-f181.google.com with SMTP id gm6so754959lbb.26 for ; Tue, 05 Feb 2013 17:41:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ooyala.com; s=google; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=+EyXSaOG0GYoevtR6EgyLjR8Fh9azXDz9dp5LwJu9pU=; b=Dfk2KkkP33yLKRV6GrvtgjUxTHn7txKzCpGeqnUaH2Fc3Pi+dtMomPMqBS1WxE06mx 1g3VIv/NX0XJE9IQvYlPrhUkq/I2rNN9nUxm7Jw6XObMzNZgRO40C+0hKo20pATs0xuj aMQTflByxYvx/zOIrUtOKKH7uk+OocqV6h/wA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=+EyXSaOG0GYoevtR6EgyLjR8Fh9azXDz9dp5LwJu9pU=; b=cCy6XsABwbp/4UmvimKsRgIiBVMZSy8H/vsxAwXluH0GEOw1rZtiyXPpCCKpCBT50V AumznDdjsOHgwv0v/oaXmpYVJeJBju5nv3Uu4BUzlXJ4wY7ZC6uoN+24MVZOM487HIUL zf74TY3yVMBHH6BjB/Cs3KqyMaVEs/0h1cUgyE6VgxNEQ/oJjzv1i/LY2rJqyFre+iLG CR9lFuHEjSZjRmbJYfNgK68Yd/Z3INgqOdenDQnK2o/46tdC0u0q8AgpEkfcVz5Yl+go vcvEZ7uy3uScy8aHemnLiRn1PpJ1YLeP6Fxksu/nV6CyPrf3fLj2rVU/S6b51HZw9tnn PqRg== MIME-Version: 1.0 X-Received: by 10.152.147.130 with SMTP id tk2mr25067040lab.24.1360114862319; Tue, 05 Feb 2013 17:41:02 -0800 (PST) Received: by 10.112.21.69 with HTTP; Tue, 5 Feb 2013 17:41:02 -0800 (PST) Date: Tue, 5 Feb 2013 17:41:02 -0800 Message-ID: Subject: Consumers constantly rebalancing From: Manish Khettry To: kafka-users@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f22beb938e9d304d5046be5 X-Gm-Message-State: ALoCoQl+rRkovqeKbg23OCPuwHVxtZmTEFpL/d747/sGcU6vm7HTLltQ4XahV/Tlxd7uKC8lf1Rv X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f22beb938e9d304d5046be5 Content-Type: text/plain; charset=ISO-8859-1 We are trying to trouble shoot a problem wherein our system just cannot seem to read messages fast enough from Kafka. We are on kafka 0.6 and are using the simple consumer. >From looking at the logs, and we see a lot (almost constant chatty messages) about rebalancing. So for instance every minute, we see messages like this: Consumer rookery-vacuum-prod_.internal-1360106018385 rebalancing the following partitions: List(0-0, 0-1, 0-10, 0-11, 0-12, 0-13, 0-14, 0-15, 0-16, 0-17, 0-18, 0-19, 0-2, 0-3, 0-4, 0-5, 0-6, 0-7, 0-8, 0-9, 1-0, 1-1, 1-10, 1-11, 1-12, 1-13, 1-14, 1-15, 1-16, 1-17, 1-18, 1-19, 1-2, 1-3, 1-4, 1-5, 1-6, 1-7, 1-8, 1-9) for topic compact-player-logs with consumers: I also see zookeeper timeouts like so: Unable to reconnect to ZooKeeper service, session 0x33c981ab95100ed has expired, closing socket connection We increased the zookeeper session timeout from 6 seconds to 12 seconds and this seems to have helped somewhat but I'm not sure if these zookeeper timeouts at 6 seconds are symptomatic of a problem with our zookeeper cluster and/or connectivity between the consumers and zk. Any thoughts? Manish --e89a8f22beb938e9d304d5046be5--