安装gcePersistentDisk kubernetes卷非常慢 [英] Mounting a gcePersistentDisk kubernetes volume is very slow

问题描述

我开始一个kubernetes复制控制器。当此复制控制器中单个pod中的相应容器具有 gcePersistentDisk 指定时，pod将开始非常慢。 5分钟后，荚仍然在待处理状态。

kubectl get po 会告诉我：

  NAME READY STATUS RESTARTS AGE 
 app-1-a4ni7 0 / 1等待0 5m 
  

没有 gcePersistentDisk pod是最多30秒内运行

（我使用的是10 GB Google云端存储磁盘，我知道这些磁盘具有较低容量的降低性能，但我不知道这是什么问题。）

这可能是什么原因？

解决方案

我们已经看到了GCE PD附加电话需要10分钟以上才能完成，所以这或多或少是预期的。例如，请参阅 https://github.com/kubernetes/kubernetes/issues/15382#issuecomment-153268655，其中PD测试在GCE PD附加/分离呼叫完成之前超时。我们正在与GCE团队合作，提高性能并减少延迟。

如果该端口从未脱离挂起状态，那么您可能会遇到一个错误。在这种情况下，请抓住您的kubelet日志，并在 https://github.com/kubernetes/kubernetes/ 上打开问题。 p>

I start a kubernetes replication controller. When the corresponding container in the single pod in this replication controller has a gcePersistentDisk specified the pods will start very slow. After 5 minutes the pod is still in the Pending state.

kubectl get po will tell me:

NAME          READY     STATUS    RESTARTS   AGE
app-1-a4ni7   0/1       Pending   0          5m

Without the gcePersistentDisk the pod is Running in max 30 seconds.

(I am using a 10 GB Google Cloud Storage disk and I know that these disks have lower performance for lower capacities, but I am not sure this is the issue.)

What could be the cause of this?

解决方案

We've seen the GCE PD attach calls take upwards of 10 minutes to complete, so this is more or less expected. For example see https://github.com/kubernetes/kubernetes/issues/15382#issuecomment-153268655, where PD tests were timing out before GCE PD attach/detach calls could complete. We're working with the GCE team to improve performance and reduce latency.

If the pod never gets out of pending state, then you might've hit a bug. In that case, grab your kubelet log and open an issue at https://github.com/kubernetes/kubernetes/

这篇关于安装gcePersistentDisk kubernetes卷非常慢的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！