yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

As it stands, if a client issuing an RPC call() sends a message to the
rabbitmq server, then the rabbitmq server does a failover the client
will wait for the full RPC timeout period (60 seconds) even though new
rabbitmq server has come up long before then and some connections have
been reestablished.

The RPC core should notice that the server has gone away and should
notify any entities waiting for an RPC call() response so that they can
error out early rather than waiting for the full RPC timeout period.

This was detected on Havana, but it seems to apply to all other versions
as well.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: oslo

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1368917

Title:
  rpc core should abort a call() early if the connection is terminated
  before the timeout period expires

Status in OpenStack Compute (Nova):
  New

Bug description:
  As it stands, if a client issuing an RPC call() sends a message to the
  rabbitmq server, then the rabbitmq server does a failover the client
  will wait for the full RPC timeout period (60 seconds) even though new
  rabbitmq server has come up long before then and some connections have
  been reestablished.

  The RPC core should notice that the server has gone away and should
  notify any entities waiting for an RPC call() response so that they
  can error out early rather than waiting for the full RPC timeout
  period.

  This was detected on Havana, but it seems to apply to all other
  versions as well.

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