RPC publisher shouldn't block if transport layer is down
Bug #1189488 reported by
Julien Danjou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Medium
|
Mehdi Abaakouk |
Bug Description
The current RPC publisher might block any program trying to publisher to an AMQP server if it fails to publisher.
It should handle its inability to publish with either dropping the counter or storing in a local queue until it's possible to publish.
Changed in ceilometer: | |
importance: | Undecided → Medium |
status: | New → Triaged |
summary: |
- RPC publisher shouldn't block if transport layer id own + RPC publisher shouldn't block if transport layer is down |
Changed in ceilometer: | |
assignee: | nobody → Mehdi Abaakouk (sileht) |
Changed in ceilometer: | |
status: | Triaged → In Progress |
Changed in ceilometer: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/35604 github. com/openstack/ ceilometer/ commit/ 3f044dd1ace2da3 dba65fdb9017b87 8ce902a554
Committed: http://
Submitter: Jenkins
Branch: master
commit 3f044dd1ace2da3 dba65fdb9017b87 8ce902a554
Author: Mehdi Abaakouk <email address hidden>
Date: Thu Jul 4 09:30:43 2013 +0200
publisher.rpc: queing policies
This change allow to configure the behavior of rpc publisher
when rabbitmq is down.
3 policies are available:
raise a exception if rabbit_max_retries > 0
- default: wait until it comes back if rabbit_max_retries <= 0
- drop: don't publish the samples
- queue: create a local queue of 'max_queue_length' samples
Configuration of the policy is done via the publisher url policy= queue&max_ queue_length= 100
example: rpc://?
Change-Id: I41c9be9e1c760d b1155711325434a 1877e6dd7b2
Fixes: bug#1192918 bug#1189488