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 BA14F10123 for ; Mon, 17 Jun 2013 16:22:58 +0000 (UTC) Received: (qmail 51496 invoked by uid 500); 17 Jun 2013 16:22:58 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 51437 invoked by uid 500); 17 Jun 2013 16:22:57 -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 51430 invoked by uid 99); 17 Jun 2013 16:22:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jun 2013 16:22:57 +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 (nike.apache.org: domain of manikumar.reddy@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-wg0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jun 2013 16:22:51 +0000 Received: by mail-wg0-f43.google.com with SMTP id z11so2570244wgg.10 for ; Mon, 17 Jun 2013 09:22:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=m7ZCguR4fgwiTDtb/DJyxCimQcxQKySwSzJ5ssXG0Oo=; b=SwAdScdMM+GV3lXbWLzTF7Hy1ETVg5qQ7yMyL0CTyZwAXUHQHFoo6mx/G3jGTzyA6f YB4jRfSIiq+YMdzlesrY1bwLv5xZQgfjtstKC8TQHTF2nKGlMGRh3rqip9/0OSpf3L+K u2/My9/OvyUnZHGbjJrjepcE1smDMnQLfDBUBa+Olb4AGCizqHgZ3uznHomzYhsD4071 0YUk1u5O3bvpRczY1s41SrSYg2D2UKriImCzT6BtHAxeaDjEtx1qOKhhf86c2/AzYQEG TS2WnvOg1FrwNsR9Jos45KKX15TWacLsCKkYO2BkiyZGOGpc4Jm+f0+jZAjy2PmrNX9R 3t6g== MIME-Version: 1.0 X-Received: by 10.194.179.33 with SMTP id dd1mr8318191wjc.51.1371486150868; Mon, 17 Jun 2013 09:22:30 -0700 (PDT) Sender: manikumar.reddy@gmail.com Received: by 10.194.235.132 with HTTP; Mon, 17 Jun 2013 09:22:30 -0700 (PDT) In-Reply-To: References: Date: Mon, 17 Jun 2013 21:52:30 +0530 X-Google-Sender-Auth: W84VBrJ3SYv6LxohU0GncU7kaEM Message-ID: Subject: Re: Controller fault tolerance From: Manikumar Reddy To: user@helix.incubator.apache.org Content-Type: multipart/alternative; boundary=089e013d0f80d6443604df5c00c0 X-Virus-Checked: Checked by ClamAV on apache.org --089e013d0f80d6443604df5c00c0 Content-Type: text/plain; charset=ISO-8859-1 Hi Kishore, Thanks for the quick response. Regards, Kumar On Mon, Jun 17, 2013 at 8:18 PM, kishore g wrote: > Hi Kumar, > > You can start multiple controllers and only one of them will be active and > rest of them will be in standby mode. If the active controller fails, one > of the standby will become active and start managing the cluster. > > You can start the controllers either using command line or > programmatically. > > command line > > ./run-helix-controller.sh --zkSvr localhost:2199 --cluster > > using Helix api > > controllerManager = HelixControllerMain.startHelixController(zkAddress, > clusterName, "controller", HelixControllerMain.STANDALONE); > > Hope this helps. > > thanks, > Kishore G > > > > > On Mon, Jun 17, 2013 at 7:01 AM, Manikumar Reddy wrote: > >> Hi, >> >> I am trying to understand the Helix Controller/Cluster manager fault >> tolerance mechanism. >> Single Controller will become Single-Point-Failure. So what are the >> available options/techniques to >> achieve controller fault tolerance? Any pointers/recipes/code snippets? >> >> Regards, >> Kumar > > > --089e013d0f80d6443604df5c00c0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Kishore,

Thanks for the quick response.

Regards,
Kumar<= br>
On Mon, Jun 17, 2013 at 8:18 PM, kishore = g <g.kishore@gmail.com> wrote:
Hi Kumar,

You can start multiple controllers and only one of them will be active an= d rest of them will be in standby mode. If the active controller fails, one= of the standby will become active and start managing the cluster.

You can start the controllers either using command line= or programmatically.

command line
./run-helix-<=
span style=3D"color:rgb(0,0,0)">controller.sh --zkSvr l=
ocalhost:2199 <=
span style=3D"color:rgb(102,102,0)">--cluster <clustername>
using Helix api
controllerManager =3D HelixControllerMain.startHelixC=
ontroller(zkAddress=
,=




=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0cluster=
Name, "controller", HelixControllerMain.STANDALONE);





Hope thi=
s helps.
=
= thanks,<= /span>
Kishore = G


--089e013d0f80d6443604df5c00c0--