tacker

vim monitor mistral action is taking too much in output debuging

Bug #1702575 reported by yong sheng gong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Critical
yong sheng gong
tacker pike-3 "p3"

Bug Description

the mistral executor is taking too much CPU to output ping command

yong sheng gong (gongysh)
Changed in tacker:
milestone: none → pike-3
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.openstack.org/480757

Changed in tacker:
assignee: nobody → yong sheng gong (gongysh)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/480757
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=e197a7d3cdcc006816c94ed3ad5199d54360c39e
Submitter: Jenkins
Branch: master

commit e197a7d3cdcc006816c94ed3ad5199d54360c39e
Author: yong sheng gong <gong.yongsheng@99cloud.net>
Date: Thu Jul 6 05:42:55 2017 +0800

    disable log output when needed.

    vim ping action is in a tight loop, too disable log
    is a must to avoid CPU and IO comsumption.

    Change-Id: Ie5974541f03b41db04b47700bfafed7c023862f3
    Closes-bug: #1702575

Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 0.8.0

This issue was fixed in the openstack/tacker 0.8.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.