Connection pool is full when boot an instance
Bug #1497949 reported by
Lan Qi song
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-docker |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
When I tried to boot an instance on an host which already have lots of containers (> 500), and there are lots of following logs in nova-compute.log:
2015-09-15 04:05:03.681 8975 WARNING requests.
This is because currently each time we boot an instance and attach the interface , novadocker will inspect all the instance to match the correct container( By host name), that would take too much time and waste too much connection.
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/225623 /git.openstack. org/cgit/ stackforge/ nova-docker/ commit/ ?id=33643b24a10 90efb26d968e318 f3f7878a7e958a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 33643b24a1090ef b26d968e318f3f7 878a7e958a
Author: lqslan <lqslan.cn.ibm.com>
Date: Mon Sep 21 10:41:57 2015 +0000
Find container by uuid instead of by name
Currently, when boot a container, novadocker will create the container firstly,
then attach the interface, this step novadocker will loop to inspect all the
containers to find the right one. This takes too much time and docker connections.
This patch use find container by uuid instead of by name, this way would save much
time and connections.
Change-Id: I1cdf672e99b269 b1f7e18d1a73a65 57c7eb0540a
Closes-Bug: #1497949