gate-tempest-dsvm-largeops sometimes fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Won't Fix
|
Low
|
Li Ma |
Bug Description
Before oslo.messaging 1.5 the rpc.call timeout (by default the rpc_response_
for example we see two rpc.call that timeout in:
http://
I have tracked the msg id 42ed8c906547434
the rpc.call is done here:
2015-01-27 14:55:41.816 6907 DEBUG oslo_messaging.
Exactly, one minute later we receive the timeout for this both message:
2015-01-27 14:56:41.823 6907 TRACE nova.compute.
If we check a bit later (3 seconds), oslo.messaging received the response a bit too late:
2015-01-27 14:56:44.744 6907 INFO oslo_messaging.
2015-01-27 14:56:44.744 6907 INFO oslo_messaging.
Perhaps we need to increase the rpc_timeout_
We can note that we between 320 and 640 rpc.call that run concurrently in this jobs, that represent many greenthread to schedule.
Cheers,
Changed in oslo.messaging: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in oslo.messaging: | |
assignee: | nobody → Li Ma (nick-ma-z) |
Changed in oslo.messaging: | |
importance: | High → Low |
status: | In Progress → Triaged |
Seems I also have the same problem.
http:// logs.openstack. org/22/ 145722/ 3/check/ gate-tempest- dsvm-largeops- src-oslo. messaging/ 633f627/ logs/screen- n-cpu-1. txt.gz? level=ERROR