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 B9AA811CB1 for ; Fri, 21 Feb 2014 05:58:58 +0000 (UTC) Received: (qmail 93272 invoked by uid 500); 21 Feb 2014 05:58:58 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 93188 invoked by uid 500); 21 Feb 2014 05:58:53 -0000 Mailing-List: contact user-help@helix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.apache.org Delivered-To: mailing list user@helix.apache.org Received: (qmail 93175 invoked by uid 99); 21 Feb 2014 05:58:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Feb 2014 05:58:52 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of osgigeek@gmail.com designates 209.85.220.173 as permitted sender) Received: from [209.85.220.173] (HELO mail-vc0-f173.google.com) (209.85.220.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Feb 2014 05:58:45 +0000 Received: by mail-vc0-f173.google.com with SMTP id ld13so2833141vcb.32 for ; Thu, 20 Feb 2014 21:58:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/MckW4lv9COMK20HPr8fuo/4u4wPWKZzvB7Li4ZPnTg=; b=L6vCr+MSeRAjSrxsr70ArJSLI0fb95TgOqoac6vAe82dBivXhSZrpApDfDTVAw/8EB PQ49ID3RljHgO/lHqWUD/DkQTUSNRLJgyjOl7Uqhh1hGcBciQ3QVbLRhEnYilWnjELVg N86n5ZodhvOG2k+37nkcDKcasl+IUC67qgaxk/XkoziJtyAFbJT6ZPXh9d4JHfhwQzxZ 7emY2vKljZB1C+aId9tnTGe5PLz0kzs0ASHOGLt2XPYuD3oagyy9eL3e/h9nyfnw5zv3 z4tLMIscBZ5WaT2utivbi23X1WQLJ3FWX1qoAQwSIkGJagPlUnPgBip4X7GEEO5B1HpP Pj6Q== MIME-Version: 1.0 X-Received: by 10.221.2.138 with SMTP id nu10mr3644505vcb.52.1392962304573; Thu, 20 Feb 2014 21:58:24 -0800 (PST) Received: by 10.220.90.80 with HTTP; Thu, 20 Feb 2014 21:58:24 -0800 (PST) Date: Thu, 20 Feb 2014 21:58:24 -0800 Message-ID: Subject: Helix 0.6.2: Resetting or removing a resource From: Sandeep Nayak To: user@helix.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on 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