neutron

  1. Bug #1987377
  2. Comment #4

Comment 4 for bug 1987377

Revision history for this message
liujinxin (scilla) wrote :

I found that the memory growth may be related to the operation of the health probe.

Readiness: exec [python /tmp/health-probe.py --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/metadata_agent.ini]

Steps to Reproduce：

kubectl top pods -nopenstack neutron-metadata-agent-default-b97p5
NAME CPU(cores) MEMORY(bytes)
neutron-metadata-agent-default-b97p5 40m 301Mi

kubectl exec -it -nopenstack neutron-metadata-agent-default-b97p5 bash -c 'for ((i=0;i<5000;i++)) do python /tmp/health-probe.py --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/metadata_agent.ini; done'

1 hour later

kubectl top pods -nopenstack neutron-metadata-agent-default-b97p5
NAME CPU(cores) MEMORY(bytes)
neutron-metadata-agent-default-b97p5 37m 5808Mi