Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Is it possible to spin-up and spin-down infrastructure on a set schedule using blueprints via cloudbreak?

Solved Go to solution

Is it possible to spin-up and spin-down infrastructure on a set schedule using blueprints via cloudbreak?

New Contributor

Hi there,

We are looking to use ephemeral hadoop cluster/infrastructure approach for one of our applications. Assuming the application runs at 6am/6pm and it runs for around 30min each time. We want to bring up the infrastructure with a particular blueprint for the application then let the application run end-to-end and then bring it down until the next run 12 hours later.

Does cloudbreak provide this feature and if so can someone help us with where is a resource/documentation for it? Or we need to have a small cluster running all the time with minimum nodes and scale up/down depending on application schedule with time based autoscaling?

Thanks.!

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Is it possible to spin-up and spin-down infrastructure on a set schedule using blueprints via cloudbreak?

@Amey Hegde

There are the two ways to achieve this as follows:

  • The most cost effective way of doing this is by using Cloudbreak shell to automate the cluster create and tear-down and schedule it with e.g. cron. You can even start the application with a post recipe.
  • The other way is using time based autoscaling and keep the minimum nodes alive. Post recipes will run on upscale. In this case consider that data nodes should not be subject of downscale.

Hope this helps!

1 REPLY 1

Re: Is it possible to spin-up and spin-down infrastructure on a set schedule using blueprints via cloudbreak?

@Amey Hegde

There are the two ways to achieve this as follows:

  • The most cost effective way of doing this is by using Cloudbreak shell to automate the cluster create and tear-down and schedule it with e.g. cron. You can even start the application with a post recipe.
  • The other way is using time based autoscaling and keep the minimum nodes alive. Post recipes will run on upscale. In this case consider that data nodes should not be subject of downscale.

Hope this helps!