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 A6C60109E1 for ; Thu, 6 Mar 2014 21:53:42 +0000 (UTC) Received: (qmail 66453 invoked by uid 500); 6 Mar 2014 21:53:41 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 66369 invoked by uid 500); 6 Mar 2014 21:53:41 -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 66362 invoked by uid 99); 6 Mar 2014 21:53:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 21:53:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of g.kishore@gmail.com designates 74.125.82.47 as permitted sender) Received: from [74.125.82.47] (HELO mail-wg0-f47.google.com) (74.125.82.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 21:53:36 +0000 Received: by mail-wg0-f47.google.com with SMTP id x12so3985190wgg.6 for ; Thu, 06 Mar 2014 13:53:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8L/UziKxanLTsLf7SrAs8nCNTGHw3RGK3zCe3LkZ62c=; b=tX9wdE397u4/F5ypzFWMlkcZz0rM0iXC29+7+/afb9d67GfI+lpsRTZzUOtlYZY2wq BrVcU7zyBMo+w+h+0KqV0YI3I7t88cCtFthyZZ10w6Yv5MMr7yB9yuf90WuBHWOR7f70 OLrhw+oALQuhOzrIqBa+aimxqi9+f3nwFymDwSFomd4lX8tyd5tYHXSY40klelXuHeb/ DU131zBJKSk5QbrncylkoYOvPxf96R3prcay/1Ta1LEkrYrzNJ88XBet/fuCvButpRdi gtzQOz4IPIHPjV7xTzv3ygUrpNSiW6RZ8M5kN+esIwSKe5xwC81LhJvkiDh1eBJVT7kt xRcw== MIME-Version: 1.0 X-Received: by 10.194.186.170 with SMTP id fl10mr5358974wjc.67.1394142795556; Thu, 06 Mar 2014 13:53:15 -0800 (PST) Received: by 10.194.78.143 with HTTP; Thu, 6 Mar 2014 13:53:15 -0800 (PST) In-Reply-To: <5318771A.50309@gmail.com> References: <5318771A.50309@gmail.com> Date: Thu, 6 Mar 2014 13:53:15 -0800 Message-ID: Subject: Re: Apache Helix From: kishore g To: Leonard Kramer , "user@helix.apache.org" Content-Type: multipart/alternative; boundary=047d7bb70892186ba704f3f72a91 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb70892186ba704f3f72a91 Content-Type: text/plain; charset=ISO-8859-1 + user On Thu, Mar 6, 2014 at 5:24 AM, Leonard Kramer < leonard.alexander.kramer@googlemail.com> wrote: > Hi Mr. Kishore, > > my name is Leonard Kramer and I've found your mail-address in the Apache > Helix mailing list. I'm currently evaluating Apache Helix for the > cluster-management of ZooKeeper itself. The ultimate goal is to create an > autonomous zookeeper-service with its own migration-strategies and self > repair functions. > > For the monitoring and reaction to outages of nodes I want to use Apache > Helix, because it already uses ZooKeeper as its primary coordination & > data-store. In the mailing-list you have answered a thread for the > differences between norbert and helix and mentioned that "Failure: When a > node fails, you have multiple options [...] #3 Start a new node and assign > the partitions to that new node. [...] #3 feature is work in progress and > is possible if the deployment system is flexible and allows starting up > process dynamically". > While studying Helix I couldn't find any more information regarding this > feature. All I could find was the blog post "http://engineering.linkedin. > com/cluster-management/auto-scaling-apache-helix-and-apache-yarn", which > I think is too complex for my specific use-case. > > Can you please provide me with more information regarding the self repair > of a helix cluster? Is the helix-controller capable of invoking logic for > starting additional nodes? My plan is to use Jclouds in addition to the > cloud-controller and start a new node when the helix-controller notices a > node's failure. Is this possible? > > Thank you for your help and have nice day. > Greetings from Germany > > Leo > --047d7bb70892186ba704f3f72a91 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
+ user




On Thu, Mar 6, 2014 at 5:24 AM, Leonard Kramer <leonard.alexander.kramer@googlemail.com> wr= ote:
Hi Mr. Kishore,

my name is Leonard Kramer and I've found your mail-address in the Apach= e Helix mailing list. I'm currently evaluating Apache Helix for the clu= ster-management of ZooKeeper itself. The ultimate goal is to create an auto= nomous zookeeper-service with its own migration-strategies and self repair = functions.

For the monitoring and reaction to outages of nodes I want to use Apache He= lix, because it already uses ZooKeeper as its primary coordination & da= ta-store. In the mailing-list you have answered a thread for the difference= s between norbert and helix and mentioned that "Failure: When a node f= ails, you have multiple options [...] #3 Start a new node and assign the pa= rtitions to that new node. [...] #3 feature is work in progress and is poss= ible if the deployment system is flexible and allows starting up process dy= namically".
While studying Helix I couldn't find any more information regarding thi= s feature. All I could find was the blog post "http://engineering.linkedin.com/cluster-man= agement/auto-scaling-apache-helix-and-apache-yarn", = which I think is too complex for my specific use-case.

Can you please provide me with more information regarding the self repair o= f a helix cluster? Is the helix-controller capable of invoking logic for st= arting additional nodes? My plan is to use Jclouds in addition to the cloud= -controller and start a new node when the helix-controller notices a node&#= 39;s failure. Is this possible?

Thank you for your help and have nice day.
Greetings from Germany

Leo

--047d7bb70892186ba704f3f72a91--