kubernetes - 动物园管理员 : Hostname resolution fails

标签 kubernetes openshift apache-zookeeper kube-dns

我在 OpenShift/Kubernetes 环境中运行 Zookeeper。我已将 zookeeper 设置为 StatefulSet为了可靠地持久化配置数据。

我在我的 zoo.cfg 中配置了三台服务器按主机名,但在启动时,主机名解析失败。我验证了主机名确实可以在集群中使用 nslookup 解析。

动物园.cfg:

clientPort=2181
dataDir=/var/lib/zookeeper/data
dataLogDir=/var/lib/zookeeper/log
tickTime=2000
initLimit=10
syncLimit=2000
maxClientCnxns=60
minSessionTimeout= 4000
maxSessionTimeout= 40000
autopurge.snapRetainCount=3
autopurge.purgeInteval=0
server.1=zookeeper-0.zookeeper-headless:2888:3888
server.2=zookeeper-1.zookeeper-headless:2888:3888
server.3=zookeeper-2.zookeeper-headless:2888:3888

我的 OpenShift/Kubernetes 配置的相关部分:
  # StatefulSet
  - apiVersion: apps/v1beta1
    kind: StatefulSet
    metadata:
      labels:
        app: zookeeper
      name: zookeeper
    spec:
      serviceName: zookeeper-headless
      replicas: 3
      template:
        metadata:
          labels:
            app: zookeeper
        spec:
          containers:
            - image: 172.30.158.156:5000/os-cloud-platform/zookeeper:latest
              name: zookeeper
              ports:
                - containerPort: 2181
                  protocol: TCP
                  name: client
                - containerPort: 2888
                  protocol: TCP
                  name: server
                - containerPort: 3888
                  protocol: TCP
                  name: leader-election
          dnsPolicy: ClusterFirst
          schedulerName: default-scheduler

  # Service
  - apiVersion: v1
    kind: Service
    metadata:
      labels:
        app: zookeeper
      name: zookeeper
    spec:
      ports:
        - name: client
          port: 2181
          protocol: TCP
          targetPort: 2181
      selector:
        app: zookeeper
      sessionAffinity: None
      type: ClusterIP

  - apiVersion: v1
    kind: Service
    metadata:
      name: zookeeper-headless
      labels:
        app: zookeeper
    spec:
      ports:
        - port: 2888
          name: server
        - port: 3888
          name: leader-election
      clusterIP: None
      selector:
        app: zookeeper

OpenShift 日志显示 UnknownHostException s,虽然:
2017-10-06 10:59:18,289 [myid:] - WARN  [main:QuorumPeer$QuorumServer@155] - Failed to resolve address: zookeeper-2.zookeeper-headless
java.net.UnknownHostException: zookeeper-2.zookeeper-headless: No address associated with hostname
    at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
    at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
    at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
    at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
    at java.net.InetAddress.getAllByName(InetAddress.java:1192)
    at java.net.InetAddress.getAllByName(InetAddress.java:1126)
    at java.net.InetAddress.getByName(InetAddress.java:1076)
    at org.apache.zookeeper.server.quorum.QuorumPeer$QuorumServer.recreateSocketAddresses(QuorumPeer.java:148)
    at org.apache.zookeeper.server.quorum.QuorumPeer$QuorumServer.<init>(QuorumPeer.java:133)
    at org.apache.zookeeper.server.quorum.QuorumPeerConfig.parseProperties(QuorumPeerConfig.java:228)
    at org.apache.zookeeper.server.quorum.QuorumPeerConfig.parse(QuorumPeerConfig.java:140)
    at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:101)
at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
...

可能是什么原因?我验证了主机名(例如 zookeeper-2.zookeeper-headless )可通过 nslookup 从其他 pod 获得.

最佳答案

我为这个问题找到了一个可行的解决方案。 ZooKeeper 在启动时读取 ensemble 中的服务器列表,并查找它的“自己的”条目。然后它使用此条目来确定要监听的端口和接口(interface)。

server.1=zookeeper-0.zookeeper-headless:2888:3888
server.2=zookeeper-1.zookeeper-headless:2888:3888
server.3=zookeeper-2.zookeeper-headless:2888:3888

由于提供的主机名将在这台机器上解析为 127.0.0.1,ZooKeeper 将监听本地环回接口(interface),因此不接受来自其他 ZooKeeper 服务器的连接。
server.1=0.0.0.0:2888:3888
server.2=zookeeper-1.zookeeper-headless:2888:3888
server.3=zookeeper-2.zookeeper-headless:2888:3888

为了使集群中的事情自动化,我编写了一个 bash 脚本,它将在容器启动时替换一个“自己的”条目。

编辑:如评论中所问,这是我的 ENTRYPOINT负责放置 myid 文件并为每个 zoo.cfg 设置适当主机名的脚本:
#!/bin/bash
# This script extracts the number out of the pod's hostname and sets it as zookeepers id.

# Exact paths may vary according to your setup
MYID_FILE="/var/lib/zookeeper/data/myid"
ZOOCFG_FILE="/conf/zoo.cfg"

# Create myid-file
# Extract only numbers from hostname
id=$(hostname | tr -d -c 0-9)
echo $id > "${MYID_FILE}"

# change own hostname to 0.0.0.0
# otherwise, the own hostname will resolve to 127.0.0.1
# https://stackoverflow.com/a/40750900/5764665
fullHostname="$(hostname).zookeeper-headless"
sed -i -e "s/${fullHostname}/0.0.0.0/g" "${ZOOCFG_FILE}"

echo "Executing $@"
exec "$@"

关于kubernetes - 动物园管理员 : Hostname resolution fails,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/46605686/

相关文章:

kubernetes - 如何判断现有集群的类型是地区性集群还是区域性集群?

kubernetes - 将动态配置的 PV 重新附加到 PVC

kubernetes - 在 M1 Mac 上本地运行 Kubernetes

ruby-on-rails - mongoid yaml 结合主机的环境变量

docker - 在没有Zookeeper的情况下在Docker Swarm(1.12)上启动Solr云

apache-kafka - -bash : bin/kafka-topics. sh: 没有通过 ambari 安装这样的文件或目录

solr - Leader 选举 SolrCloud + Zookeeper

kubernetes - 标识未处于就绪状态的Pod

java - OpenShift:无法在 Wildfly 上部署二进制应用程序

java - Spring boot 1.5.2 未部署在 Openshift Tomcat 7(JBoss EWS 2.0) 中