Bug 1099657
| Summary: | qpid should be set to auto delete the queues | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Mark Wagner <mwagner> | |
| Component: | openstack-neutron | Assignee: | Ihar Hrachyshka <ihrachys> | |
| Status: | CLOSED WONTFIX | QA Contact: | Ofer Blaut <oblaut> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.0 | CC: | chrisw, ihrachys, nyechiel, yeylon | |
| Target Milestone: | --- | 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: | ||||
| : | 1147154 (view as bug list) | Environment: | ||
| Last Closed: | 2015-04-26 11:11:34 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: | ||
| Embargoed: | ||||
| Bug Depends On: | 1147154 | |||
| Bug Blocks: | 1081488 | |||
|
Description
Mark Wagner
2014-05-20 20:49:22 UTC
Simple change, greatly improves performance, scalability and reliability of system under load As a workaround, we may set amqp_auto_delete = True in neutron-dist.conf until the fix is propagated to our RPC layer code. We do not depend on oslo.messaging team since we have a workaround that can be applied thru neutron-dist.conf I've talked to sileht@ from oslo.messaging cores, and he told me that forcing amqp_auto_delete like that will result in that being set for TopicConsumers too. That will mean that if consumer is dead for a short time, the queue will be dropped. This may result in notifications lost, and other nasty things. Quoting: [15:04] <sileht> ihrachyshka, I think you can loose notifications if nobody consume them, and imagines you restart a nova-compute just when the scheduler ask something to the compute, you will lost the calls, and the caller (scheduler will retry until the compute is back) instead of having the scheduler waiting and the nova-compute restarting where it was stopped [15:07] <sileht> ihrachyshka, on small deployement that doesn't consume notification, I think it's doable, but I big one you will create many unuseful message each time you restart something [15:08] <sileht> ihrachyshka, for the notification part the rabbit driver have a workaround, that the qpid don't have So we still need a solution for this from oslo.messaging team. :| Moving to A6 as per Livnat's request. The reasoning is that the bug is internal and is not something any known customer is waiting for. Waiting for oslo.messaging guys to handle the issue in oslo in upstream first. |