[jira] [Created] (TS-1075) Port range bottleneck in transparent proxy mode
Port range bottleneck in transparent proxy mode --- Key: TS-1075 URL: https://issues.apache.org/jira/browse/TS-1075 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.1 Environment: Centos 5.6, kernel 2.6.39.2 compiled with TPROXY support ATS compiled as: ./configure --enable-tproxy Reporter: Danny Shporer The Linux TPROXY stack only takes into account the local addresses when using dynamic bind (bind without specifying a specific port). This limits the port range to only the local range (around 30K by default and can be extended to around 64K) - this together with the TIME-WAIT Linux method of releasing ports causes a bottleneck). One symptom of this is that traffic_cop cannot open a connection to the server to monitor it (it gets error 99 - address already in use) and kills it. Another issue is when opening the connection to the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1075) Port range bottleneck in transparent proxy mode
[ https://issues.apache.org/jira/browse/TS-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Shporer updated TS-1075: -- Attachment: ports.patch This is a pssible fix for this issue for your review. I have used this fix for a while now and it seems to work. It forces traffic cop to bind to specific port to monitor the server - since I am using it on a specific system I took the liberty of hardcoding it (you may want to make it configurable). Regarding the connection to the server, it binds to a random port based on gettimeofday. Port range bottleneck in transparent proxy mode --- Key: TS-1075 URL: https://issues.apache.org/jira/browse/TS-1075 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.0.1 Environment: Centos 5.6, kernel 2.6.39.2 compiled with TPROXY support ATS compiled as: ./configure --enable-tproxy Reporter: Danny Shporer Attachments: ports.patch The Linux TPROXY stack only takes into account the local addresses when using dynamic bind (bind without specifying a specific port). This limits the port range to only the local range (around 30K by default and can be extended to around 64K) - this together with the TIME-WAIT Linux method of releasing ports causes a bottleneck). One symptom of this is that traffic_cop cannot open a connection to the server to monitor it (it gets error 99 - address already in use) and kills it. Another issue is when opening the connection to the server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1048) Add TS API to enable plugins to use traffic server configuration infrastructure
[ https://issues.apache.org/jira/browse/TS-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13182200#comment-13182200 ] bianca cooper commented on TS-1048: --- Leif: looks great. thanks Add TS API to enable plugins to use traffic server configuration infrastructure Key: TS-1048 URL: https://issues.apache.org/jira/browse/TS-1048 Project: Traffic Server Issue Type: Improvement Components: Configuration, TS API Environment: Centos 6 Reporter: bianca cooper Assignee: Leif Hedstrom Priority: Minor Labels: api-addition, configuration Fix For: 3.1.2 Attachments: TS-1048.diff, diff.txt Original Estimate: 72h Remaining Estimate: 72h Export RecRegisterConfigInt and RecRegisterConfigString to enable adding a configuration record to the records hashtable. Once plugin new configuration records should be added, the addition will be done by calling the API in the plugin code. No need to add the record to RecordsConfig static array. No need to recompile the ATS each time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
