ICP 2.1 Beta 2无法足够快地创建Cloudant DB

时间:2017-10-04 22:08:16

标签: ibm-cloud-private

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

3 个答案:

答案 0 :(得分:1)

运行命令

docker info | grep -i cgroup

你应该看到

Cgroup Driver: systemd

...通过添加行

在ICP中匹配

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

到ICP的config.yaml

答案 1 :(得分:0)

这通常意味着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 被清理干净了。

答案 2 :(得分:0)

在某些情况下,我们发现ICP数据存储区的大小(基于Cloudant)需要一段时间才能下载。您是否考虑过将图像预先拉到主机上?

docker pull ibmcom/icp-datastore:{version}

您需要在每个master(但不在工作节点上)执行此操作。