Comment 4 for bug 2045058

The plan is:

- engage the call_monitor_timeout option without touching rpc client backoff mechanism. (In this way, the backoff will serve as a failsafe option when timeout misbehaves for some reason.)
- monitor behavior of the automatic timeout mechanism over several cycles.
- eventually, consider removal of the backoff mechanism from neutron-lib.

Nova enabled the active heartbeating for rpc calls when rpc timeout is bumped from the default 60 seconds. This seems a historical decision, to quote, to "keep the failure timing characteristics that our code likely expects (from history)". I will check with Dan Smith who wrote this (and the patch that integrates the mechanism in nova from ~2018) to see if there is a good reason to follow this example, or we can proactively enable it for all calls. For now, I plan to apply it unconditionally, unless there is a good scaling or stability related reason not to.