Instead of reopening, which gets weird with the release notes, maybe create a new JIRA?
> On Jan 16, 2015, at 10:32 AM, Bryan Call (JIRA) <[email protected]> wrote: > > > [ > https://issues.apache.org/jira/browse/TS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Bryan Call reopened TS-153: > --------------------------- > > I have updates after running this feature in production for ~1 week. > > Changes: > 1. Changed the limit on the number of connections to include all incoming > connections instead of just ones that are idle. This will keep the number of > incoming connections per thread more consistent. > 2. Change the double link list to a queue. > 3. When adding to the queue if the connection is already in the queue remove > it and then add it to the end the queue. > 4. Properly close the connection by mimicking what inactivity cop does to > close the connection. > 5. Add stats to determine the average KA timeout since it is now dynamic. > 6. Added support for spdy connections. > > New config name: > proxy.config.net.max_connections_in > > New stats: > proxy.process.net.dynamic_keep_alive_timeout_in_total > proxy.process.net.dynamic_keep_alive_timeout_in_count > > >> "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 >> Assignee: Bryan Call >> Priority: Minor >> Labels: A >> Fix For: 5.3.0 >> >> Attachments: ts153.diff >> >> >> (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 TS 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 was sent by Atlassian JIRA > (v6.3.4#6332)
