yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <2045058@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently, neutron RPC clients will repeat calls, timeout, back off,
repeat again... this logic is implemented in neutron-lib RPCClient
itself. This is done to handle requests that take a very long time.

Instead of failing, then bumping timeout and hope that it's enough now
(and leave the server unaware), we could instead enable active
heartbeating with oslo.messaging call_monitor_timeout option.

See nova did this for their clients:
https://opendev.org/openstack/nova/commit/fe26a52024416ed2d37c2d5027da4b23231dc515

I believe this should replace backoff logic in neutron-lib.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

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

Title:
  [RFE] Use call_monitor_timeout of oslo.messaging RPCClient instead of
  custom backoff mechanism and hardcoded timeouts

Status in neutron:
  New

Bug description:
  Currently, neutron RPC clients will repeat calls, timeout, back off,
  repeat again... this logic is implemented in neutron-lib RPCClient
  itself. This is done to handle requests that take a very long time.

  Instead of failing, then bumping timeout and hope that it's enough now
  (and leave the server unaware), we could instead enable active
  heartbeating with oslo.messaging call_monitor_timeout option.

  See nova did this for their clients:
  https://opendev.org/openstack/nova/commit/fe26a52024416ed2d37c2d5027da4b23231dc515

  I believe this should replace backoff logic in neutron-lib.

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