[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-06-16 (世界標準時間)。"],[[["Cloud Composer 2 environments automatically scale the number of workers based on the demands of executed DAGs and tasks, increasing workers during heavy loads and removing them during inactivity."],["The environment's scaling is governed by the Scaling Factor Target metric, which considers the current worker count, queued tasks, idle workers, and the `celery.worker_concurrency` Airflow setting."],["Cloud Composer 2 utilizes three GKE autoscalers (Horizontal Pod Autoscaler, Cluster Autoscaler, and Node auto-provisioning) to automatically adjust the number of nodes, machine types, and workers in the environment's cluster."],["In addition to autoscaling, users can manually adjust the CPU, memory, and disk limits for schedulers, web servers, and workers to vertically scale the environment, and they can also choose the environment size to control the managed Cloud Composer infrastructure."],["Cloud Composer 2 allows for the configuration of multiple Airflow schedulers (HA scheduler) to be used simultaneously, but the number of schedulers is not automatically scaled by the system."]]],[]]
