Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A557BFFE0 for ; Wed, 8 May 2013 22:53:41 +0000 (UTC) Received: (qmail 59160 invoked by uid 500); 8 May 2013 22:53:41 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 59130 invoked by uid 500); 8 May 2013 22:53:41 -0000 Mailing-List: contact user-help@helix.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.incubator.apache.org Delivered-To: mailing list user@helix.incubator.apache.org Received: (qmail 59111 invoked by uid 99); 8 May 2013 22:53:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 22:53:41 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lushi04@gmail.com designates 209.85.210.174 as permitted sender) Received: from [209.85.210.174] (HELO mail-ia0-f174.google.com) (209.85.210.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 22:53:34 +0000 Received: by mail-ia0-f174.google.com with SMTP id j3so1239771iae.33 for ; Wed, 08 May 2013 15:53:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=Foczrk/GXJJbZvIV9RVJaDjRk3MA43n5QghxAkcaaS0=; b=X9w0fE1iOQrw+0qY926thH6LuFT9DnadniGNv8HoqOQYpruxI5jtfKqmoOI0g68qIi I2J+WuwPACC9bAi25eHj0fBQGdC2K+EFP6/se4jljjhJNqCxWySB64cDyZwvBd6mT2Gr 2BJJAkd9uyOQB+MHqk4lbyZsM9xIQXgqRcveJ5AVvflukHzBPjeypqbsqsYaJR2gNiPR kqP3FnUD+xsAS/aDZnLMK4V+LsWhYZxZXsyoODztwEm6dhSUVBo/pvwNfAjCQvtfZZsh ttmAx5+a3d6K372cTQhGDTz2OZkZq/FvcbYYi5imA0VihoMX5iiqmHWqJfcIDaj5BfDu qh5Q== MIME-Version: 1.0 X-Received: by 10.50.27.37 with SMTP id q5mr1896874igg.52.1368053593811; Wed, 08 May 2013 15:53:13 -0700 (PDT) Received: by 10.64.13.80 with HTTP; Wed, 8 May 2013 15:53:13 -0700 (PDT) In-Reply-To: References: <518ACE13.70100@gmail.com> Date: Wed, 8 May 2013 15:53:13 -0700 Message-ID: Subject: Re: Dropping a resource From: Shi Lu To: user@helix.incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b10c8377e339304dc3ccca0 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10c8377e339304dc3ccca0 Content-Type: text/plain; charset=ISO-8859-1 Hi Vinayak: For auto_rebalance mode resources, dropping them should trigger the same logic for the partition to go into OFFLINE state then disappear, just like dropping a resource in AUTO mode. Can you share the participant/controller log if there are any? Thanks, -shi On Wed, May 8, 2013 at 3:38 PM, kishore g wrote: > Hi Vinayak, > > Thats probably a bug. Do you have a test case? > > thanks, > Kishore G > > > On Wed, May 8, 2013 at 3:13 PM, Vinayak Borkar wrote: > >> Hi, >> >> >> When I create a resource and rebalance it, the participants receive >> transitions for that resource and its partitions become masters. However, >> when I drop the resource from Helix (using --dropResource in helix-admin), >> I do not see any transitions from master -> slave -> dropped. In fact >> --listResourceInfo shows the external view of the resource partitions as >> being in the master state. >> >> What is the process to be followed in auto_rebalance mode to have the >> resources deleted from the entire cluster? >> >> Thanks, >> Vinayak >> > > --047d7b10c8377e339304dc3ccca0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Vinayak:

For auto_rebalance mo= de resources, dropping them should trigger the same logic for the partition= to go into OFFLINE state then disappear, just like dropping a resource in = AUTO mode. Can you share the participant/controller log if there are any?= =A0

Thanks,
-shi


On Wed, May 8, 2= 013 at 3:38 PM, kishore g <g.kishore@gmail.com> wrote:
Hi Vinayak,

<= div>Thats probably a bug. Do you have a test case?

thanks,
Kishore G


On Wed, May 8, 2013 at 3:13 PM, Vinayak Borkar <vinayakb@gmail.com>= ; wrote:
Hi,


When I create a resource and rebalance it, the participants receive transit= ions for that resource and its partitions become masters. However, when I d= rop the resource from Helix (using --dropResource in helix-admin), I do not= see any transitions from master -> slave -> dropped. In fact --listR= esourceInfo shows the external view of the resource partitions as being in = the master state.

What is the process to be followed in auto_rebalance mode to have the resou= rces deleted from the entire cluster?

Thanks,
Vinayak


--047d7b10c8377e339304dc3ccca0--