[jira] [Commented] (TS-745) Support ssd
[ https://issues.apache.org/jira/browse/TS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031254#comment-13031254 ] John Plevyak commented on TS-745: - We should make a branch for this. Then we could collaborate. I would also like to simplify locking in the cache by getting rid of the TryLocks for the partition. This would make it easier to write the SSD code to handle multiple SSDs I think. What do you think mohan_zl? Support ssd --- Key: TS-745 URL: https://issues.apache.org/jira/browse/TS-745 Project: Traffic Server Issue Type: New Feature Components: Cache Reporter: mohan_zl Assignee: mohan_zl Attachments: ssd_cache.patch A patch for supporting, not work well for a long time with --enable-debug -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-769) traffic server loops forever if the origin sends back a 505 and the connection is keep-alive
traffic server loops forever if the origin sends back a 505 and the connection is keep-alive Key: TS-769 URL: https://issues.apache.org/jira/browse/TS-769 Project: Traffic Server Issue Type: Bug Components: HTTP Affects Versions: 2.1.8 Environment: This was observed in the Yahoo! version of traffic server Reporter: Bryan Call Assignee: Bryan Call Fix For: 2.1.9 Traffic server tries to downgrade the connection/protocol when it gets back a 505 from the origin server. First it removes keep-alive and retries, then traffic sever start to downgrade the http protocol version and retry. However, another part of the code turns keep-alive back on and traffic server will loop turning on and off keep-alive and making the same request to the origin server. I fixed the issue in the Yahoo! tree by alway downgrade keep-alive and protocol version together. This will eventually stop after it has tried HTTP/0.9. Also, I added an option to not downgrade and retry at all when getting a 505. I have to verify that this is also an issue with the Apache tree. I looked over the code and it doesn't look like it changed at all from the Yahoo! tree, so the bug should also be there. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-770) proxy.config.http.doc_in_cache_skip_dns is not being read from records.config
proxy.config.http.doc_in_cache_skip_dns is not being read from records.config - Key: TS-770 URL: https://issues.apache.org/jira/browse/TS-770 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 2.1.6, 2.1.7, 2.1.8 Reporter: Yakov Markovitch Priority: Minor The value of new configuration option proxy.config.http.doc_in_cache_skip_dns is not read from records.config on TS start. This is rather unfortunate, since its default value is 1 and our plugin needs DNS on every transaction, even if the document is served from the cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-770) proxy.config.http.doc_in_cache_skip_dns is not being read from records.config
[ https://issues.apache.org/jira/browse/TS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Markovitch updated TS-770: Attachment: trafficserver.2.1.8.doc_in_cache_skip_dns.patch Patch that enables reading proxy.config.http.doc_in_cache_skip_dns value from recorda.config at TS start. proxy.config.http.doc_in_cache_skip_dns is not being read from records.config - Key: TS-770 URL: https://issues.apache.org/jira/browse/TS-770 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 2.1.8, 2.1.7, 2.1.6 Reporter: Yakov Markovitch Priority: Minor Attachments: trafficserver.2.1.8.doc_in_cache_skip_dns.patch The value of new configuration option proxy.config.http.doc_in_cache_skip_dns is not read from records.config on TS start. This is rather unfortunate, since its default value is 1 and our plugin needs DNS on every transaction, even if the document is served from the cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-770) proxy.config.http.doc_in_cache_skip_dns is not being read from records.config
[ https://issues.apache.org/jira/browse/TS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-770: Assignee: Leif Hedstrom proxy.config.http.doc_in_cache_skip_dns is not being read from records.config - Key: TS-770 URL: https://issues.apache.org/jira/browse/TS-770 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 2.1.8, 2.1.7, 2.1.6 Reporter: Yakov Markovitch Assignee: Leif Hedstrom Priority: Minor Attachments: trafficserver.2.1.8.doc_in_cache_skip_dns.patch The value of new configuration option proxy.config.http.doc_in_cache_skip_dns is not read from records.config on TS start. This is rather unfortunate, since its default value is 1 and our plugin needs DNS on every transaction, even if the document is served from the cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-770) proxy.config.http.doc_in_cache_skip_dns is not being read from records.config
[ https://issues.apache.org/jira/browse/TS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031309#comment-13031309 ] Leif Hedstrom commented on TS-770: -- Cool, thanks for the patch. While we are at it, should this configuration be a candidate to be configurable via the plugin APIs? (that's the oride struct in the config). That would allow you to turn this on and off from a plugin, or using the standard remap plugin, per remap rule. proxy.config.http.doc_in_cache_skip_dns is not being read from records.config - Key: TS-770 URL: https://issues.apache.org/jira/browse/TS-770 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 2.1.8, 2.1.7, 2.1.6 Reporter: Yakov Markovitch Assignee: Leif Hedstrom Priority: Minor Attachments: trafficserver.2.1.8.doc_in_cache_skip_dns.patch The value of new configuration option proxy.config.http.doc_in_cache_skip_dns is not read from records.config on TS start. This is rather unfortunate, since its default value is 1 and our plugin needs DNS on every transaction, even if the document is served from the cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-770) proxy.config.http.doc_in_cache_skip_dns is not being read from records.config
[ https://issues.apache.org/jira/browse/TS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-770: - Fix Version/s: 2.1.9 proxy.config.http.doc_in_cache_skip_dns is not being read from records.config - Key: TS-770 URL: https://issues.apache.org/jira/browse/TS-770 Project: Traffic Server Issue Type: Bug Components: Configuration Affects Versions: 2.1.8, 2.1.7, 2.1.6 Reporter: Yakov Markovitch Assignee: Leif Hedstrom Priority: Minor Fix For: 2.1.9 Attachments: trafficserver.2.1.8.doc_in_cache_skip_dns.patch The value of new configuration option proxy.config.http.doc_in_cache_skip_dns is not read from records.config on TS start. This is rather unfortunate, since its default value is 1 and our plugin needs DNS on every transaction, even if the document is served from the cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-738) 'make check` fails on x86
[
https://issues.apache.org/jira/browse/TS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-738.
--
Resolution: Fixed
Closing this, since John fixed it (thanks!)
'make check` fails on x86
-
Key: TS-738
URL: https://issues.apache.org/jira/browse/TS-738
Project: Traffic Server
Issue Type: Bug
Components: Build
Affects Versions: 2.1.7
Environment: ATS 2.1.7 on x86, gcc 4.5.2
Reporter: Arno Toell
Assignee: John Plevyak
Priority: Minor
Fix For: 2.1.9
The `make check' target of the Makefile fails to build on x86, AMD64 is fine.
Output is (stripped to relevant parts only):
{code}
root@build:/home/arno/build-area/trafficserver-2.1.7-unstable# make check
Making check in proxy/api/ts
...
Create thread 59
Create thread 60
Create thread 61
Create thread 62
Create thread 63
0x08724a60 0x08724a60 0x08724a60
FAIL: test_freelist
PASS: test_arena
test_List PASSED
PASS: test_List
=
1 of 4 tests failed
Please report to d...@trafficserver.apache.org
=
{code}
or
{code}
/bin/bash: line 5: 29956 Segmentation fault ${dir}$tst
FAIL: test_freelist
{code}
or it even succeeds. This might be a race condition therefore. A backtrace
from a core dump of a crashed {{LD_PRELOAD=./.libs/libtsutil.so.2
./.libs/test_freelist}} run shows:
{code}
Core was generated by `./.libs/test_freelist'.
Program terminated with signal 11, Segmentation fault.
#0 ink_freelist_new (f=0x94ff018) at ink_queue.cc:322
322 SET_FREELIST_POINTER_VERSION(next,
*ADDRESS_OF_NEXT(TO_PTR(FREELIST_POINTER(item)), f-offset),
(gdb) bt
#0 ink_freelist_new (f=0x94ff018) at ink_queue.cc:322
#1 0x08048996 in test (d=0x1f) at test_freelist.cc:50
#2 0xf772f7b0 in start_thread () from /lib/libpthread.so.0
#3 0xf74688fe in clone () from /lib/libc.so.6
{code}
I'm not familiar with ATS' data structures, but gdb indicates the following
values:
{code}
$2 = {s = {pointer = 0x1f1f1f1f, version = 165962584}, data =
712803871161786143}
(gdb) print f
$3 = (InkFreeList *) 0x94ff018
(gdb) print f-offset
$4 = 0
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-738) 'make check` fails on x86
[
https://issues.apache.org/jira/browse/TS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-738:
Assignee: John Plevyak
'make check` fails on x86
-
Key: TS-738
URL: https://issues.apache.org/jira/browse/TS-738
Project: Traffic Server
Issue Type: Bug
Components: Build
Affects Versions: 2.1.7
Environment: ATS 2.1.7 on x86, gcc 4.5.2
Reporter: Arno Toell
Assignee: John Plevyak
Priority: Minor
Fix For: 2.1.9
The `make check' target of the Makefile fails to build on x86, AMD64 is fine.
Output is (stripped to relevant parts only):
{code}
root@build:/home/arno/build-area/trafficserver-2.1.7-unstable# make check
Making check in proxy/api/ts
...
Create thread 59
Create thread 60
Create thread 61
Create thread 62
Create thread 63
0x08724a60 0x08724a60 0x08724a60
FAIL: test_freelist
PASS: test_arena
test_List PASSED
PASS: test_List
=
1 of 4 tests failed
Please report to d...@trafficserver.apache.org
=
{code}
or
{code}
/bin/bash: line 5: 29956 Segmentation fault ${dir}$tst
FAIL: test_freelist
{code}
or it even succeeds. This might be a race condition therefore. A backtrace
from a core dump of a crashed {{LD_PRELOAD=./.libs/libtsutil.so.2
./.libs/test_freelist}} run shows:
{code}
Core was generated by `./.libs/test_freelist'.
Program terminated with signal 11, Segmentation fault.
#0 ink_freelist_new (f=0x94ff018) at ink_queue.cc:322
322 SET_FREELIST_POINTER_VERSION(next,
*ADDRESS_OF_NEXT(TO_PTR(FREELIST_POINTER(item)), f-offset),
(gdb) bt
#0 ink_freelist_new (f=0x94ff018) at ink_queue.cc:322
#1 0x08048996 in test (d=0x1f) at test_freelist.cc:50
#2 0xf772f7b0 in start_thread () from /lib/libpthread.so.0
#3 0xf74688fe in clone () from /lib/libc.so.6
{code}
I'm not familiar with ATS' data structures, but gdb indicates the following
values:
{code}
$2 = {s = {pointer = 0x1f1f1f1f, version = 165962584}, data =
712803871161786143}
(gdb) print f
$3 = (InkFreeList *) 0x94ff018
(gdb) print f-offset
$4 = 0
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-771) Remove last V1 log buffer support
Remove last V1 log buffer support - Key: TS-771 URL: https://issues.apache.org/jira/browse/TS-771 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.9 We don't need to support reading V1 logs, so we should remove the remaining V1 logging code for less confusion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-771) Remove last V1 log buffer support
[ https://issues.apache.org/jira/browse/TS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-771. -- Resolution: Fixed Remove last V1 log buffer support - Key: TS-771 URL: https://issues.apache.org/jira/browse/TS-771 Project: Traffic Server Issue Type: Improvement Components: Logging Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.9 We don't need to support reading V1 logs, so we should remove the remaining V1 logging code for less confusion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-772) Make proxy.config.http.doc_in_cache_skip_dns overridable
[ https://issues.apache.org/jira/browse/TS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-772. -- Resolution: Fixed Make proxy.config.http.doc_in_cache_skip_dns overridable Key: TS-772 URL: https://issues.apache.org/jira/browse/TS-772 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.9 Make this overridable per remap rule / plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-772) Make proxy.config.http.doc_in_cache_skip_dns overridable
Make proxy.config.http.doc_in_cache_skip_dns overridable Key: TS-772 URL: https://issues.apache.org/jira/browse/TS-772 Project: Traffic Server Issue Type: Improvement Components: Configuration Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.9 Make this overridable per remap rule / plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-773) Traffic server has a hard limit of 512 gigabytes per RAW disk partition
Traffic server has a hard limit of 512 gigabytes per RAW disk partition --- Key: TS-773 URL: https://issues.apache.org/jira/browse/TS-773 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 2.1.8 Environment: Debian Lenny 5.0.8 2.6.34.7 x86_64 12 1.5TB harddrives for cache disks. Reporter: David Robinson Using 1.5TB harddrives as cache disks results in ATS only using 512GBs of the disk. The disks are configured in RAW mode with no partition information. storage.config is setup like this, /dev/sda /dev/sdb /dev/sde /dev/sdf /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo fdisk -l /dev/sdo Disk /dev/sdo: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Partitioning a disk into 3 512G partition and adding then to storage.config will make ATS use the entire 1.5TBs of space. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-773) Traffic server has a hard limit of 512 gigabytes per RAW disk partition
[ https://issues.apache.org/jira/browse/TS-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031478#comment-13031478 ] David Robinson commented on TS-773: --- Debug log of all 12 disks http://pastebin.com/S343UjCV Traffic server has a hard limit of 512 gigabytes per RAW disk partition --- Key: TS-773 URL: https://issues.apache.org/jira/browse/TS-773 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 2.1.8 Environment: Debian Lenny 5.0.8 2.6.34.7 x86_64 12 1.5TB harddrives for cache disks. Reporter: David Robinson Using 1.5TB harddrives as cache disks results in ATS only using 512GBs of the disk. The disks are configured in RAW mode with no partition information. storage.config is setup like this, /dev/sda /dev/sdb /dev/sde /dev/sdf /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo fdisk -l /dev/sdo Disk /dev/sdo: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Partitioning a disk into 3 512G partition and adding then to storage.config will make ATS use the entire 1.5TBs of space. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-773) Traffic server has a hard limit of 512 gigabytes per RAW disk partition
[ https://issues.apache.org/jira/browse/TS-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-773: - Fix Version/s: 2.1.9 Assignee: John Plevyak Traffic server has a hard limit of 512 gigabytes per RAW disk partition --- Key: TS-773 URL: https://issues.apache.org/jira/browse/TS-773 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 2.1.8 Environment: Debian Lenny 5.0.8 2.6.34.7 x86_64 12 1.5TB harddrives for cache disks. Reporter: David Robinson Assignee: John Plevyak Fix For: 2.1.9 Using 1.5TB harddrives as cache disks results in ATS only using 512GBs of the disk. The disks are configured in RAW mode with no partition information. storage.config is setup like this, /dev/sda /dev/sdb /dev/sde /dev/sdf /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm /dev/sdn /dev/sdo fdisk -l /dev/sdo Disk /dev/sdo: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Partitioning a disk into 3 512G partition and adding then to storage.config will make ATS use the entire 1.5TBs of space. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
