147186c7b4
If using rabbitmq as rpc backend, oslo.messaging generates large amount of redundant timeout debug logs (several logs per second on multiple openstack services, such as nova, heat, cinder), in format of 'Timed out waiting for RPC response: Timeout while waiting on RPC response - topic: "<unknown>", RPC method: "<unknown>" info: "<unknown>'. It's because each socket timeout exception is raised to multiple levels of error recovery callback functions then logged repeatedly. However, the accompanying value of socket.timeout exception is currently always “timed out”. Besides, oslo.messaging has implemented retry mechanism to recover socket timeout failure. Therefore, IMO those logs should be suppressed, even if at debug level, to save disk space and make debugging more convenient. Change-Id: Iafc360f8d18871cff93e7fd721d793ecdef5f4a1 Closes-Bug: #1714558
Team and repository tags
Oslo Messaging Library
The Oslo messaging API supports RPC and notifications over a number of different messaging transports.
- License: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/oslo.messaging/latest/
- Source: https://git.openstack.org/cgit/openstack/oslo.messaging
- Bugs: https://bugs.launchpad.net/oslo.messaging