[jira] [Updated] (TS-2729) Add HTTP/2 support to ATS
[
https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryo Okubo updated TS-2729:
--
Attachment: h2-14.patch
Current HTTP/2 implementation supports draft-12, but it isn't latest
specification.
After this patch is applied, you can use latest draft.
Add HTTP/2 support to ATS
-
Key: TS-2729
URL: https://issues.apache.org/jira/browse/TS-2729
Project: Traffic Server
Issue Type: New Feature
Components: HTTP/2
Reporter: Ryo Okubo
Assignee: James Peach
Labels: review
Fix For: 6.0.0
Attachments: h2-14.patch, http2-0004.patch
h2. Overview
We, CDN team of Yahoo! JAPAN, have implemented HTTP/2 support in ATS core
experimentally.
Now, it supports HTTP/2 draft-12.
http://tools.ietf.org/html/draft-ietf-httpbis-http2-12
Our implementation similar to the SPDY implementation in ATS core(TS-2431)
but we use nghttp2 library instead of spdylay to interpret HTTP/2 frames.
https://github.com/tatsuhiro-t/nghttp2
We tested NPN and ALPN negotiation.
h2. How to test it
* Install nghttp2 library, here is URL of this library:
https://github.com/tatsuhiro-t/nghttp2
* Use '--enable-http2' option to compile ATS:
{noformat}
$ ./configure --enable-http2
$ make all make install
{noformat}
* You can use '--with-openssl=dir' option.
* Need not configure anything if you just want to test HTTP/2 without SSL.
The code can recognize HTTP2, SPDY or HTTP by reading first to 3rd bytes of
requests.
* You can use nghttp in nghttp2 library(or other HTTP/2 client) to request,
for example:
{noformat}
# HTTP/2 without SSL
$ nghttp -v http://localhost/b.txt
# HTTP/2 + SSL
$ nghttp -v https://localhost/b.txt
{noformat}
h2. TODO
* -Cleanup codes.-
* Follow -http2 draft-12- and later.
* -Support ALPN.-
* Add settings related to HTTP/2 into records.config.
** it'll refer to configuration settings for SPDY on TS-2740
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TS-2729) Add HTTP/2 support to ATS
[
https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131283#comment-14131283
]
Ryo Okubo edited comment on TS-2729 at 9/12/14 8:48 AM:
Current HTTP/2 implementation supports draft-12, but it isn't latest
specification.
After h2-14.patch is applied, you can use latest draft.
was (Author: rokubo):
Current HTTP/2 implementation supports draft-12, but it isn't latest
specification.
After this patch is applied, you can use latest draft.
Add HTTP/2 support to ATS
-
Key: TS-2729
URL: https://issues.apache.org/jira/browse/TS-2729
Project: Traffic Server
Issue Type: New Feature
Components: HTTP/2
Reporter: Ryo Okubo
Assignee: James Peach
Labels: review
Fix For: 6.0.0
Attachments: h2-14.patch, http2-0004.patch
h2. Overview
We, CDN team of Yahoo! JAPAN, have implemented HTTP/2 support in ATS core
experimentally.
Now, it supports HTTP/2 draft-12.
http://tools.ietf.org/html/draft-ietf-httpbis-http2-12
Our implementation similar to the SPDY implementation in ATS core(TS-2431)
but we use nghttp2 library instead of spdylay to interpret HTTP/2 frames.
https://github.com/tatsuhiro-t/nghttp2
We tested NPN and ALPN negotiation.
h2. How to test it
* Install nghttp2 library, here is URL of this library:
https://github.com/tatsuhiro-t/nghttp2
* Use '--enable-http2' option to compile ATS:
{noformat}
$ ./configure --enable-http2
$ make all make install
{noformat}
* You can use '--with-openssl=dir' option.
* Need not configure anything if you just want to test HTTP/2 without SSL.
The code can recognize HTTP2, SPDY or HTTP by reading first to 3rd bytes of
requests.
* You can use nghttp in nghttp2 library(or other HTTP/2 client) to request,
for example:
{noformat}
# HTTP/2 without SSL
$ nghttp -v http://localhost/b.txt
# HTTP/2 + SSL
$ nghttp -v https://localhost/b.txt
{noformat}
h2. TODO
* -Cleanup codes.-
* Follow -http2 draft-12- and later.
* -Support ALPN.-
* Add settings related to HTTP/2 into records.config.
** it'll refer to configuration settings for SPDY on TS-2740
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2729) Add HTTP/2 support to ATS
[
https://issues.apache.org/jira/browse/TS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryo Okubo updated TS-2729:
--
Attachment: hpack_prototype.patch
The hpack_prototype.patch enables to handle HTTP/2 headers that's
encoded/decoded by HPACK.
http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-09
This patch has below features.
- The encoder supports essential features.
- The decoder supports all of compression format required by HPACK draft-09.
- Some regression tests.
- Decoded headers are stored into HTTPHdr object.
Large parts of this patch are implemented by Daiki Aminaka, a student who had
worked for our company as intern. thanks! :)
Add HTTP/2 support to ATS
-
Key: TS-2729
URL: https://issues.apache.org/jira/browse/TS-2729
Project: Traffic Server
Issue Type: New Feature
Components: HTTP/2
Reporter: Ryo Okubo
Assignee: James Peach
Labels: review
Fix For: 6.0.0
Attachments: h2-14.patch, hpack_prototype.patch, http2-0004.patch
h2. Overview
We, CDN team of Yahoo! JAPAN, have implemented HTTP/2 support in ATS core
experimentally.
Now, it supports HTTP/2 draft-12.
http://tools.ietf.org/html/draft-ietf-httpbis-http2-12
Our implementation similar to the SPDY implementation in ATS core(TS-2431)
but we use nghttp2 library instead of spdylay to interpret HTTP/2 frames.
https://github.com/tatsuhiro-t/nghttp2
We tested NPN and ALPN negotiation.
h2. How to test it
* Install nghttp2 library, here is URL of this library:
https://github.com/tatsuhiro-t/nghttp2
* Use '--enable-http2' option to compile ATS:
{noformat}
$ ./configure --enable-http2
$ make all make install
{noformat}
* You can use '--with-openssl=dir' option.
* Need not configure anything if you just want to test HTTP/2 without SSL.
The code can recognize HTTP2, SPDY or HTTP by reading first to 3rd bytes of
requests.
* You can use nghttp in nghttp2 library(or other HTTP/2 client) to request,
for example:
{noformat}
# HTTP/2 without SSL
$ nghttp -v http://localhost/b.txt
# HTTP/2 + SSL
$ nghttp -v https://localhost/b.txt
{noformat}
h2. TODO
* -Cleanup codes.-
* Follow -http2 draft-12- and later.
* -Support ALPN.-
* Add settings related to HTTP/2 into records.config.
** it'll refer to configuration settings for SPDY on TS-2740
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-306) enable log rotation for diags.log
[ https://issues.apache.org/jira/browse/TS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131326#comment-14131326 ] kang li commented on TS-306: I'm now working at this issue. There are two common ways to do log rotation. 1. Use pipe for log rotation Pro: Easy to configure Could take advantage of several logging tools, ie. cronolog, multilog. Con: Need additional processes to do logging. 2. Use logrotate for log rotation Pro: System level log rotation management. Con: Need extra configuration. Need to figure out how to reload log files. I prefer to use pipe to do log rotation as it’s easy to use. Is there any concern for the pipe file? Any suggestions would be appreciated. Comment from [~bcall]: I would lean towards using inotify/kqueue to see if the file has been removed or renamed and then reopen the file. There is more overhead and more complexity with the external tools with the pipe approach. -Bryan enable log rotation for diags.log - Key: TS-306 URL: https://issues.apache.org/jira/browse/TS-306 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Miles Libbey Priority: Critical Fix For: 5.3.0 (from yahoo bug 913896) Original description by Leif Hedstrom 3 years ago at 2006-12-04 12:42 There might be reasons why this file might get filled up, e.g. libraries used by plugins producing output on STDOUT/STDERR. A few suggestions have been made, to somehow rotate traffic.out. One possible solution (suggested by Ryan) is to use cronolog (http://cronolog.org/), which seems like a fine idea. Comment 1 by Joseph Rothrock 2 years ago at 2007-10-17 09:13:24 Maybe consider rolling diags.log as well. -Feature enhancement. Comment 2 by Kevin Dalley 13 months ago at 2009-03-04 15:32:18 When traffic.out gets filled up, error.log stops filing up, even though rotation is turned on. This is counter-intuitive. Rotation does not control traffic.out, but a large traffic.out will stop error.log from being written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3066) Latest master does not compile on OmniOS
[
https://issues.apache.org/jira/browse/TS-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131631#comment-14131631
]
ASF subversion and git services commented on TS-3066:
-
Commit ddd6ef71b4fde330a5109cb662a9e5ec45c6b6d3 in trafficserver's branch
refs/heads/5.1.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ddd6ef7 ]
TS-3066 Fix various build issues for OmniOS, broken since 5.0.x.
Latest master does not compile on OmniOS
Key: TS-3066
URL: https://issues.apache.org/jira/browse/TS-3066
Project: Traffic Server
Issue Type: Bug
Components: Build, Core
Affects Versions: 5.1.0
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Priority: Critical
Fix For: 5.2.0
We introduced (removed?) something between 5.0 and 5.1, where we now fail on
OmniOS with
{code}
In file included from ../../lib/ts/libts.h:66:0,
from P_EventSystem.h:34,
from EventSystem.cc:31:
../../lib/ts/ink_resolver.h:272:3: error: ‘u_int16_t’ does not name a type
u_int16_t _nstimes[INK_MAXNS]; /*% ms. */
^
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-306) enable log rotation for diags.log
[
https://issues.apache.org/jira/browse/TS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131672#comment-14131672
]
James Peach commented on TS-306:
Rotation of {{diags.log}} should work the same as rotation for all the other
logs.
enable log rotation for diags.log
-
Key: TS-306
URL: https://issues.apache.org/jira/browse/TS-306
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Reporter: Miles Libbey
Priority: Critical
Fix For: 5.3.0
(from yahoo bug 913896)
Original description
by Leif Hedstrom 3 years ago at 2006-12-04 12:42
There might be reasons why this file might get filled up, e.g. libraries used
by plugins producing output on STDOUT/STDERR. A few suggestions have been
made, to somehow rotate traffic.out. One possible solution (suggested by
Ryan) is to use cronolog (http://cronolog.org/), which seems like a fine idea.
Comment 1
by Joseph Rothrock 2 years ago at 2007-10-17 09:13:24
Maybe consider rolling diags.log as well. -Feature enhancement.
Comment 2
by Kevin Dalley 13 months ago at 2009-03-04 15:32:18
When traffic.out gets filled up, error.log stops filing up, even though
rotation is turned on. This is
counter-intuitive. Rotation does not control traffic.out, but a large
traffic.out will stop error.log from being
written.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin
[ https://issues.apache.org/jira/browse/TS-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-2314: -- Attachment: (was: TS-2314.diff) New config to allow unsatifiable Range: request to go straight to Origin Key: TS-2314 URL: https://issues.apache.org/jira/browse/TS-2314 Project: Traffic Server Issue Type: Bug Components: Core Reporter: jaekyung oh Labels: range Attachments: TS-2314.diff Basically read_while_writer works fine when ATS handles normal file. In progressive download and playback of mp4 in which moov atom is placed at the end of the file, ATS makes and returns wrong response for range request from unfulfilled cache when read_while_writer is 1. In origin, apache has h264 streaming module. Everything is ok whether the moov atom is placed at the beginning of the file or not in origin except a range request happens with read_while_writer. Mostly our customer’s contents placed moov atom at the end of the file and in the case movie player stops playing when it seek somewhere in the movie. to check if read_while_writer works fine, 1. prepare a mp4 file whose moov atom is placed at the end of the file. 2. curl --range - http://www.test.com/mp4/test.mp4 1 no_cache_from_origin 3. wget http://www.test.com/mp4/test.mp4 4. right after wget, execute “curl --range - http://www.test.com/mp4/test.mp4 1 from_read_while_writer” on other terminal (the point is sending range request while ATS is still downloading) 5. after wget gets done, curl --range - http://www.test.com/mp4/test.mp4 1 from_cache 6. you can check compare those files by bindiff. The response from origin(no_cache_from_origin) for the range request is exactly same to from_cache resulted from #5's range request. but from_read_while_writer from #4 is totally different from others. i think a range request should be forwarded to origin server if it can’t find the content with the offset in cache even if the read_while_writer is on, instead ATS makes(from where?) and sends wrong response. (In squid.log it indicates TCP_HIT) That’s why a movie player stops when it seeks right after the movie starts. Well. we turned off read_while_writer and movie play is ok but the problems is read_while_writer is global options. we can’t set it differently for each remap entry by conf_remap. So the downloading of Big file(not mp4 file) gives overhead to origin server because read_while_writer is off. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-2314) New config to allow unsatifiable Range: request to go straight to Origin
[ https://issues.apache.org/jira/browse/TS-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-2314: -- Attachment: TS-2314.diff Update the patch to set cache_lookup_result to CACHE_MISS to avoid a loop when proxy.config.http.cache.range.write is set to 1 New config to allow unsatifiable Range: request to go straight to Origin Key: TS-2314 URL: https://issues.apache.org/jira/browse/TS-2314 Project: Traffic Server Issue Type: Bug Components: Core Reporter: jaekyung oh Labels: range Attachments: TS-2314.diff, TS-2314.diff Basically read_while_writer works fine when ATS handles normal file. In progressive download and playback of mp4 in which moov atom is placed at the end of the file, ATS makes and returns wrong response for range request from unfulfilled cache when read_while_writer is 1. In origin, apache has h264 streaming module. Everything is ok whether the moov atom is placed at the beginning of the file or not in origin except a range request happens with read_while_writer. Mostly our customer’s contents placed moov atom at the end of the file and in the case movie player stops playing when it seek somewhere in the movie. to check if read_while_writer works fine, 1. prepare a mp4 file whose moov atom is placed at the end of the file. 2. curl --range - http://www.test.com/mp4/test.mp4 1 no_cache_from_origin 3. wget http://www.test.com/mp4/test.mp4 4. right after wget, execute “curl --range - http://www.test.com/mp4/test.mp4 1 from_read_while_writer” on other terminal (the point is sending range request while ATS is still downloading) 5. after wget gets done, curl --range - http://www.test.com/mp4/test.mp4 1 from_cache 6. you can check compare those files by bindiff. The response from origin(no_cache_from_origin) for the range request is exactly same to from_cache resulted from #5's range request. but from_read_while_writer from #4 is totally different from others. i think a range request should be forwarded to origin server if it can’t find the content with the offset in cache even if the read_while_writer is on, instead ATS makes(from where?) and sends wrong response. (In squid.log it indicates TCP_HIT) That’s why a movie player stops when it seeks right after the movie starts. Well. we turned off read_while_writer and movie play is ok but the problems is read_while_writer is global options. we can’t set it differently for each remap entry by conf_remap. So the downloading of Big file(not mp4 file) gives overhead to origin server because read_while_writer is off. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3023) Support space separated values in inline plugin parameters in remap rules
[ https://issues.apache.org/jira/browse/TS-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131735#comment-14131735 ] ASF subversion and git services commented on TS-3023: - Commit 85afd76e07380161dc3268a1b5d3bdd7286a9527 in trafficserver's branch refs/heads/master from [~sudheerv] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=85afd76 ] [TS-3023] - Support space separated values in inline plugin parameters in remap rules Support space separated values in inline plugin parameters in remap rules - Key: TS-3023 URL: https://issues.apache.org/jira/browse/TS-3023 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Sudheer Vinukonda Fix For: 5.2.0 Attachments: TS-3023.diff While reviewing and testing TS-2947, Leif found that, space separated values are not supported correctly for inline plugin params whereas, they work as expected when specified in the config file. For example, @pparam=proxy.config.foo='bar beer' results only in setting proxy.config.foo=bar whereas CONFIG proxy.config.foo STRING 'bar beer' results in setting proxy.config.foo='bar beer' Further analysis revealed that the limitation is in parsing/tokenizing the input, which always treats space or tab as delimiters, regardless of whether they are included within quotes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-2955) support variable expansion in set-redirect operator for header_rewrite
[
https://issues.apache.org/jira/browse/TS-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131739#comment-14131739
]
ASF subversion and git services commented on TS-2955:
-
Commit 243d1b13fa34098e6d9fe1c218f0133b66a6cfc9 in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=243d1b1 ]
[TS-2955] - support variable expansion in set-redirect operator for
header_rewrite
support variable expansion in set-redirect operator for header_rewrite
--
Key: TS-2955
URL: https://issues.apache.org/jira/browse/TS-2955
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Reporter: Sudheer Vinukonda
Assignee: Leif Hedstrom
Labels: review, yahoo
Fix For: 5.2.0
Attachments: TS-2955.diff
support variable expansion in set-redirect operator for header_rewrite to be
able to dynamically substitute variables in the Location header (currently,
only %{PATH} is supported).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3035) Double logging on errored transactions
[
https://issues.apache.org/jira/browse/TS-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131746#comment-14131746
]
ASF subversion and git services commented on TS-3035:
-
Commit a56319eee7556c10c7f473ab2b4a5fe1907025c8 in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a56319e ]
[TS-3035] - fix duplicate logging on error transactions
Double logging on errored transactions
--
Key: TS-3035
URL: https://issues.apache.org/jira/browse/TS-3035
Project: Traffic Server
Issue Type: Bug
Components: Core, Logging
Reporter: Brian Geffon
Assignee: Brian Geffon
Fix For: 5.2.0
Attachments: TS-3035.diff
When an error occurs it results in transactions being logged twice, an
example is:
{code}
1408720751.393 0 72.52.91.30 ERR_CONNECT_FAIL 404 0 Accept-Language:
https://en-US,en;q=0.8/ - NONE/- - https://en-US,en;q=0.8/ f1 f2 f3 f4
1408720751.393 0 72.52.91.30 ERR_CONNECT_FAIL 404 1820 Accept-Language:
https://en-US,en;q=0.8/ - NONE/- text/html https://en-US,en;q=0.8/ f1 f2 f3 f4
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-2938) Core dump in HttpSM::redirect_request when handling 307
[
https://issues.apache.org/jira/browse/TS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14131754#comment-14131754
]
ASF subversion and git services commented on TS-2938:
-
Commit 1736377ce48d51ac29bd4e76ddb626b6e9ed95ea in trafficserver's branch
refs/heads/master from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1736377 ]
[TS-2938] - Fix core dump in 307 redirect follow handling
Core dump in HttpSM::redirect_request when handling 307
---
Key: TS-2938
URL: https://issues.apache.org/jira/browse/TS-2938
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Sudheer Vinukonda
Assignee: James Peach
Labels: yahoo
Fix For: 5.2.0
Attachments: TS-2938.diff
Below is the gdb back trace and other info. Looks like
t_state.hdr_info.server_request is not valid when handling 307.
{code}
#0 method_get (this=0x2b294c6c4dd0,
redirect_url=0x2b2a1ff0d914
http://ads.unister-gmbh.de/newsletter_img/aidude/template/countdown/hfr/countdown180.gif\r\nCache-Control:
max-age=600, public, must-revalidate\r\nVary:
Accept-Encoding\r\nContent-Encoding: gzip\r\nContent-Ty...,
redirect_len=value optimized out) at ../../proxy/hdrs/HTTP.h:1031
#1 HttpSM::redirect_request (this=0x2b294c6c4dd0,
redirect_url=0x2b2a1ff0d914
http://ads.unister-gmbh.de/newsletter_img/aidude/template/countdown/hfr/countdown180.gif\r\nCache-Control:
max-age=600, public, must-revalidate\r\nVary:
Accept-Encoding\r\nContent-Encoding: gzip\r\nContent-Ty...,
redirect_len=value optimized out) at HttpSM.cc:7416
#2 0x00599dcb in HttpSM::do_redirect (this=0x2b294c6c4dd0) at
HttpSM.cc:7350
#3 0x005aa968 in HttpSM::set_next_state (this=0x2b294c6c4dd0) at
HttpSM.cc:7050
#4 0x005ac462 in HttpSM::handle_api_return (this=0x2b294c6c4dd0) at
HttpSM.cc:1505
#5 0x005a48e0 in HttpSM::state_api_callout (this=0x2b294c6c4dd0,
event=0, data=0x0) at HttpSM.cc:1437
#6 0x005aa302 in HttpSM::set_next_state (this=0x2b294c6c4dd0) at
HttpSM.cc:6830
#7 0x005ac462 in HttpSM::handle_api_return (this=0x2b294c6c4dd0) at
HttpSM.cc:1505
#8 0x005a48e0 in HttpSM::state_api_callout (this=0x2b294c6c4dd0,
event=0, data=0x0) at HttpSM.cc:1437
#9 0x005aa302 in HttpSM::set_next_state (this=0x2b294c6c4dd0) at
HttpSM.cc:6830
#10 0x005ac462 in HttpSM::handle_api_return (this=0x2b294c6c4dd0) at
HttpSM.cc:1505
#11 0x005a48e0 in HttpSM::state_api_callout (this=0x2b294c6c4dd0,
event=0, data=0x0) at HttpSM.cc:1437
#12 0x005a7710 in do_api_callout (this=0x2b294c6c4dd0, event=value
optimized out, data=0xb050) at HttpSM.cc:444
#13 setup_cache_lookup_complete_api (this=0x2b294c6c4dd0, event=value
optimized out, data=0xb050) at HttpSM.cc:2403
#14 HttpSM::state_cache_open_read (this=0x2b294c6c4dd0, event=value
optimized out, data=0xb050) at HttpSM.cc:2459
#15 0x005a7418 in HttpSM::main_handler (this=0x2b294c6c4dd0,
event=1103, data=0xb050) at HttpSM.cc:2501
#16 0x00585882 in handleEvent (this=0x2b294c6c67a0, event=1103,
data=0xb050) at ../../iocore/eventsystem/I_Continuation.h:146
#17 HttpCacheSM::state_cache_open_read (this=0x2b294c6c67a0, event=1103,
data=0xb050) at HttpCacheSM.cc:137
#18 0x006dbf5e in Cache::open_read (this=value optimized out,
cont=0x2b294c6c67a0, key=value optimized out, request=0x2b294c6c54d8,
params=0x2b294c6c4eb0,
type=value optimized out,
hostname=0x2b2977c3aaeb
ads.unister-gmbh.denewsletter_img/aidude/template/countdown/hfr/countdown180.gifhttpads.unister-gmbh.denewsletter_img/aidude/template/countdown/hfr/countdown180.gifhttpads.unister-gmbh.denewsletter_im...,
host_len=19) at CacheRead.cc:143
#19 0x006bcb9d in open_read (this=value optimized out,
cont=0x2b294c6c67a0, url=0x2b294c6c54f0, cluster_cache_local=value optimized
out, request=0x2b294c6c54d8,
params=0x2b294c6c4eb0, pin_in_cache=0, type=CACHE_FRAG_TYPE_HTTP) at
P_CacheInternal.h:1079
#20 CacheProcessor::open_read (this=value optimized out,
cont=0x2b294c6c67a0, url=0x2b294c6c54f0, cluster_cache_local=value optimized
out, request=0x2b294c6c54d8, params=0x2b294c6c4eb0,
pin_in_cache=0, type=CACHE_FRAG_TYPE_HTTP) at Cache.cc:3440
#21 0x00585334 in do_cache_open_read (this=0x2b294c6c67a0, url=value
optimized out, hdr=value optimized out, params=value optimized out,
pin_in_cache=value optimized out)
at HttpCacheSM.cc:216
#22 HttpCacheSM::open_read (this=0x2b294c6c67a0, url=value optimized out,
hdr=value optimized out, params=value optimized out, pin_in_cache=value
[jira] [Updated] (TS-3070) consistent span configuration
[ https://issues.apache.org/jira/browse/TS-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach updated TS-3070: Attachment: TS-3070.patch consistent span configuration - Key: TS-3070 URL: https://issues.apache.org/jira/browse/TS-3070 Project: Traffic Server Issue Type: Bug Components: Cache, Core Reporter: James Peach Assignee: James Peach Fix For: 5.2.0 Attachments: TS-3070.patch The span configuration is not consistent across platforms because the code is duplicated for Linux, Solaris and the BSD family. We should refactor this code so that cache files and directories are handled consistently and only the disk geometry probing is platform specific. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-3072) Debug logging for a single connection in production traffic.
Sudheer Vinukonda created TS-3072: - Summary: Debug logging for a single connection in production traffic. Key: TS-3072 URL: https://issues.apache.org/jira/browse/TS-3072 Project: Traffic Server Issue Type: Improvement Components: Core, Logging Reporter: Sudheer Vinukonda Presently, when there's a production issue (e.g. TS-3049, TS-2983 etc), it is really hard to isolate/debug with the high traffic. Turning on debug logs in traffic is unfortunately not an option due to performance impacts. Even if you took a performance hit and turned on the logs, it is just as hard to separate out the logs for a single connection/transaction among the millions of the logs output in a short period of time. I think it would be good if there's a way to turn on debug logs in a controlled manner in production environment. One simple option is to support a config setting for example, with a client-ip, which when set, would turn on debug logs for any connection made by just that one client. If needed, instead of one client-ip, we may allow configuring up to 'n' (say, 5) client-ips. If there are other ideas, please comment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3072) Debug logging for a single connection in production traffic.
[ https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-3072: -- Affects Version/s: 5.0.1 Fix Version/s: 5.2.0 Labels: Yahoo (was: ) Debug logging for a single connection in production traffic. Key: TS-3072 URL: https://issues.apache.org/jira/browse/TS-3072 Project: Traffic Server Issue Type: Improvement Components: Core, Logging Affects Versions: 5.0.1 Reporter: Sudheer Vinukonda Labels: Yahoo Fix For: 5.2.0 Presently, when there's a production issue (e.g. TS-3049, TS-2983 etc), it is really hard to isolate/debug with the high traffic. Turning on debug logs in traffic is unfortunately not an option due to performance impacts. Even if you took a performance hit and turned on the logs, it is just as hard to separate out the logs for a single connection/transaction among the millions of the logs output in a short period of time. I think it would be good if there's a way to turn on debug logs in a controlled manner in production environment. One simple option is to support a config setting for example, with a client-ip, which when set, would turn on debug logs for any connection made by just that one client. If needed, instead of one client-ip, we may allow configuring up to 'n' (say, 5) client-ips. If there are other ideas, please comment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
