yahoo-eng-team team mailing list archive

[nicky <1805769@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There is only rpc_response_time option in neutron.conf and the maximum
waiting time is just rpc_response_time * 10 which is neither efficient
nor flexible. 600 seconds are way too long under the majority of
circumstances and it is binded with default rpc_response_time which is
60 seconds, making it impossible to be adjusted to accustom every
condition.

** Affects: neutron
     Importance: Undecided
     Assignee: nicky (ss104301)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => nicky (ss104301)

** Changed in: neutron
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1805769

Title:
  maximum RPC response timeout is not reasonable

Status in neutron:
  In Progress

Bug description:
  There is only rpc_response_time option in neutron.conf and the maximum
  waiting time is just rpc_response_time * 10 which is neither efficient
  nor flexible. 600 seconds are way too long under the majority of
  circumstances and it is binded with default rpc_response_time which is
  60 seconds, making it impossible to be adjusted to accustom every
  condition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1805769/+subscriptions