I spent some time trying to reproduce this. I don’t believe the problem is still occurring.
Here’s what I did:
I used devstack to set up an environment on an ubuntu image.
I edited /etc/apache2/sites-available/keystone.conf and changed processes=5 to processes=1 for both virtualhosts (to reduce the number of processes I needed to watch)
and restarted the apache service.
Use ps aux | grep keystone and noted the PIDs for processes named
(wsgi:keystone-pu -k start
and
(wsgi:keystone-ad -k start
after my keystone.conf http config edit there is only one each of these processes.
I opened two windows and monitored each process with a loop like:
while true; do lsof -p <processid> | wc -l; sleep 2; done
Then I opened Horizon. I launched 10 instances, terminated them and launched 10 again. The output from my loops did not change at all during this time.
I spent some time trying to reproduce this. I don’t believe the problem is still occurring.
Here’s what I did:
I used devstack to set up an environment on an ubuntu image. sites-available /keystone. conf and changed processes=5 to processes=1 for both virtualhosts (to reduce the number of processes I needed to watch)
I edited /etc/apache2/
and restarted the apache service.
Use ps aux | grep keystone and noted the PIDs for processes named
(wsgi:keystone-pu -k start
and
(wsgi:keystone-ad -k start
after my keystone.conf http config edit there is only one each of these processes.
I opened two windows and monitored each process with a loop like:
while true; do lsof -p <processid> | wc -l; sleep 2; done
Then I opened Horizon. I launched 10 instances, terminated them and launched 10 again. The output from my loops did not change at all during this time.