Change report_interval from 4 to 30, agent_down_time from 9 to 75

Bug #1308336 reported by Openstack Gerrit
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Medium
Gauvain Pocentek

Bug Description

https://review.openstack.org/87240
commit 3569abac570f3176466b94b2c9ed9ff50d2f0b0d
Author: Assaf Muller <email address hidden>
Date: Sun Mar 16 13:01:18 2014 +0200

    Change report_interval from 4 to 30, agent_down_time from 9 to 75

    report_interval is how often an agent sends out a heartbeat to the
    service. The Neutron service responds to these 'report_state' RPC
    messages by updating the agent's heartbeat DB record.
    The last heartbeat is then compared to the configured
    agent_down_time to determine if the agent is up or down.
    The agent's status is used when scheduling networks on DHCP
    and L3 agents.

    In the spirit of sane defaults suited for production, these values
    should be bumped to reduce the load on the Neutron service
    dramatically, freeing up CPU time to perform intensive operations.

    DocImpact
    Closes-Bug: #1293083

    (cherry picked from commit e13d19cab384a9f5f8a00436ad39118f342af32c)
    Change-Id: I77bcf8f66f74ba55513c989caead1f96c92b9832
    Conflicts:
     neutron/agent/common/config.py

Tags: neutron
Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

This change is part of the current config reference.

Changed in openstack-manuals:
status: New → Fix Released
importance: Undecided → Medium
assignee: nobody → Gauvain Pocentek (gpocentek)
milestone: none → icehouse
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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