Add another maxretry handler which does not create additional exchanges#205
Add another maxretry handler which does not create additional exchanges#205nevesenin wants to merge 3 commits intojondot:masterfrom
Conversation
|
I bet to get this merged, it'll be helpful to convert from rspec back into minitest like. If you'd like some help with this, I could either pair with you on it or I might be able to take a look and try to convert it myself. If you're not merged in by then, I'll pull request to your branch. |
|
Hi, I don't have much experience with minitest. To be honest, I don't know what you mean. |
b457aab to
7e6d67b
Compare
| channel.reject(delivery_info.delivery_tag) | ||
| end | ||
|
|
||
| def error_payload(delivery_info, message_properties, payload, reason, num_attempts) |
There was a problem hiding this comment.
@nevesenin
Could you explain why we need to change original payload?
There was a problem hiding this comment.
To add debug information in case of an error.
|
Cool, how does this differ in terms of the existing max retry exchange? thanks looks interesting! |
|
After some experimenting a couple of pointers for other people that want to try: when making a worker you must add the following arguments: class Worker
from_queue :foo, handler: Sneakers::Handlers::RoutingMaxretry,
arguments: {
'x-dead-letter-exchange' => "exchange",
'x-dead-letter-routing-key' => "queue.foo.retry"
}
# ...
endNotice that its Next, wildcard route matching is quite dangerous. I had a general routing key from my
|
|
I am working on using this, but when an error goes to the error queue bunny errors and gives me a |
|
It was something with how |
No description provided.