[jira] Updated: (TS-153) "Dynamic" keep-alive timeouts

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-153:
-----------------------------

    Description: 
(This is from a Y! Bugzilla ticket 1821593, adding it here. . Originally posted by Leif Hedstrom on 2008-03-19):


Currently you have to set static keep-alive idle timeouts in TS, e.g.

   CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 8
   CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 30


even with epoll() in 1.17.x, this is difficult to configure, and put an appropriate timeout. The key here is that the
settings above need to assure that you stay below the max configured number of connections, e.g.:

    CONFIG proxy.config.net.connections_throttle INT 75000


I'm suggesting that we add one (or two) new configuration options, and appropriate YTS code support, to instead of
specifying timeouts, we specify connection limits for idle KA connections. For example:

    CONFIG proxy.config.http.keep_alive_max_idle_connections_in INT 50000
    CONFIG proxy.config.http_keep_alive_max_idle_connections_out INT 5000

(one still has to be careful to leave head-room for active connections here, in the example above, 20000 connections
could be active, which is a lot of traffic).

These would override the idle timeouts, so one could use the max_idle connections for incoming (client) connections,
and the idle timeouts for outgoing (origin) connections for instance.

The benefit here is that it makes configuration not only easier, but also a lot safer for many applications.

  was:
(This is from a Y! Bugzilla ticket 1821593, adding it here. . Originally posted by Leif Hedstrom on 2008-03-19:


Currently you have to set static keep-alive idle timeouts in YTS, e.g.

   CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 8
   CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 30


even with epoll() in 1.17.x, this is difficult to configure, and put an appropriate timeout. The key here is that the
settings above need to assure that you stay below the max configured number of connections, e.g.:

    CONFIG proxy.config.net.connections_throttle INT 75000


I'm suggesting that we add one (or two) new configuration options, and appropriate YTS code support, to instead of
specifying timeouts, we specify connection limits for idle KA connections. For example:

    CONFIG proxy.config.http.keep_alive_max_idle_connections_in INT 50000
    CONFIG proxy.config.http_keep_alive_max_idle_connections_out INT 5000

(one still has to be careful to leave head-room for active connections here, in the example above, 20000 connections
could be active, which is a lot of traffic).

These would override the idle timeouts, so one could use the max_idle connections for incoming (client) connections,
and the idle timeouts for outgoing (origin) connections for instance.

The benefit here is that it makes configuration not only easier, but also a lot safer for applications like YCPI. YCS
could also benefit from this, but probably to a lesser degree.



> "Dynamic" keep-alive timeouts
> -----------------------------
>
>                 Key: TS-153
>                 URL: https://issues.apache.org/jira/browse/TS-153
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Leif Hedstrom
>            Priority: Minor
>
> (This is from a Y! Bugzilla ticket 1821593, adding it here. . Originally posted by Leif Hedstrom on 2008-03-19):
> Currently you have to set static keep-alive idle timeouts in TS, e.g.
>    CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 8
>    CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 30
> even with epoll() in 1.17.x, this is difficult to configure, and put an appropriate timeout. The key here is that the
> settings above need to assure that you stay below the max configured number of connections, e.g.:
>     CONFIG proxy.config.net.connections_throttle INT 75000
> I'm suggesting that we add one (or two) new configuration options, and appropriate YTS code support, to instead of
> specifying timeouts, we specify connection limits for idle KA connections. For example:
>     CONFIG proxy.config.http.keep_alive_max_idle_connections_in INT 50000
>     CONFIG proxy.config.http_keep_alive_max_idle_connections_out INT 5000
> (one still has to be careful to leave head-room for active connections here, in the example above, 20000 connections
> could be active, which is a lot of traffic).
> These would override the idle timeouts, so one could use the max_idle connections for incoming (client) connections,
> and the idle timeouts for outgoing (origin) connections for instance.
> The benefit here is that it makes configuration not only easier, but also a lot safer for many applications.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.