Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8251EE32E for ; Mon, 7 Jan 2013 16:09:09 +0000 (UTC) Received: (qmail 40543 invoked by uid 500); 7 Jan 2013 16:09:09 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 40512 invoked by uid 500); 7 Jan 2013 16:09: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 40504 invoked by uid 99); 7 Jan 2013 16:09:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 16:09:09 +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 jay.kreps@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pb0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 16:09:02 +0000 Received: by mail-pb0-f41.google.com with SMTP id xa7so10656698pbc.14 for ; Mon, 07 Jan 2013 08:08:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=++CaA8enSuqO8iWL+SacEV35UHDwRHX13kQkY1RCDh0=; b=G0LprL3yZ4Ga14L9W1JNRXe22WIGVJQFMcUBZwTDZGIjD/GcQ6xK+L7YmvFEwXv1kt Jrie1G3nyRstwkUxh+oWBRkcAqEDCnis0RHy8bS5u++c2l72ms5raIXe2ojJ5/eubuGw ZDyVKVhu5l8cck6JCwyoAj4TjvQFMUR7Q9ApNh+mx6kaJRuDSy8CzDidtYv53l5B1DBf IPxhy+Sm9xK59/sOl1qeRWT0nlHZE+QKa6FHNuA4E+9U/7FV90XvcBcq0Chp1MAd+Gqs 2/YxpPCwoolJB//UwlOf0mt0UDrXCDdQE4yLsos5ldTLa2S9Zi1/YZo/TTGRUd7J1JMP IdkQ== MIME-Version: 1.0 Received: by 10.68.138.229 with SMTP id qt5mr185489343pbb.122.1357574921406; Mon, 07 Jan 2013 08:08:41 -0800 (PST) Received: by 10.66.122.67 with HTTP; Mon, 7 Jan 2013 08:08:41 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Jan 2013 08:08:41 -0800 Message-ID: Subject: Re: About Kafka 0.8 producer From: Jay Kreps To: "dev@kafka.apache.org" Content-Type: multipart/alternative; boundary=047d7b15aa5bf2494c04d2b50af1 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b15aa5bf2494c04d2b50af1 Content-Type: text/plain; charset=ISO-8859-1 In other words 0.8 gives you the richer functionality of the zk producer without requiring a zk connection. As with zk, you need to give it one or more urls to bootstrap a connection, but these urls don't need to be the complete set of brokers (just choose a couple in case one is down or set up a vip or dns or something). -Jay On Sun, Jan 6, 2013 at 9:55 PM, Neha Narkhede wrote: > In 0.8, the producer load balances data across the Kafka brokers using a > special getMetadata API. You still need to wire in a broker.list since the > producer will use this list to talk to one of the brokers to get the > leadership information for a new topic/partition. If the leader moves over > time, the produce request will fail which is when the producer will > re-issue the getMetadata request again. So zk.connect is not required > anymore. > > Thanks, > Neha > > > On Sun, Jan 6, 2013 at 9:08 PM, Jun Guo -X (jungu - CIIC at Cisco) < > jungu@cisco.com> wrote: > > > Hi all, > > I find that in Kafka 0.72, we can specify either zk.connect or > > broker.list. But in Kafka 0.8, we can only specify broker.list ,and we > > can't specify zk.connect without specifying broker.list. I think, in this > > case, we can't balance producer through zookeeper. If anyone use Kafka > 0.8, > > or have some understanding with that? > > Many thanks! > > Best Regard > > > > > --047d7b15aa5bf2494c04d2b50af1--