Mailing-List: contact user-help@helix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@helix.apache.org
Received-SPF: pass (nike.apache.org: domain of osgigeek@gmail.com designates
 209.85.128.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BAY173-W5014C59A28D679F8C99BB6ED850@phx.gbl>
References: 
 <CAJT9z6N998Wx73cFGDgA-pR01ToAWDkgk3qTyA9dL=h+3m6v1w@mail.gmail.com>
	<BAY173-W5014C59A28D679F8C99BB6ED850@phx.gbl>
Date: Thu, 20 Feb 2014 22:06:03 -0800
Message-ID: 
 <CAJT9z6NrijM_noOq5t+nL9BivQn5qpnjB1iX+O+V_ggBscv8Vw@mail.gmail.com>
Subject: Re: Helix 0.6.2: Resetting or removing a resource
From: Sandeep Nayak <osgigeek@gmail.com>
To: user@helix.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Does it need time to remove the resource? I tried dropResource and the
very next call I invoke addResource to see if I can add it again and
the add call fails with the exception

org.apache.helix.HelixException: Skip the operation. Resource ideal
state directory already exists:/cluster/IDEALSTATES/resource-name

On Thu, Feb 20, 2014 at 10:03 PM, Kanak Biscuitwala <kanak.b@hotmail.com> wrote:
> Hi Sandeep,
>
> dropResource is correct. resetResource takes resources in error state and resets them to the initial state.
>
> Kanak
> ----------------------------------------
>> Date: Thu, 20 Feb 2014 21:58:24 -0800
>> Subject: Helix 0.6.2: Resetting or removing a resource
>> From: osgigeek@gmail.com
>> To: user@helix.apache.org
>>
>> Hi guys,
>>
>> Wanted to check what is the correct API for removing a resource so
>> that it is unavailable on any of the nodes?
>>
>> I see HelixAdmin.dropResource and HelixAdmin.resetResource. What is
>> the right API to use to remove a resource entirely from the cluster?
>>
>> Thanks,
>>
>> Sandeep