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 2013/01/23 23:53:14 UTC
[jira] [Commented] (TS-1510) Large files being purged from cache
incorrectly
[ https://issues.apache.org/jira/browse/TS-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561195#comment-13561195 ]
Kingsley Foreman commented on TS-1510:
--------------------------------------
Ok an update on this, it appears it isn't going into cache correctly. This file is 1.8gb, and the cache is mostly empty (spare 1TB)
I've done a bit of testing, and things look a little like this
[Jan 24 09:09:16.758] Server {0x2adf1b819700} DEBUG: (http_cache_write) [59] writing to cache with URL http://127.0.0.1:8081/20022/depot/209541/chunk/bd4874c63dfe699dcec21da7efe31930c73334f9
[Jan 24 09:09:16.759] Server {0x2adf1b819700} DEBUG: (http_cache) [59] [&HttpCacheSM::state_cache_open_write, CACHE_EVENT_OPEN_WRITE_FAILED]
[Jan 24 09:09:16.760] Server {0x2adf1b819700} DEBUG: (http) [59] [HttpSM::main_handler, CACHE_EVENT_OPEN_WRITE_FAILED]
[Jan 24 09:09:16.760] Server {0x2adf1b819700} DEBUG: (http) [59] [&HttpSM:state_cache_open_write, CACHE_EVENT_OPEN_WRITE_FAILED]
So for some reason it isn't going into cache correctly.
> 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.3
>
>
> 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