[jira] [Updated] (TS-2391) Traffic Server tries to reverse resolve 127.0.0.1
[
https://issues.apache.org/jira/browse/TS-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Carlin updated TS-2391:
-
Description:
We have a number of remaps using 127.0.0.1 for serving healthchecks. Bryan
Call noticed ATS seems to try and resolve 1.0.0.127.in-addr.arpa for every one
of the requests (there are a lot, sometimes hundreds per second).
Occasionally this process hangs; If I grep squid.blog for 127.0.0.1 I'll see
the healthcheck log entries flowing and then all of a sudden it'll stop
anywhere from 15-80 seconds. Then the backlog of healthchecks is cleared out
at once. 5-20 minutes later this process will recur.
From traffic.out with debug dns.*|hostdb.* - this occurs continuously.
Lookup for 1.0.0.127.in-addr.arpa fails (NXDOMAIN) and it doesn't get added to
HostDB.
Unsure if related, but TS-852 seemed similar.
{noformat}
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) received query type
= 12, timeout = 0
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) enqueing query
1.0.0.127.in-addr.arpa
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) adding first to
collapsing queue
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) send query
(qtype=12) for 1.0.0.127.in-addr.arpa to fd 236
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) sent qname =
1.0.0.127.in-addr.arpa, id = 56887, nameserver = 0
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) sent_one:
failover_number for resolver 0 is 1
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) received packet size
= 109
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) primary DNS response
code = 0
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) received rcode = 3
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) DNS error 3 for
[1.0.0.127.in-addr.arpa]
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) send query
(qtype=12) for to fd 236
[Nov 24 20:40:46.619] Server {0x2b759c8953a0} DEBUG: (dns) sent qname = , id =
4497, nameserver = 0
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) sent_one:
failover_number for resolver 0 is 1
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) received packet size
= 92
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) primary DNS response
code = 0
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) received rcode = 0
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) DNS error 0 for []
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) FAIL result for =
not found retry 0
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (dns) called back
continuation for
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (hostdb) probe
aa30de0f80a82135 1 [ignore_timeout = 1]
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (hostdb) '' failed
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (hostdb) fail timeout 0
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (hostdb) failed for
127.0.0.1
[Nov 24 20:40:46.620] Server {0x2b759c8953a0} DEBUG: (hostdb) inserting for: :
(md5: aa30de0f80a82135) bucket: 1017 now: 1385325494 timeout: 0 ttl: 0
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) probe 127.0.0.1
9993e35a45b4be6a 1 [ignore_timeout = 0]
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) immediate answer
for 127.0.0.1
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) probe
aa30de0f80a82135 1 [ignore_timeout = 0]
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) '' failed
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) fail timeout 0
[Nov 24 20:40:46.707] Server {0x2b759d74e700} DEBUG: (hostdb) delaying force 0
answer for 127.0.0.1
[Nov 24 20:40:46.707] Server {0x2b759c8953a0} DEBUG: (hostdb) probe
aa30de0f80a82135 1 [ignore_timeout = 0]
[Nov 24 20:40:46.708] Server {0x2b759c8953a0} DEBUG: (hostdb) '' failed
[Nov 24 20:40:46.708] Server {0x2b759c8953a0} DEBUG: (hostdb) fail timeout 0
[Nov 24 20:40:46.708] Server {0x2b759c8953a0} DEBUG: (hostdb) DNS IP 127.0.0.1
{noformat}
YTS doesn't have this issue:
{noformat}
bash-3.2# traffic_server -k
[Nov 24 20:18:11.941] {4146358528} STATUS: opened /home/y/logs/yts/diags.log
[Nov 24 20:18:11.959] Server {4146358528} DEBUG: (dns) ink_dns_init: called
with init_called = 0
[Nov 24 20:18:11.992] Server {4146358528} DEBUG: (dns) initial
dns_sequence_number = 10131
[Nov 24 20:18:11.993] Server {4146358528} DEBUG: (dns) localhost=hostname
redacted
[Nov 24 20:18:11.993] Server {4146358528} DEBUG: (dns) Round-robin nameservers
= 0
[Nov 24 20:18:12.554] Server {4146358528} DEBUG: (dns) DNSHandler::startEvent:
on thread0
[Nov 24 20:18:12.554] Server {4146358528} DEBUG: (dns) open_con: opening
connection dns server ip redacted:53
[Nov 24 20:18:12.554] Server {4146358528} DEBUG: (dns) random port = 28292
[Nov 24 20:18:12.554] Server {4146358528}
[jira] [Assigned] (TS-2386) clean up unused files and codes -- round 4.2
[ https://issues.apache.org/jira/browse/TS-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2386: - Assignee: Zhao Yongming clean up unused files and codes -- round 4.2 Key: TS-2386 URL: https://issues.apache.org/jira/browse/TS-2386 Project: Traffic Server Issue Type: Task Components: Cleanup Reporter: Zhao Yongming Assignee: Zhao Yongming Fix For: 4.2.0 nuke unused files and codes, as we want to -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2386) clean up unused files and codes -- round 4.2
[ https://issues.apache.org/jira/browse/TS-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831087#comment-13831087 ] Leif Hedstrom commented on TS-2386: --- zym: Can this be closed ? clean up unused files and codes -- round 4.2 Key: TS-2386 URL: https://issues.apache.org/jira/browse/TS-2386 Project: Traffic Server Issue Type: Task Components: Cleanup Reporter: Zhao Yongming Assignee: Zhao Yongming Fix For: 4.2.0 nuke unused files and codes, as we want to -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2387) traffic_top should resize to the terminal window size
[ https://issues.apache.org/jira/browse/TS-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2387: -- Fix Version/s: 4.2.0 traffic_top should resize to the terminal window size - Key: TS-2387 URL: https://issues.apache.org/jira/browse/TS-2387 Project: Traffic Server Issue Type: Improvement Components: Console, Management Reporter: James Peach Assignee: Bryan Call Fix For: 4.2.0 traffic_top is hard-coded to draw a 80x24 window. It would be much better if it queried the window size and drew itself with the actual window dimensions. Bonus points for resizing when the terminal window size changes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2392) Enable elliptic curve ciphers to support forward secrecy
[
https://issues.apache.org/jira/browse/TS-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan-Frode Myklebust updated TS-2392:
Description:
ATS does not seem to support the elliptic curve diffie hellman ephemeral key
exchanges (ECDH) that are available in openssl. It seems these needs to be
enabled explicitly to take advantage of them. Ref: the following commit for how
this support was added to apache httpd v2.3.3:
http://mail-archives.apache.org/mod_mbox/httpd-cvs/200911.mbox/%3c20091110075514.166a62388...@eris.apache.org%3E
and for stud:
https://github.com/bumptech/stud/pull/61/files
Maybe both a DH key exchange needs to be set up, and then the various elliptic
curves needs to be initialized..?
Checking the openssl docs, I see SSL_CTX_set_tmp_dh_callback() needs to be
called to set up the ephemeral keys:
http://www.openssl.org/docs/ssl/SSL_CTX_set_tmp_dh_callback.html
https://tech.immerda.ch/2011/11/the-state-of-forward-secrecy-in-openssl/
http://wiki.openssl.org/index.php/Elliptic_Curve_Diffie_Hellman
And these are the named curves available with openssl-1.0.1e-16.el6_5.x86_64 on
RHEL-6.5:
{noformat}
$ openssl ecparam -list_curves
secp384r1 : NIST/SECG curve over a 384 bit prime field
prime256v1: X9.62/SECG curve over a 256 bit prime field
{noformat}
was:
ATS does not seem to support the elliptic curve diffie hellman ephemeral key
exchanges (ECDH) that are available in openssl. It seems these needs to be
enabled explicitly to take advantage of them. Ref: the following commit for how
this support was added to apache httpd v2.3.3:
http://mail-archives.apache.org/mod_mbox/httpd-cvs/200911.mbox/%3c20091110075514.166a62388...@eris.apache.org%3E
and for stud:
https://github.com/bumptech/stud/pull/61/files
Maybe both a DH key exchange needs to be set up, and then the various elliptic
curves needs to be initialized..?
Checking the openssl docs, I see SSL_CTX_set_tmp_dh_callback() needs to be
called to set up the ephemeral keys:
http://www.openssl.org/docs/ssl/SSL_CTX_set_tmp_dh_callback.html
https://tech.immerda.ch/2011/11/the-state-of-forward-secrecy-in-openssl/
Enable elliptic curve ciphers to support forward secrecy
Key: TS-2392
URL: https://issues.apache.org/jira/browse/TS-2392
Project: Traffic Server
Issue Type: Improvement
Components: SSL
Reporter: Jan-Frode Myklebust
ATS does not seem to support the elliptic curve diffie hellman ephemeral key
exchanges (ECDH) that are available in openssl. It seems these needs to be
enabled explicitly to take advantage of them. Ref: the following commit for
how this support was added to apache httpd v2.3.3:
http://mail-archives.apache.org/mod_mbox/httpd-cvs/200911.mbox/%3c20091110075514.166a62388...@eris.apache.org%3E
and for stud:
https://github.com/bumptech/stud/pull/61/files
Maybe both a DH key exchange needs to be set up, and then the various
elliptic curves needs to be initialized..?
Checking the openssl docs, I see SSL_CTX_set_tmp_dh_callback() needs to be
called to set up the ephemeral keys:
http://www.openssl.org/docs/ssl/SSL_CTX_set_tmp_dh_callback.html
https://tech.immerda.ch/2011/11/the-state-of-forward-secrecy-in-openssl/
http://wiki.openssl.org/index.php/Elliptic_Curve_Diffie_Hellman
And these are the named curves available with openssl-1.0.1e-16.el6_5.x86_64
on RHEL-6.5:
{noformat}
$ openssl ecparam -list_curves
secp384r1 : NIST/SECG curve over a 384 bit prime field
prime256v1: X9.62/SECG curve over a 256 bit prime field
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (TS-2357) Add option to cache POST requests
[ https://issues.apache.org/jira/browse/TS-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-2357: - Assignee: Bryan Call Giving to Bryan, since this is hopefully a quick merge of YTS to ATS :). Add option to cache POST requests - Key: TS-2357 URL: https://issues.apache.org/jira/browse/TS-2357 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: Bryan Call Assignee: Bryan Call Fix For: 4.2.0 This feature was added to YTS after it was open sourced. Yahoo bug number: 2831983 This is the configuration option and it might be nice to keep it the same name for those that are migrating from YTS to ATS: CONFIG proxy.config.http.cache.cache_method_post INT 1 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2329) Document header_rewrite's ability to set overridable configurations
[ https://issues.apache.org/jira/browse/TS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2329: -- Fix Version/s: Docs Document header_rewrite's ability to set overridable configurations Key: TS-2329 URL: https://issues.apache.org/jira/browse/TS-2329 Project: Traffic Server Issue Type: Bug Components: Documentation, Plugins Affects Versions: 4.2.0 Reporter: Igor Galić Assignee: Leif Hedstrom Fix For: Docs This plugin contains a README, but we should probably drop that in favour of the reference documentation for the plugin. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2330) Update proxy.config.body_factory.enable_customizations comments in records.config
[
https://issues.apache.org/jira/browse/TS-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2330:
--
Fix Version/s: 4.2.0
Update proxy.config.body_factory.enable_customizations comments in
records.config
-
Key: TS-2330
URL: https://issues.apache.org/jira/browse/TS-2330
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 4.1.0
Reporter: David Carlin
Assignee: Leif Hedstrom
Fix For: 4.2.0
The comments in records.config for
proxy.config.body_factory.enable_customizations don't reflect TS-2217 changes
- remove any mention of option 0.
{noformat}
##
#
# Customizable User Response Pages
#
##
# 0 - turn off customizable user response pages
# 1 - enable customizable user response pages in only the default
directory
# 2 - enable language-targeted user response pages
CONFIG proxy.config.body_factory.enable_customizations INT 1
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2329) Document header_rewrite's ability to set overridable configurations
[ https://issues.apache.org/jira/browse/TS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831096#comment-13831096 ] Leif Hedstrom commented on TS-2329: --- Is anyone from LinkedIn working on these docs btw? Document header_rewrite's ability to set overridable configurations Key: TS-2329 URL: https://issues.apache.org/jira/browse/TS-2329 Project: Traffic Server Issue Type: Bug Components: Documentation, Plugins Affects Versions: 4.2.0 Reporter: Igor Galić Assignee: Leif Hedstrom Fix For: Docs This plugin contains a README, but we should probably drop that in favour of the reference documentation for the plugin. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (TS-2330) Update proxy.config.body_factory.enable_customizations comments in records.config
[
https://issues.apache.org/jira/browse/TS-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-2330:
-
Assignee: Leif Hedstrom
Update proxy.config.body_factory.enable_customizations comments in
records.config
-
Key: TS-2330
URL: https://issues.apache.org/jira/browse/TS-2330
Project: Traffic Server
Issue Type: Bug
Components: Configuration
Affects Versions: 4.1.0
Reporter: David Carlin
Assignee: Leif Hedstrom
Fix For: 4.2.0
The comments in records.config for
proxy.config.body_factory.enable_customizations don't reflect TS-2217 changes
- remove any mention of option 0.
{noformat}
##
#
# Customizable User Response Pages
#
##
# 0 - turn off customizable user response pages
# 1 - enable customizable user response pages in only the default
directory
# 2 - enable language-targeted user response pages
CONFIG proxy.config.body_factory.enable_customizations INT 1
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TS-2347) buffer_upload uses unsafe function tempnam()
[
https://issues.apache.org/jira/browse/TS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2347:
--
Fix Version/s: 4.2.0
buffer_upload uses unsafe function tempnam()
Key: TS-2347
URL: https://issues.apache.org/jira/browse/TS-2347
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Reporter: Igor Galić
Assignee: Kit Chan
Fix For: 4.2.0
{code}
make[3]: Entering directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload'
CXX buffer_upload.lo
CXXLDbuffer_upload.la
.libs/buffer_upload.o: In function `attach_pvc_plugin(tsapi_cont*, TSEvent,
void*)':
/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload/../../../../plugins/experimental/buffer_upload/buffer_upload.cc:915:
warning: the use of `tempnam' is dangerous, better use `mkstemp'
make[3]: Leaving directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload'
Making all in esi
make[3]: Entering directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/esi'
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2329) Document header_rewrite's ability to set overridable configurations
[ https://issues.apache.org/jira/browse/TS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831095#comment-13831095 ] Leif Hedstrom commented on TS-2329: --- We need to document the entire plugin though, there's nothing in the docs right now :/. Document header_rewrite's ability to set overridable configurations Key: TS-2329 URL: https://issues.apache.org/jira/browse/TS-2329 Project: Traffic Server Issue Type: Bug Components: Documentation, Plugins Affects Versions: 4.2.0 Reporter: Igor Galić Assignee: Leif Hedstrom Fix For: Docs This plugin contains a README, but we should probably drop that in favour of the reference documentation for the plugin. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (TS-2318) header_rewrite/header_filter plugin is not likey to parse properly.
[
https://issues.apache.org/jira/browse/TS-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-2318.
---
Resolution: Duplicate
header_rewrite/header_filter plugin is not likey to parse properly.
---
Key: TS-2318
URL: https://issues.apache.org/jira/browse/TS-2318
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Reporter: seri,Kim
header_rewrite/header_filter plugin is not parsing properly.
My header_rewrite config is
cond %\{READ_RESPONSE_HDR_HOOK\}
cond %\{HEADER:Vary\} =Accept-Encoding,User-Agent \[NC\]
set-header Vary Accept-Encoding
header_rewrite plugin is likely to parse
not
Vary: Accept-Encoding,User-Agent
to
Vary: Accept-Encoding
My config is missing something?
Please, help me.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TS-2325) remap.config .include should support directories
[ https://issues.apache.org/jira/browse/TS-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2325: -- Fix Version/s: 4.2.0 remap.config .include should support directories Key: TS-2325 URL: https://issues.apache.org/jira/browse/TS-2325 Project: Traffic Server Issue Type: Improvement Components: Configuration, Core Reporter: James Peach Fix For: 4.2.0 The remap.config .include directive should support including a directory. The implementation for this would be to simply read all the files in the directory and include each one. I don't think the files in the directory should be sorted, since that requires us to read all the names into memory, and there might be a very large number of them. Typical ordering constraints can be expressed using multiple directories. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2358) DNS does not fail-over promptly for DNS server returning SERVFAIL
[ https://issues.apache.org/jira/browse/TS-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831107#comment-13831107 ] William Bardwell commented on TS-2358: -- I am not working on this one for now. DNS does not fail-over promptly for DNS server returning SERVFAIL - Key: TS-2358 URL: https://issues.apache.org/jira/browse/TS-2358 Project: Traffic Server Issue Type: Bug Components: DNS Affects Versions: 3.2.5 Reporter: William Bardwell Attachments: ats.dns.txt If I have 2 dns servers listed in my resolv.conf and the first one is returning SERVFAIL for something that I try to lookup, ATS takes a long time to fail over, and won't do it for the first request to look something up. Using normal system commands (host, ping etc.) with the same resolv.conf work fine. I tried various config values with out much improvement. I could make it fail in 40sec instead of 60sec for the initial failure... debug logs will be attached, doing one DNS and then waiting a while and doing another. (Doing more before enough time has passed don't seem to help much.) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (TS-2034) make test fails with Linux AIO enabled
[
https://issues.apache.org/jira/browse/TS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming reassigned TS-2034:
-
Assignee: weijin
make test fails with Linux AIO enabled
--
Key: TS-2034
URL: https://issues.apache.org/jira/browse/TS-2034
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Leif Hedstrom
Assignee: weijin
Fix For: 5.0.0
With
{code}
test_AIO-test_AIO.o: In function `main':
/home/leif/apache/trafficserver.git/BUILDS/debug/iocore/aio/../../../../iocore/aio/test_AIO.cc:494:
undefined reference to `cache_config_threads_per_disk'
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (TS-980) change client_session schedule from global to thread local, and reduce the try_locks in UnixNetVConnection::reenable
[
https://issues.apache.org/jira/browse/TS-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhao Yongming reassigned TS-980:
Assignee: weijin (was: weijin)
change client_session schedule from global to thread local, and reduce the
try_locks in UnixNetVConnection::reenable
-
Key: TS-980
URL: https://issues.apache.org/jira/browse/TS-980
Project: Traffic Server
Issue Type: Improvement
Components: Network, Performance
Affects Versions: 3.1.0, 3.0.0
Environment: all
Reporter: weijin
Assignee: weijin
Fix For: 5.0.0
Attachments: ts-980.diff
I did some performance test on ats last days(disable cache, set share_server
session 2, pure proxy mode), I did see significant improvement on low load,
but it dropped rapidly when load is high. meanwhile, some stability problems
happened. Through gdb, I found the client_session`s mutex can be acquired by
two or more threads, I believe some schedules happened during the sm
life_time. May be we need do some work to find these eventProcessor.schedules
and change them to thread schedules.
UnixVConnecton::reenable {
if (nh-mutex-thread_holding == t) {
// put into ready_list
} else {
MUTEX_TRY_LOCK(lock, nh-mutex, t);
if (!lock) {
// put into enable_list;
} else {
// put into ready_list;
}
}
remove UnixNetVConnection::reenable try_lock operations, 3 reasons
1. try_lock operation means obj allocation and deallocation operation.
frequently
2. try_lock hardly can lock the net-handler`s mutex.(net-handler is schedule
by as soon as possible)
3. try_lock should not acquire the net-handler`s mutex. That may lead more
net io latency if it is an epoll event need to be processed in other threads.
If it is not an epoll event(time event), I don`t think putting vc in
ready_list has any advantage than in enable_list.
may be we can change reenale function like this:
UnixVConnecton::reenable {
if (nh-mutex-thread_holding == t) {
// put into ready_list;
} else {
// put into enable_list;
}
my buddies, any advice?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (TS-899) ts crash
[ https://issues.apache.org/jira/browse/TS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao Yongming reassigned TS-899: Assignee: weijin (was: weijin) ts crash Key: TS-899 URL: https://issues.apache.org/jira/browse/TS-899 Project: Traffic Server Issue Type: Sub-task Components: HTTP, MIME Affects Versions: 3.0.1 Environment: readhat5.5, ts-3.0.1, X86-64 Reporter: weijin Assignee: weijin Fix For: 5.0.0 If a request url is forbidden then redirected to another url, TS crash. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2372) Add forward security support (SSL related)
[ https://issues.apache.org/jira/browse/TS-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831158#comment-13831158 ] James Peach commented on TS-2372: - http://en.wikibooks.org/wiki/OpenSSL/Diffie-Hellman_parameters Add forward security support (SSL related) -- Key: TS-2372 URL: https://issues.apache.org/jira/browse/TS-2372 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: Bryan Call Labels: ssl Fix For: 4.2.0 mod_ssl bug and changes: https://issues.apache.org/bugzilla/show_bug.cgi?id=49559 Discussion on httpd-dev list: http://mail-archives.apache.org/mod_mbox/httpd-dev/201309.mbox/%3c52358ed1.2070...@velox.ch%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2372) Add forward security support (SSL related)
[ https://issues.apache.org/jira/browse/TS-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831159#comment-13831159 ] James Peach commented on TS-2372: - OK, looks like there's 2 things we need to do here: 1. Set support for setting Diffie-Hellman parameters on the SSL context 2. Set up the ECDH support. Add forward security support (SSL related) -- Key: TS-2372 URL: https://issues.apache.org/jira/browse/TS-2372 Project: Traffic Server Issue Type: Improvement Components: HTTP Reporter: Bryan Call Labels: ssl Fix For: 4.2.0 mod_ssl bug and changes: https://issues.apache.org/bugzilla/show_bug.cgi?id=49559 Discussion on httpd-dev list: http://mail-archives.apache.org/mod_mbox/httpd-dev/201309.mbox/%3c52358ed1.2070...@velox.ch%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2384) Regression in key-lookup code between 4.0.x and 4.1.x
[
https://issues.apache.org/jira/browse/TS-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831231#comment-13831231
]
Igor Galić commented on TS-2384:
[~vlad.bach], do you think you could test the 4.1.x branch for us before we
attempt another release?
Regression in key-lookup code between 4.0.x and 4.1.x
-
Key: TS-2384
URL: https://issues.apache.org/jira/browse/TS-2384
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: Igor Galić
Fix For: 4.2.0
As reported on users@
{noformat}
ATS 4.0.1
Volume #1 - store='/dev/sda'
first key 409542BD429764BEE60B0610B8924C4D
key 6BA7E5696E9A9E7A1E05212E5264D3C4
sync_serial 10836
write_serial388912
header length 2480
fragment type 1
No of Alternates1
{noformat}
{noformat}
ATS 4.1.1
Volume #1 - store='/dev/sda'
first key 409542BD429764BEE60B0610B8924C4D
key 34CEA58AC5FBA6D240C484307DE4C315
sync_serial 10837
write_serial388912
header length 2480
fragment type 1
No of Alternates1
{noformat}
When run 4.1.1 all previously cached objects under 4.0.1 are MISS, these
objects downloading from parent, and then they HIT again.
*Note* This does not cause the cache to be reinitialized.
It's just that the generated cache-lookup *key* is wrong in 4.1.x. This means
that the existing objects on the disks will stay in place, but we won't be
able to find them, because we are looking in the wrong place. As such we
simply store the object again.
That's *almost* the same for people running with a 60 TiB cache, because
everything requested is also stored again,
and after a while the old objects that have been lying around for a while
will be rotated out so that's bad. People with
tiny caches or very high turn overs might even notice the downward spike in
304s.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2329) Document header_rewrite's ability to set overridable configurations
[
https://issues.apache.org/jira/browse/TS-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831235#comment-13831235
]
Igor Galić commented on TS-2329:
What we can do now is,
{code}
% git mv plugins/header_rewrite/README
doc/reference/plugins/header_rewrite.en.rst
{code}
Document header_rewrite's ability to set overridable configurations
Key: TS-2329
URL: https://issues.apache.org/jira/browse/TS-2329
Project: Traffic Server
Issue Type: Bug
Components: Documentation, Plugins
Affects Versions: 4.2.0
Reporter: Igor Galić
Assignee: Leif Hedstrom
Fix For: Docs
This plugin contains a README, but we should probably drop that in favour of
the reference documentation for the plugin.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2384) Regression in key-lookup code between 4.0.x and 4.1.x
[
https://issues.apache.org/jira/browse/TS-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831241#comment-13831241
]
Vladyslav Bachynskyi commented on TS-2384:
--
Sure!
Regression in key-lookup code between 4.0.x and 4.1.x
-
Key: TS-2384
URL: https://issues.apache.org/jira/browse/TS-2384
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: Igor Galić
Fix For: 4.2.0
As reported on users@
{noformat}
ATS 4.0.1
Volume #1 - store='/dev/sda'
first key 409542BD429764BEE60B0610B8924C4D
key 6BA7E5696E9A9E7A1E05212E5264D3C4
sync_serial 10836
write_serial388912
header length 2480
fragment type 1
No of Alternates1
{noformat}
{noformat}
ATS 4.1.1
Volume #1 - store='/dev/sda'
first key 409542BD429764BEE60B0610B8924C4D
key 34CEA58AC5FBA6D240C484307DE4C315
sync_serial 10837
write_serial388912
header length 2480
fragment type 1
No of Alternates1
{noformat}
When run 4.1.1 all previously cached objects under 4.0.1 are MISS, these
objects downloading from parent, and then they HIT again.
*Note* This does not cause the cache to be reinitialized.
It's just that the generated cache-lookup *key* is wrong in 4.1.x. This means
that the existing objects on the disks will stay in place, but we won't be
able to find them, because we are looking in the wrong place. As such we
simply store the object again.
That's *almost* the same for people running with a 60 TiB cache, because
everything requested is also stored again,
and after a while the old objects that have been lying around for a while
will be rotated out so that's bad. People with
tiny caches or very high turn overs might even notice the downward spike in
304s.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
