我已经配置了Cloud Composer 2
workloads_config {
worker {
cpu = 2
memory_gb = 6
storage_gb = 10
min_count = 1
max_count = 4
}
}
我无法在Terraform或GCP控制台中设置 Storage_GB
高于10。在Terraform中,我遇到了一个错误,说我无法将值设置为10GB以上。在控制台中,不可能输入大于10的值。
我使用 kubernetespoderator 失败,因为它达到了磁盘限制。
我可以看到POD被驱逐有以下错误:
POD临时的本地存储使用量超过容器的总限制10239Mi。
该作业在作曲家1上工作正常,我不记得必须在那里配置存储限制,但是作曲家1在设置环境方面有很大差异。
我找不到
有关如何在Composer 2中增加此限制的文档。我将尝试的事情:
- 尝试使用POD资源请求进行更多存储,
- 的群集上的限制
请参阅是否有一种方法可以配置Composer之外 除了显示了如何更改工人的存储空间,但没有提及10GB限制。
是否有将工人限制提高到10GB以上的标准方法?
I have configured cloud composer 2 using terraform with the following configuration:
workloads_config {
worker {
cpu = 2
memory_gb = 6
storage_gb = 10
min_count = 1
max_count = 4
}
}
I cannot set storage_gb
higher than 10, either in terraform or in the GCP console. In terraform, I get an error saying I can't set the value above 10GB. In the console, it's not possible to enter a value greater than 10.
I have one job using the KubernetesPodOperator which is failing because it hits the disk limit.
I can see the pod was evicted with the following error:
Pod ephemeral local storage usage exceeds the total limit of containers 10239Mi.
The job worked OK on Composer 1 and I don't recall having to configure the storage limit there but Composer 1 has a lot of differences in how the environment is setup.
I have not been able to find docs on how to increase this limit in Composer 2.
Things I will try next:
- try asking for more storage using pod resource requests
- see is there a way to configure the limits on the cluster outside of composer
I have not been able to find docs on how to change the 10GB limit besides this doc which shows how to change the storage for a worker but doesn't mention the 10GB limit.
Is there a standard way to increase the worker limit above 10GB?
发布评论
评论(1)
这是一个 。您可以参考此 Composer 2 有关作曲家2的详细信息 作曲家工人
旨在用于启动和/或投票,以实现在其他地方发射的工作状态。 这并不意味着用于本地处理或进行刮擦计算。
如果您打算有一个刮擦空间来处理文件或进行本地处理,则可以启动其他kubernetes pods来进行此操作,然后使用
kubernetespodoperator
,或者您也可以尝试gkepodoperator
由于kubernetespoderator
对您不起作用。This is a limitation as Composer 2 uses GKE Autopilot. You may refer to this Composer 2 for details of Composer 2.
Composer workers are intended to be used for launching and/or polling for the status of work launched elsewhere. It is not meant to be used for local processing or for scratch computation.
If you intend to have a scratch space to work on files or do local processing, you may launch other Kubernetes pods to do so and then use
KubernetesPodOperator
or you may also tryGKEPodOperator
since theKubernetesPodOperator
didn't work for you.