contrail-logs command does not complete in time and process hogs memory.
If run in a scale setup and for a longer time period (i.e. 5-6h or more), contrail-logs would take a lot of memory and go to D state due to waiting
for IO. This fix divides the query in multiple queries of 10 min so that contrail-logs does not take a lot of memory and have a smaller amount of
data to write to the disk. Moreover, this fix would fetch the results for the next query while writing the results for the current query to the disk
in parallel because writing to the disk may take some time.
Reviewed: https:/ /review. opencontrail. org/30149 github. org/Juniper/ contrail- controller/ commit/ 9ec7e8d1d2f3414 9556b4bf8e87444 5aa2ebfd68
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 9ec7e8d1d2f3414 9556b4bf8e87444 5aa2ebfd68
Author: mkheni <email address hidden>
Date: Tue Apr 4 09:49:47 2017 -0700
contrail-logs command does not complete in time and process hogs memory.
If run in a scale setup and for a longer time period (i.e. 5-6h or more), contrail-logs would take a lot of memory and go to D state due to waiting
for IO. This fix divides the query in multiple queries of 10 min so that contrail-logs does not take a lot of memory and have a smaller amount of
data to write to the disk. Moreover, this fix would fetch the results for the next query while writing the results for the current query to the disk
in parallel because writing to the disk may take some time.
Change-Id: Ib68c7058e970e8 53288d8236ea423 9bdb471b313
Closes-bug: #1673865