Support Questions

Find answers, ask questions, and share your expertise

Enable Auto-scaling through Cloudbreak UI

Expert Contributor

Hi All,

We have configured HDP 2.6 cluster using Cloudbreak and want to test Auto-scaling feature. When we try to enable Auto-scaling through Cloubreak UI, it is failing with below error:

"Could not create Periscope cluster: Cluster exists for the same Cloudbreak stack id and Ambari Host"

Could you please let us know how can we resolve this.

Note: We are managing more than one cluster through Cloudbreak.

5 REPLIES 5

Expert Contributor

@Shyam Shaw

Can please give us more context? Which version are you using ?

Br,

R

Expert Contributor

Hi, @rdoktorics

We are using Cloubreak 1.16.4 (latest). There was no issue in configuring the cluster but while enabling Auto-scaling we are getting above error.

At first, we thought that it might be because of Role which we are using but we do have all the required permissions to launch a cluster. Not sure what is the cause.

Expert Contributor

Can you please contact with our support team and raise an issue. We need some application log and I don't want to share here.

Br,

R

Expert Contributor

Hi, @rdoktorics

I was able to enable to AutoScaling through Cloudbreak UI.

-Stopped Cluster using Cloudbreak UI.

-Stopped Cloudbreak Instance using AWS console.

-Started Cloudbreak Instance.

-Started Cluster using Cloudbreak UI.

This time it worked. Still not sure about the root cause of this issue.

As I mentioned earlier, we are managing two clusters (hdp26-edw-etl and hdp27-edw-etl) with Cloudbreak. Both the cluster were up and running when we tried to enable AutoScaling. Could that be the reason because now only hdp27-edw-etl is up and running.

Same here. We are also managing two clusters with Cloudbreak v1.16.5. I initially couldn't enable Autoscaling when I clicked "enable" button of "autoscaling SLA policies" tab, getting the same error message. The problem resolved only after taking exactly the same steps @Shyam Shaw took.

FYI, you don't necessarily restart the Cloudbreak instance - just need to restart the cloudbreak related containers by "cbd restart" command