hdfs

1.hdfs报大量gc超时

namenode日志出现大量GC超时相关错误,且30914端口未监听:

 GC pool 'ParNew' had collection(s): count=1 time=0ms GC pool 'ConcurrentMarkSweep' had collection(s): count=1 time=17577ms

解决办法:

修改namenode启动参数:-Xmx4G改成-Xmx8G,解决30914端口未监听的问题

2.hdfs-namenode启动报错zkfc与zookeeper断开连接

hdfs报错图片

该问题可能与dns解析有关系 ,可尝试重启各个服务器对应的localnodedns ,然后删除zookeeper中与hdfs相关的znode,最后重启hdfs就可以了

重启nodelocaldns

kubectl -n kube-system  rollout restart ds nodelocaldns && watch -n1 "kubectl -n kube-system get pod | grep nodelocal"

清理与hdfs相关的znode

kubectl -n component exec -it zookeeper-default-0 -- zkCli.sh delete /hadoop-ha/hdfs-k8s/ActiveStandbyElectorLock
kubectl -n component exec -it zookeeper-default-0 -- zkCli.sh delete /hadoop-ha/hdfs-k8s/ActiveBreadCrumb
kubectl -n component exec -it zookeeper-default-0 -- zkCli.sh delete /hadoop-ha/hdfs-k8s
kubectl -n component exec -it zookeeper-default-0 -- zkCli.sh delete /hadoop-ha

重启hdfs服务

kubectl delete -f /etc/kubernetes/components/hadoop/default/
kubectl apply -f /etc/kubernetes/components/hadoop/default/
posted @ 2022-10-31 01:06  打倒资本主义  阅读(73)  评论(0)    收藏  举报