Thank-you Andrei! Will try this out. On Fri, Oct 26, 2012 at 3:22 PM, Andrei Savu <[email protected]> wrote: > Yep. You can do this using the following hack: > > whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker, 5 > hadoop-datanode+hadoop-tasktracker, 5 > hadoop-datanode+hadoop-tasktracker+noop # notice "+noop" > > whirr.templates.hadoop-datanode+hadoop-tasktracker+noop.aws-ec2-spot-price=0.15 > > Cheers, > > -- Andrei Savu / axemblr.com > > > On Fri, Oct 26, 2012 at 8:14 PM, Aamer Akhter <[email protected]> wrote: >> >> I would like to have a mix of always running compute nodes as well as >> spot-pricing nodes (that have a much higher chance of being killed) in >> a whirr cluster. >> >> Is there a way of having this kind of distinction? >> >> -- >> Aamer Akhter / [email protected] > >
-- Aamer Akhter / [email protected]
