[ 
https://issues.apache.org/jira/browse/TS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718601#comment-13718601
 ] 

Phil Sorber commented on TS-1510:
---------------------------------

With the latest master I am able to cache large objects and retrieve them.

First request:
{noformat}
-bash-4.1$ curl -v -4 -o /dev/null http://proxyhost/Fedora-19-x86_64-DVD.iso
* About to connect() to proxyhost port 80 (#0)
*   Trying 1.2.3.4... connected
* Connected to proxyhost (1.2.3.4) port 80 (#0)
> GET /Fedora-19-x86_64-DVD.iso HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-unknown-linux-gnu) libcurl/7.19.7 
> NSS/3.12.7.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Host: proxyhost
> Accept: */*
> 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0< 
HTTP/1.1 200 OK
< Content-Type: application/octet-stream
< Accept-Ranges: bytes
< Content-Length: 4444913664
< Date: Wed, 24 Jul 2013 17:13:08 GMT
< Server: ATS/3.3.5-dev
< Age: 1
< Connection: keep-alive
< Via: http/1.1 proxyhost (ApacheTrafficServer/3.3.5-dev [uScMsSfWpSeN:t cCMi p 
sS])
< 
{ [data not shown]
100 4239M  100 4239M    0     0   137M      0  0:00:30  0:00:30 --:--:--  140M* 
Connection #0 to host proxyhost left intact

* Closing connection #0
{noformat}

Then the second request that pulls from cache:
{noformat}
-bash-4.1$ curl -v -4 -o /dev/null http://proxyhost/Fedora-19-x86_64-DVD.iso
* About to connect() to proxyhost port 80 (#0)
*   Trying 1.2.3.4... connected
* Connected to proxyhost (1.2.3.4) port 80 (#0)
> GET /Fedora-19-x86_64-DVD.iso HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-unknown-linux-gnu) libcurl/7.19.7 
> NSS/3.12.7.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Host: proxyhost
> Accept: */*
> 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0< 
HTTP/1.1 200 OK
< Content-Type: application/octet-stream
< Accept-Ranges: bytes
< Content-Length: 4444913664
< Date: Wed, 24 Jul 2013 17:13:08 GMT
< Server: ATS/3.3.5-dev
< Age: 50
< Connection: keep-alive
< Via: http/1.1 proxyhost (ApacheTrafficServer/3.3.5-dev [uScHs f p eN:t cCHi p 
s ])
< 
{ [data not shown]
100 4239M  100 4239M    0     0   183M      0  0:00:23  0:00:23 --:--:--  179M* 
Connection #0 to host proxyhost left intact

* Closing connection #0
{noformat}

Here is the related server debug output:
{noformat}
[Jul 24 17:13:09.318] Server {0x7fc85aaa4700} DEBUG: (http_cache_write) [5] 
writing to cache with URL http://127.0.0.1:8080/Fedora-19-x86_64-DVD.iso
[Jul 24 17:13:09.318] Server {0x7fc85aaa4700} DEBUG: (http_cache) [5] 
[&HttpCacheSM::state_cache_open_write, CACHE_EVENT_OPEN_WRITE]
[Jul 24 17:13:58.973] Server {0x7fc85b5af700} DEBUG: (http_cache) [6] 
[&HttpCacheSM::state_cache_open_read, CACHE_EVENT_OPEN_READ]
{noformat}

I am going to mark this as not reproducible. If there is some new information 
that makes his more reproducible then please re-open.
                
> Large files being purged from cache incorrectly
> -----------------------------------------------
>
>                 Key: TS-1510
>                 URL: https://issues.apache.org/jira/browse/TS-1510
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache
>    Affects Versions: 3.3.0
>         Environment: Ubuntu 10.04 and 12.04
>            Reporter: Kingsley Foreman
>            Assignee: Phil Sorber
>              Labels: A
>             Fix For: 3.3.5
>
>
> With an empty cache of 120gb.
> I've added two files. 
> 1. 2mb file
> 2. 3gb file.
> after 30min
> 2mb file remains in cache rechecks home (304) serves from cache
> 3gb file not i cache, and does a 200 request from the origin server like it 
> has been cleared from cache.
> There is plenty of space so it isn't expiring, so really it should do a 304 
> not a 200 to the origin server.

--
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

Reply via email to