ICP 2.1 Beta 2 无法足够快地创建 Cloudant DB
ICP 2.1 Beta 2 can't create Cloudant DB fast enough
当 运行 来自 the installation instructions 的以下命令时:
sudo docker run --net=host -t -e LICENSE=accept -v $(pwd):/installer/cluster \
ibmcom/icp-inception:2.1.0-beta-2-ee install
创建 Cloudant 数据库的任务超时:
TASK [master : Ensuring that the Cloudant Database is ready] ***********************************************************************************************************************************************
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (20 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (19 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (18 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (17 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (16 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (15 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (14 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (13 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (12 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (11 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (10 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (9 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (8 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (7 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (6 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (5 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (4 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (3 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (2 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (1 retries left).
fatal: [10.20.30.29] => Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>
PLAY RECAP *************************************************************************************************************************************************************************************************
10.20.30.29 : ok=149 changed=57 unreachable=0 failed=1
容器仍在 /usr/bin/python /usr/bin/ansible-playbook -e @cluster/config.yaml playbook/site.yaml
中使用 CPU,所以我认为它仍在安装中。如何增加重试次数?
这通常意味着 cloudant db 准备时间太长,到那时,已达到 20 次重试限制。卸载 ICP 2.1 beta2 并安装它通常可以解决此问题。在 ICP 2.1 beta3 中,它会增加超时时间。
如果这不起作用,您可以检查以下内容:
docker exec -it <cloudant container> bash
现在在容器内,检查数据库状态:
cast cluster status -p $ADMIN_PASSWORD
也可以检查:
docker logs <long cloudant container name>
再次安装ICP beta2之前,检查是否
docker volume ls
已清理。
运行命令
docker info | grep -i cgroup
你应该会看到
Cgroup Driver: systemd
...通过添加
行与 ICP 中的匹配
kubelet_extra_args: ["--cgroup-driver=systemd"]
到ICPconfig.yaml
在某些情况下,我们发现基于 Cloudant 的 ICP 数据存储的大小需要一段时间才能下载。您是否考虑过将映像预拉到您的主机上?
docker pull ibmcom/icp-datastore:{version}
您需要在每个 master
上执行此操作(但不是在工作节点上)。
当 运行 来自 the installation instructions 的以下命令时:
sudo docker run --net=host -t -e LICENSE=accept -v $(pwd):/installer/cluster \
ibmcom/icp-inception:2.1.0-beta-2-ee install
创建 Cloudant 数据库的任务超时:
TASK [master : Ensuring that the Cloudant Database is ready] ***********************************************************************************************************************************************
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (20 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (19 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (18 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (17 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (16 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (15 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (14 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (13 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (12 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (11 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (10 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (9 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (8 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (7 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (6 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (5 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (4 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (3 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (2 retries left).
FAILED - RETRYING: TASK: master : Ensuring that the Cloudant Database is ready (1 retries left).
fatal: [10.20.30.29] => Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>
PLAY RECAP *************************************************************************************************************************************************************************************************
10.20.30.29 : ok=149 changed=57 unreachable=0 failed=1
容器仍在 /usr/bin/python /usr/bin/ansible-playbook -e @cluster/config.yaml playbook/site.yaml
中使用 CPU,所以我认为它仍在安装中。如何增加重试次数?
这通常意味着 cloudant db 准备时间太长,到那时,已达到 20 次重试限制。卸载 ICP 2.1 beta2 并安装它通常可以解决此问题。在 ICP 2.1 beta3 中,它会增加超时时间。
如果这不起作用,您可以检查以下内容:
docker exec -it <cloudant container> bash
现在在容器内,检查数据库状态:
cast cluster status -p $ADMIN_PASSWORD
也可以检查:
docker logs <long cloudant container name>
再次安装ICP beta2之前,检查是否
docker volume ls
已清理。
运行命令
docker info | grep -i cgroup
你应该会看到
Cgroup Driver: systemd
...通过添加
行与 ICP 中的匹配kubelet_extra_args: ["--cgroup-driver=systemd"]
到ICPconfig.yaml
在某些情况下,我们发现基于 Cloudant 的 ICP 数据存储的大小需要一段时间才能下载。您是否考虑过将映像预拉到您的主机上?
docker pull ibmcom/icp-datastore:{version}
您需要在每个 master
上执行此操作(但不是在工作节点上)。