charts of hive, docker 2.3.2-postgresql-metastore maybe have some problem

[LY1806620741]

hive charts always can't pass livenessProbe check. I try to use version 0.1.5 and 0.1.4.

hive-server error info is:

Readiness probe failed: Get "http://172.17.0.9:10002/": dial tcp 172.17.0.9:10002: connect: connection refused

[cgiraldo]

Which version are you trying?

Please try version 0.1.5

helm install my-hive gradiant/hive --version 0.1.5

There is a bug in prior versions detected in issue #34.

[LY1806620741]

At first. I use 0.1.5. And found this error. then I try 0.1.4, problem has not improved.

my env:

helm

[vagrant@control-plane test]$ helm version
version.BuildInfo{Version:"v3.4.1", GitCommit:"c4e74854886b2efe3321e185578e6db9be0a6e29", GitTreeState:"clean", GoVersion:"go1.14.11"}
[vagrant@control-plane test]$ helm list
NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION
hive    default         1               2020-11-30 10:06:12.130733853 +0000 UTC deployed        hive-0.1.5      2.3.6

minikube

[vagrant@control-plane test]$ minikube version
minikube version: v1.15.0

kubectl

[vagrant@control-plane test]$ kubectl get pods
NAME                                READY   STATUS    RESTARTS   AGE
hive-hdfs-datanode-0                1/1     Running   1          2m47s
hive-hdfs-datanode-1                1/1     Running   0          2m1s
hive-hdfs-datanode-2                1/1     Running   0          101s
hive-hdfs-httpfs-59bc69476b-sp2zh   1/1     Running   0          2m47s
hive-hdfs-namenode-0                2/2     Running   1          2m47s
hive-metastore-0                    1/1     Running   0          2m47s
hive-postgresql-0                   1/1     Running   0          2m47s
hive-server-0                       0/1     Running   2          2m47s




[vagrant@control-plane test]$ kubectl describe pods hive-server-0
Name:         hive-server-0
Namespace:    default
Priority:     0
Node:         minikube/192.168.49.2
Start Time:   Mon, 30 Nov 2020 10:06:12 +0000
Labels:       app.kubernetes.io/component=server
              app.kubernetes.io/instance=hive
              app.kubernetes.io/name=hive
              controller-revision-hash=hive-server-6c687fdbf
              statefulset.kubernetes.io/pod-name=hive-server-0
Annotations:  <none>
Status:       Running
IP:           172.17.0.8
IPs:
  IP:           172.17.0.8
Controlled By:  StatefulSet/hive-server
Containers:
  server:
    Container ID:  docker://8cb8aec27458aaf9796498e30b6d043043e8a67b66ad9e9a52a46a6799969ada
    Image:         gradiant/hive:2.3.2-postgresql-metastore
    Image ID:      docker-pullable://gradiant/hive@sha256:aae4f8a21f8b9f7cfbe5898a8c072c82eb6976026106b41ecf347b9b30cf1157
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      /opt/hive/conf/startup.sh
    State:          Running
      Started:      Mon, 30 Nov 2020 10:09:33 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Mon, 30 Nov 2020 10:08:23 +0000
      Finished:     Mon, 30 Nov 2020 10:09:32 +0000
    Ready:          False
    Restart Count:  3
    Liveness:       http-get http://:10002/ delay=10s timeout=2s period=10s #success=1 #failure=3
    Readiness:      http-get http://:10002/ delay=5s timeout=2s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /opt/hadoop/etc/hadoop from hadoop-config (rw)
      /opt/hive/conf from hive-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-x9c2k (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  hadoop-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      hive-hdfs-hadoop
    Optional:  false
  hive-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      hive
    Optional:  false
  default-token-x9c2k:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-x9c2k
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  3m54s                  default-scheduler  Successfully assigned default/hive-server-0 to minikube
  Normal   Pulled     2m50s (x2 over 3m53s)  kubelet            Container image "gradiant/hive:2.3.2-postgresql-metastore" already present on machine
  Normal   Created    2m50s (x2 over 3m53s)  kubelet            Created container server
  Normal   Started    2m50s (x2 over 3m53s)  kubelet            Started container server
  Warning  Unhealthy  2m20s (x6 over 3m40s)  kubelet            Liveness probe failed: Get "http://172.17.0.8:10002/": dial tcp 172.17.0.8:10002: connect: connection refused
  Normal   Killing    2m20s (x2 over 3m20s)  kubelet            Container server failed liveness probe, will be restarted
  Warning  Unhealthy  2m3s (x11 over 3m43s)  kubelet            Readiness probe failed: Get "http://172.17.0.8:10002/": dial tcp 172.17.0.8:10002: connect: connection refused

[cgiraldo]

You should use version 0.1.5.

It can take more than 3 minutes to be up and running in a healthy state.

If not, try to edit hive-server liveness and readiness probes and set longer initialDelaySeconds and/or timeoutSeconds.

kubectl edit statefulsets.apps hive-server

[LY1806620741]

Exactly, my minikube default config memory=2200mb cpus=2. The low conditions resulted in an extension of the start-up time then hive-server Cycle reboot .

When I remove liveness and readiness probes, It work.