[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 <[email protected]> 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:[email protected]] > Sent: Monday, August 29, 2011 2:20 PM > To: [email protected] > 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 <[email protected]> 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 > >
