RPC call monitor is started too early
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo.messaging |
New
|
Undecided
|
Arnaud Morin | ||
Bug Description
[NOTE] I'll try to provide more context to this bug soon
In AMQP driver, a call monitor timer is started when a client wait data from a server.
This monitor timer is currently started as soon as the message is sent (aka when we start waiting for a response).
As a side effect, if a client is expecting to wait for a response more than this monitor timeout, it may fail earlier than expected.
E.G. in nova code:
def check_can_
...
cctxt = client.
Client is expecting to wait until CONF.long_
So monitor timeout will wait 60s to receive the first response from this call. If the call is not receiving any response within that time, it will fail.
| Changed in oslo.messaging: | |
| assignee: | nobody → Arnaud Morin (arnaud-morin) |
| description: | updated |