Ask Your Question

What are typical numbers of nova-api processes on a controller?

asked 2015-04-29 06:52:58 -0500

SeanM gravatar image

updated 2015-04-29 09:40:14 -0500

We are looking at the behaviour of our system. We have noticed some unexpected behaviour in RabbitMQ and this is causing us to look at nova-api.

In our system, we see that we have 73 nova-api processes, one parent and 72 child processes and we believe that this has been slowly but steadily increasing over the space of a couple of months. If we stop the service and restart it, we get the same number of processes.

Surprisingly, osapi_compute_workers in nova.conf is 24 - we would have expected that this meant that the number of nova-api processes would peak at around this value.

So, my questions are:

  • is 73 nova-api processes common/typical (yes, a bit of a 'how long is a piece of strong', I know)
  • should the osapi_compute_workers parameter control the number of nova-api processes

We are running Icehouse installed with Mirantis Fuel 5.1.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-04-30 02:52:05 -0500

Ranjit gravatar image

updated 2015-04-30 02:54:56 -0500

Actually there are three types of API's exposed by nova-api. ec2, osapi_compute, metadata and enabing and disabling is controlled by enabled_apis in nova.conf.

enabled_apis = ec2, osapi_compute, metadata

No of workers for each type of API can be set by below settings in nova.conf

osapi_compute_workers = None

metadata_workers = None

ec2_workers = None

By default , for all type of API, no of workers = number of CPUs.

So for example if you have 24 CPU's then by default total no of processes = 73 = 24*3(1 for each type of API )+ PARENT
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-04-29 06:52:58 -0500

Seen: 1,937 times

Last updated: Apr 30 '15