NAME READY STATUS RESTARTS AGE
hbase-fuse-8d7gk 0/1 ContainerCreating 0 4m29s
hbase-fuse-jvlmc 0/1 ContainerCreating 0 4m29s
hbase-master-0 2/2 Running 0 5m17s
hbase-worker-thhbb 1/2 CrashLoopBackOff 5 4m29s
hbase-worker-thz6s 1/2 CrashLoopBackOff 5 4m29s
How to reproduce it
Additional Information
describe the worker pod,
Normal Started 8m4s kubelet Started container alluxio-job-worker
Normal Pulled 6m25s (x5 over 8m4s) kubelet Container image "registry.cn-huhehaote.aliyuncs.com/alluxio/alluxio:2.3.0-SNAPSHOT-e0feba3" already present on machine
Normal Created 6m25s (x5 over 8m4s) kubelet Created container alluxio-worker
Normal Started 6m25s (x5 over 8m4s) kubelet Started container alluxio-worker
Warning BackOff 2m51s (x24 over 7m59s) kubelet Back-off restarting failed container
I think we need more information to learn what's wrong with your Fluid. Could you please provide logs about this problem? The diagnose.sh shell script mentioned in this userguide may do some help.
What is your environment(Kubernetes version, Fluid version, etc.) k8s v1.19.1,fluid 0.3 Describe the bug following the doc https://github.com/fluid-cloudnative/fluid/blob/master/docs/zh/samples/accelerate_data_accessing.md , What you expect to happen: got the result after apply runtime.yaml,
How to reproduce it
Additional Information describe the worker pod,