[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[
https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885900#comment-13885900
]
Scott Harris commented on TS-2138:
--
have tested again with patch from weijin and issue is fixed.
Using linux native-AIO, restarting ATS causes complete cache data loss
--
Key: TS-2138
URL: https://issues.apache.org/jira/browse/TS-2138
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: bettydramit
Assignee: weijin
Fix For: 4.2.0
Attachments: TS-2138.wj.diff, ts-3.3.5-40.spec
ENV: centos 6 x86_64 gitmaster and
http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver
--enable-linux-native-aio --enable-reclaimable-freelist
when restart ats ,my all hit data will be lost.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[
https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836129#comment-13836129
]
Scott Harris commented on TS-2138:
--
Have just tested and bug is not fixed.
Compiled with --enable-linux-native-aio after restart
proxy.process.cache.bytes_used drops down to 0 and grows as cache is used.
Using linux native-AIO, restarting ATS causes complete cache data loss
--
Key: TS-2138
URL: https://issues.apache.org/jira/browse/TS-2138
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: bettydramit
Assignee: weijin
Fix For: 4.1.1
Attachments: TS-2138.wj.diff, ts-3.3.5-40.spec
ENV: centos 6 x86_64 gitmaster and
http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver
--enable-linux-native-aio --enable-reclaimable-freelist
when restart ats ,my all hit data will be lost.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[
https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13836134#comment-13836134
]
Scott Harris commented on TS-2138:
--
Tested also with 4.1.1 with aio not enabed and after restart
proxy.process.cache.bytes_used returns to same value as before restart (ie
proxy.process.cache.bytes_used=190189568). So the --enable-linux-native-aio is
still causing cache data loss.
Using linux native-AIO, restarting ATS causes complete cache data loss
--
Key: TS-2138
URL: https://issues.apache.org/jira/browse/TS-2138
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: bettydramit
Assignee: weijin
Fix For: 4.1.1
Attachments: TS-2138.wj.diff, ts-3.3.5-40.spec
ENV: centos 6 x86_64 gitmaster and
http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver
--enable-linux-native-aio --enable-reclaimable-freelist
when restart ats ,my all hit data will be lost.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2333) regression in proxy.node.* stats
[
https://issues.apache.org/jira/browse/TS-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818550#comment-13818550
]
Scott Harris commented on TS-2333:
--
I can reproduce and I'm linking with libhwloc.
Let me know what you need?
regression in proxy.node.* stats
Key: TS-2333
URL: https://issues.apache.org/jira/browse/TS-2333
Project: Traffic Server
Issue Type: Bug
Components: Stats
Affects Versions: 4.1.0
Reporter: Igor Galić
after upgrade from 4.0.2 to 4.1.0 users report that many {{proxy.node.*}}
stats are broken, and mostly return 0.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2333) regression in proxy.node.* stats
[
https://issues.apache.org/jira/browse/TS-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818646#comment-13818646
]
Scott Harris commented on TS-2333:
--
can confirm compiling with —with-xml=expat (as suggested by leif) fixes the
problem.
regression in proxy.node.* stats
Key: TS-2333
URL: https://issues.apache.org/jira/browse/TS-2333
Project: Traffic Server
Issue Type: Bug
Components: Stats
Affects Versions: 4.1.0
Reporter: Igor Galić
after upgrade from 4.0.2 to 4.1.0 users report that many {{proxy.node.*}}
stats are broken, and mostly return 0.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[
https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795722#comment-13795722
]
Scott Harris commented on TS-2138:
--
Have tested with 4.0.2 and see the same result with aio enabled
[Oct 16 09:06:19.588] Server {0x7f12e09407e0} NOTE: Clearing Cache
[Oct 16 09:06:19.598] Server {0x7f12df992700} NOTE: Clearing Disk: /dev/sdd
[Oct 16 09:06:19.598] Server {0x7f12df992700} NOTE: Clearing Disk: /dev/sdd
[Oct 16 09:06:19.604] Server {0x7f12df992700} NOTE: clearing cache directory
'/dev/sdd 16384:5242878'
[Oct 16 09:06:19.606] Server {0x7f12dfa93700} NOTE: clearing cache directory
'/dev/sdd 16384:5242878'
Using linux native-AIO, restarting ATS causes complete cache data loss
--
Key: TS-2138
URL: https://issues.apache.org/jira/browse/TS-2138
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: bettydramit
Assignee: weijin
Fix For: sometime
Attachments: ts-3.3.5-40.spec
ENV: centos 6 x86_64 gitmaster and
http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver
--enable-linux-native-aio --enable-reclaimable-freelist
when restart ats ,my all hit data will be lost.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[
https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794508#comment-13794508
]
Scott Harris commented on TS-2138:
--
I have the same issue with loss of cache data on restart but also noticed when
doing a traffic_server -C clear with native-aio enabled and 4 raw disks in
storage.config my logs show :
[Oct 14 15:02:08.272] Server {0x7f3ce27fb7e0} NOTE: Clearing Cache
[Oct 14 15:02:08.311] Server {0x7f3cdea1f700} NOTE: Clearing Disk: /dev/sde
[Oct 14 15:02:08.311] Server {0x7f3cdea1f700} NOTE: Clearing Disk: /dev/sde
[Oct 14 15:02:08.311] Server {0x7f3cdea1f700} NOTE: Clearing Disk: /dev/sde
[Oct 14 15:02:08.311] Server {0x7f3cdea1f700} NOTE: Clearing Disk: /dev/sde
[Oct 14 15:02:08.324] Server {0x7f3cde71c700} NOTE: clearing cache directory
'/dev/sde 81920:48706038'
[Oct 14 15:02:08.327] Server {0x7f3cde61b700} NOTE: clearing cache directory
'/dev/sde 81920:48706038'
[Oct 14 15:02:08.340] Server {0x7f3cde51a700} NOTE: clearing cache directory
'/dev/sde 81920:48706038'
[Oct 14 15:02:08.345] Server {0x7f3cde419700} NOTE: clearing cache directory
'/dev/sde 81920:48706038'
with native-aio disabled I get
[Oct 15 08:22:29.652] Server {0x7f3b0cc207e0} NOTE: Clearing Cache
[Oct 15 08:22:29.696] Server {0x7f3b0cc207e0} NOTE: Clearing Disk: /dev/sdb
[Oct 15 08:22:29.696] Server {0x7f3b0cc207e0} NOTE: Clearing Disk: /dev/sdc
[Oct 15 08:22:29.696] Server {0x7f3b0cc207e0} NOTE: Clearing Disk: /dev/sdd
[Oct 15 08:22:29.696] Server {0x7f3b0cc207e0} NOTE: Clearing Disk: /dev/sde
[Oct 15 08:22:29.700] Server {0x7f3b0cc207e0} NOTE: clearing cache directory
'/dev/sdb 81920:48706038'
[Oct 15 08:22:30.273] Server {0x7f3b0cc207e0} NOTE: clearing cache directory
'/dev/sdc 81920:48706038'
[Oct 15 08:22:30.855] Server {0x7f3b0cc207e0} NOTE: clearing cache directory
'/dev/sdd 81920:48706038'
[Oct 15 08:22:31.434] Server {0x7f3b0cc207e0} NOTE: clearing cache directory
'/dev/sde 81920:48706038'
my storage.config contains
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
Using linux native-AIO, restarting ATS causes complete cache data loss
--
Key: TS-2138
URL: https://issues.apache.org/jira/browse/TS-2138
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: bettydramit
Assignee: weijin
Fix For: sometime
Attachments: ts-3.3.5-40.spec
ENV: centos 6 x86_64 gitmaster and
http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2
./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver
--enable-linux-native-aio --enable-reclaimable-freelist
when restart ats ,my all hit data will be lost.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2188) healthcheck plugin seg faulting
[ https://issues.apache.org/jira/browse/TS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762596#comment-13762596 ] Scott Harris commented on TS-2188: -- applied patches on version 4.0.1 and all tested ok. Thanks again. healthcheck plugin seg faulting --- Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 4.1.0 When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2188) healthcheck plugin seg faulting
Scott Harris created TS-2188: Summary: healthcheck plugin seg faulting Key: TS-2188 URL: https://issues.apache.org/jira/browse/TS-2188 Project: Traffic Server Issue Type: Bug Components: Plugins Reporter: Scott Harris When using the experimental healthcheck plugin any request received with a uri of / or null results in a seg fault. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2189) enabling proxy.config.http.cache.cluster_cache_local causes all traffic to store local
Scott Harris created TS-2189: Summary: enabling proxy.config.http.cache.cluster_cache_local causes all traffic to store local Key: TS-2189 URL: https://issues.apache.org/jira/browse/TS-2189 Project: Traffic Server Issue Type: Bug Components: Cache, Clustering Reporter: Scott Harris Setting proxy.config.http.cache.cluster_cache_local=1 is causing all requests to cache locally and not work in cluster mode. cache.config contains no rules so nothing should be caching locally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2184) Fetch from cluster with proxy.config.http.cache.cluster_cache_local enabled
Scott Harris created TS-2184: Summary: Fetch from cluster with proxy.config.http.cache.cluster_cache_local enabled Key: TS-2184 URL: https://issues.apache.org/jira/browse/TS-2184 Project: Traffic Server Issue Type: Improvement Components: Cache, Clustering Reporter: Scott Harris With proxy.config.http.cache.cluster_cache_local enabled I would like cluster nodes to store content locally but try to retrieve content from the cluster first (if not cached locally) and if no cluster nodes have content cached then retrieve from origin. Example - 2 Cluster nodes in Full cluster mode. 1. Node1 and Node2 are both empty. 2. Request to Node1 for http://www.example.com/foo.html;. 3. Query Cluster for object 4. Not cached in cluster so retrieve from orgin, serve to client, object now cached on Node1. 5. Request comes to Node2 for http://www.example.com/foo.html;. 6. Node2 retrieves cached version from Node1, serves to client, stores locally. 7. Subsequent request comes to Node1 or Node2 for http://www.example.com/foo.html;, object is served to client from local cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2173) cache total hit/miss stats broken in version 4.0.1
[ https://issues.apache.org/jira/browse/TS-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Harris updated TS-2173: - Affects Version/s: 4.0.1 cache total hit/miss stats broken in version 4.0.1 -- Key: TS-2173 URL: https://issues.apache.org/jira/browse/TS-2173 Project: Traffic Server Issue Type: Bug Components: Stats Affects Versions: 4.0.1 Reporter: Scott Harris Fix For: 4.1.0 In version 4.0.1 both proxy.node.cache_total_hits and proxy.node.cache_total_misses always return 0 In version 3.2.5 both stats returned correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-2173) cache total hit/miss stats broken in version 4.0.1
Scott Harris created TS-2173: Summary: cache total hit/miss stats broken in version 4.0.1 Key: TS-2173 URL: https://issues.apache.org/jira/browse/TS-2173 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Scott Harris In version 4.0.1 both proxy.node.cache_total_hits and proxy.node.cache_total_misses always return 0 In version 3.2.5 both stats returned correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614881#comment-13614881 ] Scott Harris commented on TS-1767: -- Understand, thanks. Scott Cache Lookup Regex using incorrect urls --- Key: TS-1767 URL: https://issues.apache.org/jira/browse/TS-1767 Project: Traffic Server Issue Type: Bug Components: Web UI Reporter: Scott Harris Assignee: Leif Hedstrom Fix For: 3.3.3 When using the cache regex lookup returned urls contain origin server not of incoming mapping to ats. Ie using map http://incoming http://10.1.1.1:8080 returned regex urls are : http://10.1.1.1:8080/blah instead of http://incoming/blah Selecting any of these results in Cache Lookup Failed, or missing in cluster Doing url lookup with incoming url returns valid result. Using version 3.2.4 running as a reverse proxy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13609521#comment-13609521 ] Scott Harris commented on TS-1767: -- thanks for the suggestion, which works, but I have some sites that require the original host header to be passed through. Cache Lookup Regex using incorrect urls --- Key: TS-1767 URL: https://issues.apache.org/jira/browse/TS-1767 Project: Traffic Server Issue Type: Bug Components: Web UI Reporter: Scott Harris When using the cache regex lookup returned urls contain origin server not of incoming mapping to ats. Ie using map http://incoming http://10.1.1.1:8080 returned regex urls are : http://10.1.1.1:8080/blah instead of http://incoming/blah Selecting any of these results in Cache Lookup Failed, or missing in cluster Doing url lookup with incoming url returns valid result. Using version 3.2.4 running as a reverse proxy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1767) Cache Lookup Regex using incorrect urls
[ https://issues.apache.org/jira/browse/TS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Harris updated TS-1767: - Description: When using the cache regex lookup returned urls contain origin server not of incoming mapping to ats. Ie using map http://incoming http://10.1.1.1:8080 returned regex urls are : http://10.1.1.1:8080/blah instead of http://incoming/blah Selecting any of these results in Cache Lookup Failed, or missing in cluster Doing url lookup with incoming url returns valid result. Using version 3.2.4 running as a reverse proxy was: When using the cache regex lookup returned urls contain origin server not of incoming mapping to ats. Ie using map http://incoming http://10.1.1.1:8080 returned regex urls are : http://10.1.1.1:8080/blah instead of http://incoming/blah Selecting any of these results in Cache Lookup Failed, or missing in cluster Doing url lookup with incoming url returns valid result. Using version 3.2.4 Cache Lookup Regex using incorrect urls --- Key: TS-1767 URL: https://issues.apache.org/jira/browse/TS-1767 Project: Traffic Server Issue Type: Bug Components: Web UI Reporter: Scott Harris When using the cache regex lookup returned urls contain origin server not of incoming mapping to ats. Ie using map http://incoming http://10.1.1.1:8080 returned regex urls are : http://10.1.1.1:8080/blah instead of http://incoming/blah Selecting any of these results in Cache Lookup Failed, or missing in cluster Doing url lookup with incoming url returns valid result. Using version 3.2.4 running as a reverse proxy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
