[jira] [Resolved] (TS-57) Logging: IP's being logged in text mode when binary mode enabled for logging
[ https://issues.apache.org/jira/browse/TS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan M. Carroll resolved TS-57. --- Resolution: Fixed Fix Version/s: (was: 3.3.0) 3.1.2 Assignee: Alan M. Carroll (was: George Paul) Fixed by TS-989. > Logging: IP's being logged in text mode when binary mode enabled for logging > - > > Key: TS-57 > URL: https://issues.apache.org/jira/browse/TS-57 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.0a > Environment: All platforms >Reporter: George Paul >Assignee: Alan M. Carroll >Priority: Trivial > Fix For: 3.1.2 > > > It was reported that IP's were being logged in text mode when binary logging > was enabled. This needs to be investigated and addressed if needed. > -George -- 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] [Created] (TS-1108) Allow to "clear" a particular cache volume
Allow to "clear" a particular cache volume -- Key: TS-1108 URL: https://issues.apache.org/jira/browse/TS-1108 Project: Traffic Server Issue Type: New Feature Components: Cache Reporter: Leif Hedstrom Today, you can clear the entire cache (either at startup, or via e.g. -Cclear_cache). This wipes the entire cache. For someone hosting a "small" number of sites, it might be reasonable to partition the cache (using volume.config and hosting.config), such that each site gets a fraction of the cache. In such a setup, it would also be reasonable (and usable) to be able to clear just a single volume (e..g -Cclear_cache_volume 1 or some such). Thoughts? -- 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] [Created] (TS-1107) dynamically scale the number of net threads
dynamically scale the number of net threads --- Key: TS-1107 URL: https://issues.apache.org/jira/browse/TS-1107 Project: Traffic Server Issue Type: New Feature Components: Core, Performance Reporter: James Peach Priority: Minor The number of net threads is calculated once at startup, but we ought to consider dynamically scaling the number of threads a runtime based on load. zwoop: right, that's what I meant (keep a counter of how many times epoll had no events, and treat that as an "idle" thread) zwoop: probably a multiplier of some setting (thread_idle_seconds or some such) zwoop: this would be a cool feature, if you have the time for it ;) zwoop: can keep the original calculations / settings as the "upper" limit I think zwoop: (the calculations can also easily be configured in records.config, so that people can modify that upper limit) zwoop: an ideal solution (backward compatible) would be to just add one new setting, or some such, default to 0 (off). With it not set, our normal logic applies. With it set, your stuff takes effect, but cap it at whatever the other settings are. -- 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-1055) Wrong implementation of TSHttpSsnArgGet
[
https://issues.apache.org/jira/browse/TS-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Galić updated TS-1055:
---
Backport to Version: (was: 3.0.3)
Fix Version/s: 3.0.3
backported in 63f2267d28daa840712d3ea15d49495c18572f0e
> Wrong implementation of TSHttpSsnArgGet
> ---
>
> Key: TS-1055
> URL: https://issues.apache.org/jira/browse/TS-1055
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
>Affects Versions: 3.1.1
>Reporter: Yakov Kopel
>Assignee: Igor Galić
> Labels: api-change
> Fix For: 3.1.2, 3.0.3
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> There is a different between the interface of TSHttpSsnArgGet and it
> implemenation.
> In the interface (proxy/api/ts/ts.h.in):
> tsapi void* TSHttpSsnArgGet(TSHttpSsn ssnp, int arg_idx);
> In the implementation(proxy/InkAPI.cc):
> void * TSHttpSsnArgGet(TSHttpSsn ssnp, int arg_idx, void **argp)
> So, I wrote a simple patch to fix this problem:
> Index: InkAPI.cc
> ===
> --- InkAPI.cc (revision 1220421)
> +++ InkAPI.cc (working copy)
> @@ -5500,7 +5500,7 @@
> }
> void *
> -TSHttpSsnArgGet(TSHttpSsn ssnp, int arg_idx, void **argp)
> +TSHttpSsnArgGet(TSHttpSsn ssnp, int arg_idx)
> {
>sdk_assert(sdk_sanity_check_http_ssn(ssnp) == TS_SUCCESS);
>sdk_assert(arg_idx >= 0 && arg_idx < HTTP_SSN_TXN_MAX_USER_ARG);
--
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-1066) improve ssl port documentation
[ https://issues.apache.org/jira/browse/TS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Galić updated TS-1066: --- Fix Version/s: 3.0.3 > improve ssl port documentation > -- > > Key: TS-1066 > URL: https://issues.apache.org/jira/browse/TS-1066 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: James Peach >Assignee: Igor Galić >Priority: Minor > Fix For: 3.0.3 > > > Setting up SSL termination is documented as needing the > proxy.config.ssl.server_port option. > However you can do this using the proxy.config.http.server_other_ports > option, but not all of the relevant attributes are documented. > So I think that that: > # The documentation of proxy.config.http.server_other_ports can be improved > to document the port attribute syntax. > # The "S<>=" attributes should be documented. > # The interaction of proxy.config.ssl.server_port and > proxy.config.http.server_other_ports should be documented. > # The proxy.config.ssl.server_port could be deprecated in favour of > server_other_ports. -- 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-1066) improve ssl port documentation
[ https://issues.apache.org/jira/browse/TS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204566#comment-13204566 ] Igor Galić commented on TS-1066: I'm confuzzled by the comments and the resolution and the subversion commits and the fact that I just backported it... > improve ssl port documentation > -- > > Key: TS-1066 > URL: https://issues.apache.org/jira/browse/TS-1066 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: James Peach >Assignee: Igor Galić >Priority: Minor > > Setting up SSL termination is documented as needing the > proxy.config.ssl.server_port option. > However you can do this using the proxy.config.http.server_other_ports > option, but not all of the relevant attributes are documented. > So I think that that: > # The documentation of proxy.config.http.server_other_ports can be improved > to document the port attribute syntax. > # The "S<>=" attributes should be documented. > # The interaction of proxy.config.ssl.server_port and > proxy.config.http.server_other_ports should be documented. > # The proxy.config.ssl.server_port could be deprecated in favour of > server_other_ports. -- 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] [Assigned] (TS-1066) improve ssl port documentation
[ https://issues.apache.org/jira/browse/TS-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Galić reassigned TS-1066: -- Assignee: Igor Galić (was: James Peach) > improve ssl port documentation > -- > > Key: TS-1066 > URL: https://issues.apache.org/jira/browse/TS-1066 > Project: Traffic Server > Issue Type: Improvement > Components: Documentation >Reporter: James Peach >Assignee: Igor Galić >Priority: Minor > > Setting up SSL termination is documented as needing the > proxy.config.ssl.server_port option. > However you can do this using the proxy.config.http.server_other_ports > option, but not all of the relevant attributes are documented. > So I think that that: > # The documentation of proxy.config.http.server_other_ports can be improved > to document the port attribute syntax. > # The "S<>=" attributes should be documented. > # The interaction of proxy.config.ssl.server_port and > proxy.config.http.server_other_ports should be documented. > # The proxy.config.ssl.server_port could be deprecated in favour of > server_other_ports. -- 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
