From users-return-7571-apmail-kafka-users-archive=kafka.apache.org@kafka.apache.org Fri Dec 6 06:27:53 2013 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 2A6EA101E7 for ; Fri, 6 Dec 2013 06:27:53 +0000 (UTC) Received: (qmail 92798 invoked by uid 500); 6 Dec 2013 05:25:52 -0000 Delivered-To: apmail-kafka-users-archive@kafka.apache.org Received: (qmail 92760 invoked by uid 500); 6 Dec 2013 05:25:51 -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 92751 invoked by uid 99); 6 Dec 2013 05:25:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 05:25:51 +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 (athena.apache.org: domain of junrao@gmail.com designates 209.85.219.51 as permitted sender) Received: from [209.85.219.51] (HELO mail-oa0-f51.google.com) (209.85.219.51) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 05:25:46 +0000 Received: by mail-oa0-f51.google.com with SMTP id i7so262694oag.10 for ; Thu, 05 Dec 2013 21:25:26 -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=wDm6gAdqpJ5CKUhxmmDIR3NSPAwSR3/Dw70tkgfaCu4=; b=ZM9rTq5ebjUZzt0CLSvKa1nXaaEMwKujNPuHZkPLtMYfkLADpklXE8uU/qcKRPrlsO uy/HdzcwNHcYOOcsDO28aSY4rMbXVf0cnKyZA7YzAsRouR31TNYTO4SJiVL68PtbuMHn 9Hi4qxx2A/zDYiQRGI4TxQzPQFugdweiwvQhrZtOlMqUJxty7p+I+YNkw9ZqBuOjWgun fYDyqbkAyfkinv0S9eCy8MrS/BAb3mptQZiZHgNzFN2o0d9a0F5OdqRigkkgV8LDRart XYyzeAL03cF+XBu8tjn98yJFwu4uTccxKpUuH/sbMAGZ+hKtVz3cj99pvqMM3sS9ZXQ6 0GsQ== MIME-Version: 1.0 X-Received: by 10.60.62.172 with SMTP id z12mr1124459oer.4.1386307526242; Thu, 05 Dec 2013 21:25:26 -0800 (PST) Received: by 10.60.137.163 with HTTP; Thu, 5 Dec 2013 21:25:26 -0800 (PST) In-Reply-To: References: Date: Thu, 5 Dec 2013 21:25:26 -0800 Message-ID: Subject: Re: Preventing topics from appearing on specific brokers From: Jun Rao To: "users@kafka.apache.org" Content-Type: multipart/alternative; boundary=001a11c20976a6b60e04ecd6dfea X-Virus-Checked: Checked by ClamAV on apache.org --001a11c20976a6b60e04ecd6dfea Content-Type: text/plain; charset=ISO-8859-1 That's right. Remove the local log dir from brokers that you don't want to have the topic. Thanks, Jun On Thu, Dec 5, 2013 at 9:22 PM, Philip O'Toole wrote: > Interesting. So if we want to restrict it to a certain set of brokers, we > could just create the topic directories by hand on the brokers where we do > want the topic, and then bounce the service on those brokers? > > Philip > > > On Thu, Dec 5, 2013 at 9:18 PM, Jun Rao wrote: > > > In 0.7, if a topic already exists on at least one broker in a cluster, it > > won't be created on newly added brokers. > > > > Thanks, > > > > Jun > > > > > > On Thu, Dec 5, 2013 at 4:29 PM, Philip O'Toole > wrote: > > > > > Hello, > > > > > > Say we are using Zookeeper-based Producers, and we specify a topic to > be > > > written to. Since we don't specify the actual brokers, is there a way > to > > > prevent a topic from appearing on a specific broker? What if we set the > > > topic's partition count to 0 on the broker we don't want it to appear? > > > > > > Would that work? > > > > > > Thanks, > > > > > > Philip > > > > > > --001a11c20976a6b60e04ecd6dfea--