Return-Path: 
 <user-return-140-apmail-helix-user-archive=helix.apache.org@helix.incubator.apache.org>
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 907A0FAFF
	for <apmail-helix-user-archive@minotaur.apache.org>;
 Thu,  2 May 2013 16:23:23 +0000 (UTC)
Received: (qmail 60966 invoked by uid 500); 2 May 2013 16:23:23 -0000
Delivered-To: apmail-helix-user-archive@helix.apache.org
Received: (qmail 60922 invoked by uid 500); 2 May 2013 16:23:23 -0000
Mailing-List: contact user-help@helix.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@helix.incubator.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@helix.incubator.apache.org>
List-Post: <mailto:user@helix.incubator.apache.org>
List-Id: <user.helix.incubator.apache.org>
Reply-To: user@helix.incubator.apache.org
Delivered-To: mailing list user@helix.incubator.apache.org
Received: (qmail 60915 invoked by uid 99); 2 May 2013 16:23:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 16:23:23 +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 vinayakb@gmail.com designates
 209.85.220.46 as permitted sender)
Received: from [209.85.220.46] (HELO mail-pa0-f46.google.com) (209.85.220.46)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 16:23:15 +0000
Received: by mail-pa0-f46.google.com with SMTP id fa10so442660pad.5
        for <user@helix.incubator.apache.org>;
 Thu, 02 May 2013 09:22:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:message-id:date:from:user-agent:mime-version:to:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=axlCe/BtT+4actkRdrPYoPgyZ6rXc6PkpOM9+s+SPIM=;
        b=vX1plxsac3C6AKktzfNwwKBrr3SoCRO4Pa6Z75xc+wWFNrLpPEZG7+5d9Gz5zlKK34
         hI+DivbjEsqoTv+yftSzXjbIQyrq93YUHwVQ3jiSforaK4ltNdzj0dHACqvxCafTypTT
         TcaR85aRQnMfWRUfBnMJWQCMK/6UgEO0JxN1ky9ZL9B1AHX89HNN1PLUacyPshc3Usic
         F4vf/ntjckq7gnCeK3o9DBsD0PS5pO+Ow8EI97ofQyvQcmKN8Ar7MW8fdx4YOWLQwcaE
         kOLQ6lQSy9TGf+FG63WEKQUXqcoTxeDmF9dqaSZLNyYhXE/yMtneWd5WS4O1uWoEhGGp
         k7kA==
X-Received: by 10.68.171.196 with SMTP id aw4mr9665284pbc.78.1367511774509;
        Thu, 02 May 2013 09:22:54 -0700 (PDT)
Received: from netbook.local (210.200-157-192.rdns.scalabledns.com.
 [192.157.200.210])
        by mx.google.com with ESMTPSA id
 li15sm8888638pab.2.2013.05.02.09.22.52
        for <user@helix.incubator.apache.org>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 02 May 2013 09:22:53 -0700 (PDT)
Message-ID: <518292DC.2030102@gmail.com>
Date: Thu, 02 May 2013 09:22:52 -0700
From: Vinayak Borkar <vinayakb@gmail.com>
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: Some newbie questions
References: <279FC09E-24EF-4F29-8A3C-D19DC4DD7559@redhat.com>
 <51828F0B.7020508@gmail.com>
 <5FA9DB4F-AE1A-4249-B006-3E9431CBFD78@redhat.com>
In-Reply-To: <5FA9DB4F-AE1A-4249-B006-3E9431CBFD78@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Looking at the signature of HelixAdmin.enablePartition, I see this:

   void enablePartition(boolean enabled,
                        String clusterName,
                        String instanceName,
                        String resourceName,
                        List<String> partitionNames);



So when you disable the partition, you are doing so only on a perticular 
instance. So my understanding is that the same partition at other 
instances will participate in an election to come out of standby.

Vinayak


On 5/2/13 9:14 AM, Alexandre Porcelli wrote:
> Hi Vinayak,
>
>   Thanks for your quick answer, but I don't think this would be the case... once the partition `represents` the locked resource, so If i disable it no other instance in the cluster will be able to be promoted to Leader (at this point other nodes should be in standby just waiting to be able to acquire the lock - in other words, become Leader).
>   Anyway thanks for your support.
>
> Cheers,
> ---
> Alexandre Porcelli
> porcelli@redhat.com
>
>
> On May 2, 2013, at 1:06 PM, Vinayak Borkar <vinayakb@gmail.com> wrote:
>
>>>
>>>   1. I'm using a LeaderStandby in order to build a single global lock on my cluster, it works as expected.. but in order to release the lock I have to put the current leader in standby... I could achieve this by disabling the current instance. It works, but doing this I loose (at least seems to be) the ability to send/receive user defined messages. I'd like to know if it's possible to, via an api call, force a transition from Leader to Standby without disable an instance.
>>
>> I am a newbie to Helix too and I had a similar question a few days ago. Have you looked into disabling the resource by using the disablePartition() call in HelixAdmin using a partition number of 0? This should disable just the resource without impacting the instance.
>>
>> Vinayak
>>
>>>
>>>   2. I've been taking a quick look on Helix codebase, more specific on ZooKeeper usage. Seems that you're using ZooKeeper as a default implementation, but Helix architecture is not tied to it, right? I'm asking this, because I'm interested to implement (in a near future) a different backend (Infinispan).
>>>
>>> That's it for now...  thanks in advance.
>>>
>>> Cheers,
>>> ---
>>> Alexandre Porcelli
>>> porcelli@redhat.com
>>>
>>
>
>