Heavily loaded nova-compute instances don't sent reports frequently enough
Bug #1045152 reported by
Tiantian Gao
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Tiantian Gao | ||
Essex |
Fix Released
|
Undecided
|
Unassigned | ||
oslo-incubator |
Invalid
|
High
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We knows that nova-compute will do report_state to update the service information in DB, And the default report_interval is 5s.
When scheduler run a new instance, it will check the time that nova-compute updated. If the interval is longer than 60 seconds, Scheduler see the host is dead.
But when the host(nova-compute) running a lot of instances ( about 70+) . The report_interval sometimes can be greater then 2minutes. This will result in ERROR in scheduler.
I think report_state should be in a thread, rather than in a eventlet.spawn.
What about guys think?
Thanks
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → High |
summary: |
- The report_state interval is longger then 10s actually + Heavily loaded nova-compute instances don't sent reports frequently + enough |
Changed in nova: | |
assignee: | nobody → NetEase Cloud Team (netease-cloud) |
tags: | added: canonistack |
Changed in nova: | |
assignee: | NetEase Cloud Team (netease-cloud) → TianTian Gao (gtt116) |
status: | Triaged → In Progress |
description: | updated |
security vulnerability: | yes → no |
Changed in openstack-common: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: essex-backport |
Changed in nova: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-rc1 → 2012.2 |
affects: | openstack-common → oslo |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
information type: | Public → Public Security |
information type: | Public Security → Private Security |
information type: | Private Security → Public Security |
information type: | Public Security → Public |
Changed in oslo: | |
status: | Confirmed → Triaged |
tags: |
added: verification-done removed: verification-needed |
Changed in oslo: | |
status: | Triaged → Invalid |
To post a comment you must log in.
Also in periodic_tasks. available_ resource, could not response to AMQP request.
nova-compute is busy running update_