ICP 2.1 Beta 2不能足够快地创建Cloudant DB

Question

从安装说明运行以下命令时

sudo docker run --net=host -t -e LICENSE=accept -v $(pwd):/installer/cluster \
            ibmcom/icp-inception:2.1.0-beta-2-ee install

创建Cloudant DB的任务超时：

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，所以我认为它仍然在安装。如何增加重试次数？

Answer 1

运行命令

docker info | grep -i cgroup

你应该看看

Cgroup Driver: systemd

...so通过增加线来匹配ICP中的内容。

kubelet_extra_args: ["--cgroup-driver=systemd"]

致ICP's config.yaml

Answer 2

这通常意味着cloudant需要很长时间才能准备就绪，到那时，重试次数已经达到20次。卸载icp2.1 beta2并安装它通常可以通过这个问题。在国际比较方案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是否已被清除。

Answer 3

在某些情况下，我们发现基于Cloudant的ICP数据存储的大小需要一段时间才能下载。你考虑过要把图像放到你的主机上吗？

docker pull ibmcom/icp-datastore:{version}

您需要在每个master上(但不是在工作节点上)这样做。