Mailing-List: contact user-help@helix.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@helix.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of vinayakb@gmail.com designates
 209.85.160.50 as permitted sender)
Message-ID: <518A77A5.8040303@gmail.com>
Date: Wed, 08 May 2013 09:04:53 -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: Helix Resource Config guarantees
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,


I have a fundamental question about guarantees in Helix regarding newly 
added resources and their configuration.

When I add a new resource into Helix, I need to first configure it by 
setting some properties using the ConfigAccessor. AFAICT Helix does not 
provide a way to do both the steps (add the resource and configure it) 
in one atomic step. Another thing I noticed is that addition of a new 
Resource into Helix even in AUTO_REBALANCE mode does not immediately 
trigger a External State computation. Instead I seem to need to call 
rebalance on that resource. Since I need the configuration set before 
state models at the nodes start manipulating the resource, this is 
perfect. It allows me to add a resource, configure it and then call 
rebalance so the state models do not see an unconfigured resource.

My question is if this is a guarantee provided by Helix? i.e. Is 
rebalancing of a new resource triggered ONLY by an explicit rebalance call?

I have read/heard of a rebalance timer. How do I set that value and does 
that impact rebalancing of new resources?

Thanks,
Vinayak