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 3EC2EFBED for ; Thu, 18 Apr 2013 06:01:23 +0000 (UTC) Received: (qmail 22919 invoked by uid 500); 18 Apr 2013 06:01:23 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 22866 invoked by uid 500); 18 Apr 2013 06:01:22 -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 22856 invoked by uid 99); 18 Apr 2013 06:01:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 06:01:22 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FORGED_YAHOO_RCVD,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.138.91.92] (HELO nm16-vm2.bullet.mail.ne1.yahoo.com) (98.138.91.92) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 06:01:14 +0000 Received: from [98.138.90.52] by nm16.bullet.mail.ne1.yahoo.com with NNFMP; 18 Apr 2013 06:00:54 -0000 Received: from [98.136.44.60] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 18 Apr 2013 06:00:54 -0000 Received: from [127.0.0.1] by smtp105.prem.mail.sp1.yahoo.com with NNFMP; 18 Apr 2013 06:00:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1366264854; bh=iSOSDpGtMLN4/qjM+gFAQb7DjqDPjkFbi22zdn4xDMc=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=BZJfV+MsMFiGZdCsWLWhi66qFzGe+jKOOtIkO3gAy1W/dWLE2GnpBVWqHcYi0F1POAlmonWhr7rzlysLGBDbJvFYzY7bg0gHQGkN5UVsSSGNkXDWrRzsVc03Oos0/lNSqs4HkHLT5KqyJSVXJN50+KdGqejumco10sBiTMAXxZY= X-Yahoo-Newman-Id: 15529.56773.bm@smtp105.prem.mail.sp1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 50NN1r4VM1kapQgq65Y.fweZgrFGoiDSqDgb3_3bwOmQl0p EIPSPdt394BxuVbE6C2gHI6urtMr.8FBWUNGr0VAx3Nw67138gkzo6DKeSo6 5_MZoQjbGLRqFEg19744B8Li_BcJavdOLIHx1OEl3L3FvRzVJl8loKoCjL5u 7zUfPv188jdfSZwMcoPmuH9042VgVtT63gSRUv7NPhMaCArhgNgp1nMEYG7z WXSvmJJyaf4w3Ayinb0YkklMVieqM0dY2ZUs7ZutiO48vFKEUoWowT.NF4_4 qtFW26pJ7Mu9RolBIKAU.TAA9cbuCPb.pbEI4mDq7.xK28Re5.NFh59PQe2Y i2LuLvjmLhguKqJT6jrPceMGiNsIfKfM_UDKhUXhB8mx4SELIkoUYt6rM_L8 hBLRW0jdTjcwEKvFqiXUYogWj8ZtKABTxSCLHKs0pXLWogOxcOQUuA2GHGUK ATvthe9BIa9AsqqN2OQ-- X-Yahoo-SMTP: ZvR6Aa.swBBi9aze9_P4M914Ag-- X-Rocket-Received: from netbook.local (vborky@76.103.130.241 with plain) by smtp105.prem.mail.sp1.yahoo.com with SMTP; 17 Apr 2013 23:00:53 -0700 PDT Message-ID: <516F8C15.4030407@yahoo.com> Date: Wed, 17 Apr 2013 23:00:53 -0700 From: Vinayak Borkar User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: user@helix.incubator.apache.org Subject: Re: Resource Partition Failure References: <516F767F.80803@yahoo.com> <516F8A42.6000500@yahoo.com> <72059E7F-84D7-495E-8898-5D41F1331291@mac.com> In-Reply-To: <72059E7F-84D7-495E-8898-5D41F1331291@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org That sounds more promising. Does disabling a partition trigger ideal state computation to rebalance the cluster? Ideally it would be great if the corrupted instance could move itself to the ERROR state which was then reset by possibly the controller. Is that possible? On 4/17/13 10:55 PM, Ming Fang wrote: > how about HelixAdmin.enablePartition()? > > On Apr 18, 2013, at 1:53 AM, Vinayak Borkar wrote: > >> Hi Ming Fang, >> >> >> Enable/Disable instance will take out all the resources hosted on an instance. I would like to disable only the corrupted partition on the system without impacting other resources. >> >> Thanks, >> Vinayak >> >> >> On 4/17/13 10:43 PM, Ming Fang wrote: >>> Try HelixAdmin.enableInstance() >>> >>> On Apr 18, 2013, at 12:28 AM, Vinayak Borkar wrote: >>> >>>> Hi, >>>> >>>> >>>> What is the expected way for a system to indicate to Helix that a partition of a resource has failed? >>>> >>>> Say the bits on disk of a particular partition are found to be corrupted. Is there a way to tell helix that that partition of that resource needs to "fail" without killing the whole node and hence destroying all other resources on that machine? >>>> >>>> Thanks, >>>> Vinayak >>> >>> >> > >