FLAGS.rpc_response_timeout default is too long

Bug #938287 reported by Anthony Young on 2012-02-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Anthony Young

Bug Description

At present, the default FLAGS.rpc_response_timeout=3600 - this is excessively long, and prevents timeout errors from hitting users. For example, if n-net hangs, and then you try to list floating ips, the call will not return for an hour. This makes it very hard to diagnose system configuration issues.

Thierry Carrez (ttx) on 2012-02-24
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Changed in nova:
assignee: nobody → Anthony Young (sleepsonthefloor)
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/4376
Committed: http://github.com/openstack/nova/commit/a0001c57e7b7555801577bb568b8cd630adb152d
Submitter: Jenkins
Branch: master

commit a0001c57e7b7555801577bb568b8cd630adb152d
Author: Anthony Young <email address hidden>
Date: Tue Feb 21 15:51:32 2012 -0800

    Shorten FLAGS.rpc_response_timeout

     * Fixes bug 938287
     * Bump timeout to 60 seconds

    Change-Id: I0f38fe0bdfc950386f1fce221069e395e7e81f2a

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers