| Summary: | can't apply patch "Creates multiple worker processes for API server" | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | chen.li |
| Component: | openstack-neutron | Assignee: | Maru Newby <mnewby> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | yfried |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | chen.li, chrisw, lpeer, majopela, mnewby, yeylon, zhongyue.luo |
| Target Milestone: | z1 | Keywords: | ZStream |
| Target Release: | 4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-13 16:53:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
chen.li
2013-12-10 08:42:43 UTC
The Nova log is insufficient to diagnose this problem. Can you please respond with errors appearing in the Neutron log? If you are seeing db connection errors, as I suspect you might, you will want to check that the maximum number of mysql connections is not being exceeded. Each additional worker process will add to the number of active connections. In any case, I recommend you use a more conservative value for api_workers (e.g. 4). While using 1 or more workers increases REST scalability, rpc processing is still single-process while we work to ensure that concurrent processing of rpc is safe. This means that increasing the number of worker processes can result in a bottleneck in rpc processing depending on the deployment's workload. There is no error log in neutron. What I can only know is that I can apply the patch under a Ubuntu system, but not CentOS. I have test set api_workers=4 as well, the issue remains. We have a guess this might caused by python2.6, but only a guess currently. What problem are you trying to solve by applying the patch in question? It is only one of many being worked on upstream to try to improve Neutron reliability and it would be helpful to know why you believe it is necessary to apply this one in isolation. We're doing a test it will boot new instances in a high rate in our cloud. When the boot rate is high enough ,we found the main reason instances will boot failed is due to neutron connection time out. While, the reason neutron server can't be connected is because it is too busy,single thread can't finished all requests. So,we hope neutron-server can have multi-process,such as nova. This patch is part f havana stable u/s branch, we need to make sure we get that on our next rebase or manually backport it along with other patches as Maru mentioned in comment #4 The patch was merged u/s to stable havana branch - https://review.openstack.org/#/c/60082/ and is included in the first async release thanks to the rebase- Bug 1045419 - Rebase openstack-neutron to 2013.2.1 |