Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 327237C3B for ; Mon, 29 Aug 2011 14:10:52 +0000 (UTC) Received: (qmail 43989 invoked by uid 500); 29 Aug 2011 14:10:49 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 43674 invoked by uid 500); 29 Aug 2011 14:10:47 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 43666 invoked by uid 99); 29 Aug 2011 14:10:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2011 14:10:47 +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 tucu@cloudera.com designates 209.85.218.48 as permitted sender) Received: from [209.85.218.48] (HELO mail-yi0-f48.google.com) (209.85.218.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2011 14:10:40 +0000 Received: by yib17 with SMTP id 17so4630005yib.35 for ; Mon, 29 Aug 2011 07:10:19 -0700 (PDT) Received: by 10.43.50.69 with SMTP id vd5mr4970580icb.56.1314627019475; Mon, 29 Aug 2011 07:10:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.223.202 with HTTP; Mon, 29 Aug 2011 07:04:45 -0700 (PDT) In-Reply-To: <004901cc6642$ddb2a990$9917fcb0$@com> References: <003d01cc6631$0e721550$2b563ff0$@com> <004901cc6642$ddb2a990$9917fcb0$@com> From: Alejandro Abdelnur Date: Mon, 29 Aug 2011 07:04:45 -0700 Message-ID: Subject: Re: Oozie on the namenode server To: oozie-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec5299a03820ca804aba5743e X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5299a03820ca804aba5743e Content-Type: text/plain; charset=ISO-8859-1 [Moving thread to Oozie aliases and hadoop's alias to BCC] Avi, Currently you can have a cold standby solution. An Oozie setup consists of 2 systems, a SQL DB (storing all Oozie jobs state) and a servlet container (running Oozie proper). You need you DB to be high available. You need to have a second installation of Oozie configured identically to the running on stand by. If the running Oozie fails, you start the second one. The idea (we once did a prototype using Zookeeper) is to eventually support a multithreaded Oozie server, that would give both high-availability and horizontal scalability. Still you'll need a High Available DB. Thanks. Alejandro On Mon, Aug 29, 2011 at 4:57 AM, Avi Vaknin wrote: > Hi, > I have one more question about Oozie, > Is there any suggested high availability solution for Oozie ? > Something like active/passive or active/active solution. > Thanks. > > Avi > > -----Original Message----- > From: Harsh J [mailto:harsh@cloudera.com] > Sent: Monday, August 29, 2011 2:20 PM > To: common-user@hadoop.apache.org > Subject: Re: Oozie on the namenode server > > Avi, > > Should be OK to do so at this stage. However, keep monitoring loads on > the machines to determine when to move things out to their own > dedicated boxes. > > On Mon, Aug 29, 2011 at 3:20 PM, Avi Vaknin wrote: > > Hi All, > > > > I want to install Oozie and I wonder if it is OK to install it on the > name > > node or maybe I need to install dedicated server to it. > > > > I have a very small Hadoop cluster (4 datanodes + namenode + secondary > > namenode). > > > > Thanks for your help. > > > > > > > > Avi > > > > > > > > -- > Harsh J > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1392 / Virus Database: 1520/3864 - Release Date: 08/28/11 > > --bcaec5299a03820ca804aba5743e--