在 Google Cloud Kubernetes 上运行 elasticsearch 以 CrashLoopBackOff 结束答案

【问题标题】：Running elasticsearch on Google Cloud Kubernetes ends in CrashLoopBackOff在 Google Cloud Kubernetes 上运行 elasticsearch 以 CrashLoopBackOff 结束
【发布时间】：2018-05-12 12:01:02
【问题描述】：

我尝试在谷歌云实例上运行elasticsearch6 容器。不幸的是，容器总是以 CrashLoopBackOff 结束。这就是我所做的：

安装 gcloud 和 kubectl

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
echo "deb http://packages.cloud.google.com/apt cloud-sdk-$(lsb_release -c -s) main" | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list
sudo apt-get update && sudo apt-get install google-cloud-sdk kubectl

配置 gcloud

gcloud init
gcloud config set compute/zone europe-west3-a  # For Frankfurt

创建 Kubernetes 集群

gcloud container clusters create elasticsearch-cluster --machine-type=f1-micro --num-nodes=3

激活吊舱

kubectl create -f pod.yml  

apiVersion: v1
kind: Pod
metadata:
  name: test-elasticsearch
  labels:
    name: test-elasticsearch
spec:
  containers:
    - image: launcher.gcr.io/google/elasticsearch6
      name: elasticsearch

在此之后我得到状态：

kubectl get pods
NAME                    READY     STATUS             RESTARTS   AGE
test-elasticsearch   0/1       CrashLoopBackOff   10         31m

kubectl logs test-elasticsearch 不显示任何输出。

这里是kubectl describe po test-elasticsearch 的输出，其中包含一些信息 XXX。

Name:         test-elasticsearch
Namespace:    default
Node:         gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv/XX.XXX.X.X
Start Time:   Sat, 12 May 2018 14:54:36 +0200
Labels:       name=test-elasticsearch
Annotations:  kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container elasticsearch
Status:       Running
IP:           XX.XX.X.X
Containers:
  elasticsearch:
    Container ID:   docker://bb9d093df792df072a762973066d504a4e7d73b0e87d0236a94c3e8b972d9c41
    Image:          launcher.gcr.io/google/elasticsearch6
    Image ID:       docker-pullable://launcher.gcr.io/google/elasticsearch6@sha256:1ddafd5293dbec8fb73eabffa29614916e4933bb057db50231084d89f4a0b3fa
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Sat, 12 May 2018 14:55:06 +0200
      Finished:     Sat, 12 May 2018 14:55:09 +0200
    Ready:          False
    Restart Count:  2
    Requests:
      cpu:        100m
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-XXXXX (ro)
Conditions:
  Type           Status
  Initialized    True 
  Ready          False 
  PodScheduled   True 
Volumes:
  default-token-XXXXX:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-XXXXX
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.alpha.kubernetes.io/notReady:NoExecute for 300s
                 node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                 Age                From                                                          Message
  ----     ------                 ----               ----                                                          -------
  Normal   Scheduled              51s                default-scheduler                                             Successfully assigned test-elasticsearch to gke-elasticsearch-cluste-def
  Normal   SuccessfulMountVolume  51s                kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  MountVolume.SetUp succeeded for volume "default-token-XXXXX"
  Normal   Pulling                22s (x3 over 49s)  kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  pulling image "launcher.gcr.io/google/elasticsearch6"
  Normal   Pulled                 22s (x3 over 49s)  kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  Successfully pulled image "launcher.gcr.io/google/elasticsearch6"
  Normal   Created                22s (x3 over 48s)  kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  Created container
  Normal   Started                21s (x3 over 48s)  kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  Started container
  Warning  BackOff                4s (x3 over 36s)   kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  Back-off restarting failed container
  Warning  FailedSync             4s (x3 over 36s)   kubelet, gke-elasticsearch-cluste-default-pool-XXXXXXXX-wtbv  Error syncing pod

【问题讨论】：

好的，首先，您不应该以这种方式手动创建 pod，而应始终在某种控制器（Deployment、ReplicationController、StatefulSet 等）上进行中继。话虽如此，尝试运行kubectl describe po test-elasticsearch 并发布输出
@whites11 在完成这项工作后，我很想获得一个好的文档链接，如何正确设置它！
看起来像是运行时错误，你确定 kubectl 日志什么都不返回吗？
不幸的是，没有输出。在我的本地 docker 上运行相同的容器可以工作:-( 嗯，也许它与弹性搜索文档中提到的 vm.max_map_count=262144 有关。但我不确定如何在 GKE 上设置它。
我看到退出状态是 137 这通常意味着内存不足。您的节点中有多少内存？

标签： elasticsearch kubernetes google-kubernetes-engine

【解决方案1】：

问题出在 f1-micro 实例上。它没有足够的内存来运行。只有在升级到 4GB 的实例后它才能工作。不幸的是，这对我来说太贵了，所以我不得不寻找其他东西。

【讨论】：