You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "M. Nunberg (JIRA)" <ji...@apache.org> on 2011/08/15 23:57:27 UTC
[jira] [Created] (TS-918) Allow interval-based rotation for round
robin entries
Allow interval-based rotation for round robin entries
-----------------------------------------------------
Key: TS-918
URL: https://issues.apache.org/jira/browse/TS-918
Project: Traffic Server
Issue Type: New Feature
Components: DNS
Reporter: M. Nunberg
Attachments: timed_round_robin.patch
This patch allows trafficserver to rotate round-robin DNS entries based on interval rather than frequency.
This is beneficial for HTTP keepalive when there are a small amount of client requests scaled over multiple clients.
Thus, for e.g. google which tends to return 4-5 RR/SA entries, the normal behavior would be to open 5 TCP connections to google if five clients requested five objects (or even if a single client requested 5 objects, if strict round robin is enabled).
This patch would help in such situations by making round robin rotation based on an absolute interval, so requests are forwarded to a single TCP connection for each interval. After the interval expires, the DNS RR entry is rotated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-918) Allow interval-based rotation for round
robin entries
Posted by "M. Nunberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
M. Nunberg updated TS-918:
--------------------------
Attachment: timed_round_robin.patch
> Allow interval-based rotation for round robin entries
> -----------------------------------------------------
>
> Key: TS-918
> URL: https://issues.apache.org/jira/browse/TS-918
> Project: Traffic Server
> Issue Type: New Feature
> Components: DNS
> Reporter: M. Nunberg
> Attachments: timed_round_robin.patch
>
>
> This patch allows trafficserver to rotate round-robin DNS entries based on interval rather than frequency.
> This is beneficial for HTTP keepalive when there are a small amount of client requests scaled over multiple clients.
> Thus, for e.g. google which tends to return 4-5 RR/SA entries, the normal behavior would be to open 5 TCP connections to google if five clients requested five objects (or even if a single client requested 5 objects, if strict round robin is enabled).
> This patch would help in such situations by making round robin rotation based on an absolute interval, so requests are forwarded to a single TCP connection for each interval. After the interval expires, the DNS RR entry is rotated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-918) Allow interval-based rotation for round
robin entries
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-918:
-----------------------------
Fix Version/s: 3.1.0
> Allow interval-based rotation for round robin entries
> -----------------------------------------------------
>
> Key: TS-918
> URL: https://issues.apache.org/jira/browse/TS-918
> Project: Traffic Server
> Issue Type: New Feature
> Components: DNS
> Reporter: M. Nunberg
> Fix For: 3.1.0
>
> Attachments: timed_round_robin.patch
>
>
> This patch allows trafficserver to rotate round-robin DNS entries based on interval rather than frequency.
> This is beneficial for HTTP keepalive when there are a small amount of client requests scaled over multiple clients.
> Thus, for e.g. google which tends to return 4-5 RR/SA entries, the normal behavior would be to open 5 TCP connections to google if five clients requested five objects (or even if a single client requested 5 objects, if strict round robin is enabled).
> This patch would help in such situations by making round robin rotation based on an absolute interval, so requests are forwarded to a single TCP connection for each interval. After the interval expires, the DNS RR entry is rotated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira