@shinrich noticed default value of 10s for proxy.config.http.down_server.abort_threshold might be a little low. Example, If an HTTPS API call takes longer to return a response than 10s, the server is marked down.
Specifically, how does this setting interact with no_activity timeouts like proxy.config.http.transaction_no_activity_timeout_out ? We were having origin connections erroneously marked dead until we set proxy.config.http.down_server.abort_threshold to exceed proxy.config.http.transaction_no_activity_timeout_out - effectively turning the setting off. This made me wonder if this setting is useful at all.
Even after this change, very occasionally ran into conflict with proxy.config.net.default_inactivity_timeout = 300 as well.
@shinrich noticed default value of 10s for proxy.config.http.down_server.abort_threshold might be a little low. Example, If an HTTPS API call takes longer to return a response than 10s, the server is marked down.
Specifically, how does this setting interact with no_activity timeouts like proxy.config.http.transaction_no_activity_timeout_out ? We were having origin connections erroneously marked dead until we set proxy.config.http.down_server.abort_threshold to exceed proxy.config.http.transaction_no_activity_timeout_out - effectively turning the setting off. This made me wonder if this setting is useful at all.
Even after this change, very occasionally ran into conflict with proxy.config.net.default_inactivity_timeout = 300 as well.