Hi David, Sorry for the late reply. I think you are also affected by a timing issue. We are starting all the services at the same time with no coordination and sometimes (quite often) the datanode / tasktracker tries to start before the namenode / jobtracker is started.
>From my point of view this is a critical issue we need to address in 0.8.0. -- Andrei Savu / andreisavu.ro On Sat, Jan 7, 2012 at 7:07 PM, David Dundas <[email protected]> wrote: > Forgot to add I am using Whirr 0.7.0 > > Hadoop 0.20.2-cdh3u2 > > > On Sat, Jan 7, 2012 at 12:05 PM, David Dundas <[email protected]> wrote: > > > I keep on getting this error when trying to launch a cluster. > > > > I notice that the cluster unsuccessfully when I use the configuration of: > > > > whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,2 > > hadoop-datanode+hadoop-tasktracker > > > > however it everything works as expected when I use the configuration of: > > > > whirr.instance-templates=1 > > hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker > > > > So in order to make whirl work I am forced to launch the same number of > > each instance which is a bit of overkill. > > > > Thanks for any help! > > > > > > > -- > _______________________________ > > David Dundas > CEO - textingly > www.textingly.com > text DAVID to 52627 > linkedin - http://www.linkedin.com/in/daviddundas > textingly twitter: twitter.com/textingly > my twitter: twitter.com/dundas >
