amoghyermalkar123 opened a new issue, #8672: URL: https://github.com/apache/trafficserver/issues/8672
I have the following cache.config configuration: ``` url_regex=subdomain.domain.com.* method=PUT method=POST method=PATCH method=DELETE method=OPTIONS method=GET method=HEAD ttl-in-cache=15s ``` i have a one child one parent tiered ATS architecture. When I request a content under the specified domain, it caches beyond the mentioned ttl-in-cache value, i.e. in this case more than 15 seconds. I tried quite some different combinations of the configuration from cache.config but nothing has worked so far. The content is always cached beyond the mentioned time frame. I have tried matching on the domains, hosts tried using that with revalidate timer, nothing seems to work. One thing to note I have cached only one image under this domain. I confirm how long its cached for by the Age header and by verifying via logs and everytime it shows TCP_MEM_HIT. I also tried purging all caches, making the first request, waiting for around 10-20 minutes before hitting the second request but same result is what I am seeing. After all this, I tried going through the CLFUS algorithm, a brief look into the cache architecture to try to understand how TTL is taken under consideration, but to no avail. I only found one reference to ttl in cache architecture that to while cache reading. In the RAM cache document there is no mention of ttl. What am I missing in all these cases? I thought maybe the TTL might be for disk cache, but for ATS to even go to disk IO would be when the object is removed from RAM which is not happening even after hours. The CLFUS algorithm is extrememly sophisticated to even consider ttl-in-cache, so I am not understanding if I am missing something? Are there some opinionated ways being followed here? Have I missed a document to go through? I understood that cache is a cycle? so maybe after the cache is full eviction begins? if so, whats the point of ttl-in-cache configuration from cache.config? Where exactly does the ttl-in-cache come into play? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
