A few fixes in api_handler solved this issue
- not calling json.dumps on the returned dict
- force non parallel api execution, to avoid multiple concurrent allocations
- call gc.collect as part of get_topology
- api handler runs in different process
- using generators to avoid creation of large collections
- removing excessive debug logging
Reviewed: https:/ /review. openstack. org/566794 /git.openstack. org/cgit/ openstack/ vitrage/ commit/ ?id=d485c6157dd 38c316d6b46a73d c595b421dfc94b
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit d485c6157dd38c3 16d6b46a73dc595 b421dfc94b
Author: Idan Hefetz <email address hidden>
Date: Tue May 8 06:59:41 2018 +0000
handle severe memory problem with get_topology
A few fixes in api_handler solved this issue
- not calling json.dumps on the returned dict
- force non parallel api execution, to avoid multiple concurrent allocations
- call gc.collect as part of get_topology
- api handler runs in different process
- using generators to avoid creation of large collections
- removing excessive debug logging
Change-Id: Ied24d8c0b1d301 49e45d63e95cf1b 3b2afdf504f
Closes-Bug: #1769826