edit-icon download-icon

What if the auto scaling rule does not take effect

Last Updated: Dec 29, 2017

If your created container auto scaling rule or node auto scaling rule does not take effect, you can perform troubleshooting according to the following methods.

View monitoring metrics, and confirm that monitoring metrics have data and the data reaches the configured threshold for a certain period of time

  • View the monitoring metrics of container auto scaling

    1. Click Services in the left-side navigation pane.

    2. Select the cluster in which the service resides from the Cluster list.

    3. Click Monitor at the right of the service.

      You are redirected to the CloudMonitor console. You can view the container monitoring information. Confirm that monitoring metrics have data and the data reaches the configured threshold for a certain period of time.

      When determining whether the monitoring metric value exceeds the configured upper limit or lower limit, Container Service uses the average value of the monitoring metrics (namely, the average CPU usage and the average memory usage) within a sample period (one minute). Container Service triggers scaling only when the average monitoring metrics of three consecutive sample periods all exceed the configured upper limit or lower limit so as to avoid frequent scaling caused by monitoring data jitter.

      1

  • View the monitoring metrics of node auto scaling

    1. Click Clusters in the left-side navigation pane.

    2. Click Monitor at the right of the cluster.

      You are redirected to the CloudMonitor console. You can view the cluster monitoring information. Confirm that monitoring metrics have data and the data reaches the configured threshold for a certain period of time.

      When determining whether the monitoring metric value exceeds the configured upper limit or lower limit, Container Service uses the average value of the monitoring metrics (namely, the average CPU usage and the average memory usage) within a sample period (one minute). Container Service triggers scaling only when the average monitoring metrics of three consecutive sample periods all exceed the configured upper limit or lower limit so as to avoid frequent scaling caused by monitoring data jitter.

      1

If no monitoring data is displayed

Check the following possibilities:

  • Whether or not the monitoring service (acsmonitoring) is correctly installed (whether or not the status and number of containers are correct). If not, redeploy the monitoring service (acsmonitoring).

  • Whether or not the cluster Agent is in the latest version. If not, upgrade the cluster Agent. For more information, see Upgrade Agent.

  • Whether or not the monitoring service (acsmonitoring) is in the latest version. If not, upgrade the monitoring service (acsmonitoring). For more information, see Upgrade system services.

View monitoring alarm rules and status, and confirm the rules are created and in the correct status

  1. Log on to the CloudMonitor console.

  2. Click Cloud Service Monitoring > Container Service in the left-side navigation pane.

  3. Click View All Rules on the Clusters page to view the alarm rules automatically configured by auto scaling.

    1

If no monitoring alarm rule is displayed

  • Update the RAM authorization information in the cluster by completing the following steps:

    1. Log on to the Container Service console.

    2. Click Clusters in the left-side navigation pane.

    3. Click More at the right of the cluster.

    4. Select Update RAM Authorization Information from the list.

    Activate the RAM service before updating the RAM authorization information. Otherwise, the system reports an error.

  • Check the following possibilities:

    • Whether or not the monitoring service (acsmonitoring) is correctly installed (whether or not the status and number of containers are correct). If not, redeploy the monitoring service (acsmonitoring).

    • Whether or not the cluster Agent is in the latest version. If not, upgrade the cluster Agent. For more information, see Upgrade Agent.

    • Whether or not the monitoring service (acsmonitoring) is in the latest version. If not, upgrade the monitoring service (acsmonitoring). For more information, see Upgrade system services.

View alarm history

If the status of an alarm rule is abnormal (in the Alarm status) on the Alarm Rules page, you can view the alarm history of this rule to locate the problem.

Under Actions, click View at the right of the alarm rule.

Click the Alarm Logs tab, and you can select the time to view the alarms occurred within specified time period.

Thank you! We've received your feedback.