Support Questions
Find answers, ask questions, and share your expertise

Cloudbreak Autoscaling doesn't check all metric alarms

Solved Go to solution

Cloudbreak Autoscaling doesn't check all metric alarms

New Contributor

I created 12 metrics alarms and policy configurations based on these alarms (6 for scale out and 6 for scale in). But in cloudbreak logs I can see that only several alarms are checked and then "No scaling activity required".
Why doesn't cloudbreak check all metrics alarms? What the number of checked alarms are depend on? How can I change this behavior?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Cloudbreak Autoscaling doesn't check all metric alarms

New Contributor

The problem has been fixed in the next way:
- create all policies for scaling out first

- then create all policies for scaling in

autoscaling2.PNG

After checking first policy for scaling in (memory-used-ok) I can see "No scaling activity required" message in the log but now cloudbreak checks all my "critical" policies.

View solution in original post

2 REPLIES 2

Re: Cloudbreak Autoscaling doesn't check all metric alarms

New Contributor

The current Policy configuration for Autoscaling:
autoscaling.PNG
However in cloudbreak logs I can see:

[cb-stack-id:1] Checking metric based alert: 'memory-used-critical'
[cb-stack-id:1] Finished cronTimeEvaluator for cluster 1 in 72 ms
[cb-stack-id:1] Ambari 'alertHistory' finished in 79 ms
[cb-stack-id:1] Checking metric based alert: 'memory-used-ok'
[cb-stack-id:1] Ambari 'alertHistory' finished in 58 ms
[cb-stack-id:1] Alert: memory-used-ok is in 'OK' state since 1027.78 min(s)
[cb-stack-id:1] Ambari 'clusterHosts' finished in 350 ms
[cb-stack-id:1] No scaling activity required
[cb-stack-id:1] Finished metricEvaluator for cluster 1 in 581 ms

 

Cloudbreak checks only "memory-used-critical" and "memory-used-ok" but ignores everything else.
Cloudbreak version is 2.9.1.


Re: Cloudbreak Autoscaling doesn't check all metric alarms

New Contributor

The problem has been fixed in the next way:
- create all policies for scaling out first

- then create all policies for scaling in

autoscaling2.PNG

After checking first policy for scaling in (memory-used-ok) I can see "No scaling activity required" message in the log but now cloudbreak checks all my "critical" policies.

View solution in original post