networking-powervm

Better default value for heal and optimize loop

Bug #1571648 reported by Sridhar Venkat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-powervm
Fix Released
Undecided
Sridhar Venkat

Bug Description

Currently heal and optimize loop interval is set to 300 seconds (5 minutes). Due to this, it has been observed that CPU utilization is very high. This is due to frequent port updates. During every loop, port is updated to DOWN and made UP.

This work will increase this interval to 1800 seconds (30 minutes).

Sridhar Venkat (svenkat)
Changed in networking-powervm:
assignee: nobody → Sridhar Venkat (svenkat)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-powervm (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-powervm (master)

Reviewed: https://review.openstack.org/307168
Committed: https://git.openstack.org/cgit/openstack/networking-powervm/commit/?id=0c6d097db41103ad29b9333d5981dbb15a68756b
Submitter: Jenkins
Branch: master

commit 0c6d097db41103ad29b9333d5981dbb15a68756b
Author: Sridhar Venkat <email address hidden>
Date: Mon Apr 18 09:08:01 2016 -0400

    Better default value for heal and optimize loop

    Currently heal and optimize loop interval is set to 300 seconds
    Due to this, it has been observed that CPU utilization is very
    high. This is due to frequent port updates. During every loop,
    port is updated to DOWN and made UP.

    This work will increase this interval to 1800 seconds (30 minutes).

    Change-Id: I3ed9abca5534228eb335ae21070cbf73b9f43aed
    Closes-Bug: #1571648

Changed in networking-powervm:
status: In Progress → Fix Released
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.