You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Kingsley Foreman (JIRA)" <ji...@apache.org> on 2012/10/08 03:22:03 UTC
[jira] [Created] (TS-1510) Large files being purged from cache
incorrectly
Kingsley Foreman created TS-1510:
------------------------------------
Summary: 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
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
[jira] [Updated] (TS-1510) Large files being purged from cache
incorrectly
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1510:
------------------------------
Fix Version/s: 3.3.2
> 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
> Fix For: 3.3.2
>
>
> 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