| 2014-09-15 16:43:04 |
Chris Friesen |
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. |
As it stands, if a client issuing an RPC call() sends a message to the rabbitmq server, then the rabbitmq server does a switchover/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.
On a controlled switchover especially 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. |
|
