[jira] [Commented] (TS-2264) The current cache connection counter is not reliably decremented with use_client_source_port
[ https://issues.apache.org/jira/browse/TS-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787508#comment-13787508 ] Mohamad Khateeb commented on TS-2264: - Alan, I think I have a solution for this bug , when we get the "EADDRNOTAVAIL failure" , the client connection is terminated so we should also close the cache connection , simply by adding this line " cache_sm.end_both(); " . > The current cache connection counter is not reliably decremented with > use_client_source_port > > > Key: TS-2264 > URL: https://issues.apache.org/jira/browse/TS-2264 > Project: Traffic Server > Issue Type: Bug > Components: TProxy >Reporter: Alan M. Carroll >Assignee: Alan M. Carroll >Priority: Minor > > If use_client_target_addr and use_client_source_port are enabled with > transparent proxy, in some cases the current cache connection counter is not > decremented. This happens when a client connection is terminated due to an > EADDRNOTAVAIL failure. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2262) range request for cached content with small size(around 2k bytes) fails.
[
https://issues.apache.org/jira/browse/TS-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787452#comment-13787452
]
jaekyung oh commented on TS-2262:
-
i tried same test with ats 4.0.1 and it works fine.
now i can see we'd better move to ats 4.0.1 from ats 3.2.4.
The problem is...
1. we(especially op team) are not familiar with ats 4.0.1 because some
configuration styles were changed and they are confused. so op team don't feel
safe to move to ats 4.0.1 until they get familiar with it.
2. we should fix it on ats 3.2.4 right now because one of our customer is
complaing about it.
Could i get simple patch for that? Is there only one way(moving to ats 4.0.1)
to fix our urgent problem?
thank you Leif.
> range request for cached content with small size(around 2k bytes) fails.
>
>
> Key: TS-2262
> URL: https://issues.apache.org/jira/browse/TS-2262
> Project: Traffic Server
> Issue Type: Bug
>Reporter: jaekyung oh
>
> after cache a content with 2k bytes size, range request for it fails showing
> timeout.
> Version : ATS 3.2.4
> curl -v -o /dev/null --range 100-200 "http://ats-test.test.net/1-test.2k";
> shows
> * About to connect() to ats-test.test.net port 80 (#0)
> * Trying 110.45.197.30... % Total% Received % Xferd Average Speed
> TimeTime Time Current
> Dload Upload Total SpentLeft Speed
> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
> 0connected
> * Connected to ats-test.test.net (xxx.xxx.xxx.xxx) port 80 (#0)
> > GET ats-test.test.net/1-test.2k HTTP/1.1
> > Range: bytes=100-200
> > User-Agent: curl/7.20.1 (x86_64-unknown-linux-gnu) libcurl/7.20.1
> > OpenSSL/1.0.0 zlib/1.2.5 libidn/1.15 libssh2/1.2.2_DEV
> > Host: ats-test.test.net
> > Accept: */*
> >
> < HTTP/1.1 206 Partial Content
> < Accept-Ranges: bytes
> < ETag: "2429143783"
> < Last-Modified: Mon, 22 Apr 2013 07:46:30 GMT
> < Date: Tue, 01 Oct 2013 09:15:00 GMT
> < Server: ATS/3.2.4.3.0
> < Content-Type: multipart/byteranges; boundary=RANGE_SEPARATOR
> < Content-Length: 1000
> < Age: 172
> < Connection: keep-alive
> <
> { [data not shown]
> 0 10000 10 0 0 0 --:--:-- 0:00:30 --:--:--
> 0* transfer closed with 999 bytes remaining to read
> 0 10000 10 0 0 0 --:--:-- 0:00:30 --:--:--
> 0* Closing connection #0
> curl: (18) transfer closed with 999 bytes remaining to read
> is there any limit on the size of contents for range request processing?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2257) Healthcheck plugin can stop watching for inotify events
[ https://issues.apache.org/jira/browse/TS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787266#comment-13787266 ] ASF subversion and git services commented on TS-2257: - Commit 196cd66f1e35b5cfd92215b81f17b1c594dfd539 in branch refs/heads/master from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=196cd66 ] TS-2257 More fixes for healtchecks plugin losing events > Healthcheck plugin can stop watching for inotify events > --- > > Key: TS-2257 > URL: https://issues.apache.org/jira/browse/TS-2257 > Project: Traffic Server > Issue Type: Bug > Components: Plugins >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 4.1.0 > > > Under certain conditions, the healthcheck plugin can stop watching some > inotify events, and therefore stop taking action on such events. > The problem is in the garbage collection, and i have a fix for it. -- This message was sent by Atlassian JIRA (v6.1#6144)
