[
https://issues.apache.org/jira/browse/TS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450172#comment-13450172
]
Phil Sorber commented on TS-1416:
---------------------------------
02024e4 TS-1416: Do not do cache lookup if cop_test_page is true to stop
artificial increase of cache misses.
> Heartbeat increases Cache Misses count
> --------------------------------------
>
> Key: TS-1416
> URL: https://issues.apache.org/jira/browse/TS-1416
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 3.2.0
> Environment: Centos 6.3
> Reporter: Jon Cowie
> Priority: Minor
> Fix For: 3.3.1
>
> Attachments: cop_no_cache_lookup.diff
>
>
> With no network traffic going to the TS box, the following increase in Read
> Misses can be seen:
> {code}
> trafficserver> show:cache-stats
> Bytes Used --- 0 GB
> Cache Size --- 9 GB
> --RAM Cache--
> Total Bytes -- 10737418240
> Bytes Used --- 0
> Hits --------- 0
> Misses ------- 0
> --Lookups--
> In Progress -- 0
> Hits --------- 0
> Misses ------- 0
> --Reads--
> In Progress -- 0
> Hits --------- 0
> Misses ------- 35
> --Writes--
> In Progress -- 0
> Hits --------- 0
> Misses ------- 0
> --Updates--
> In Progress -- 0
> Hits --------- 0
> Misses ------- 0
> --Removes--
> In Progress -- 0
> Hits --------- 0
> Misses ------- 0
> {code}
> After discussion with PSUdaemon, he identified this as occurring as follows:
> {code}
> <PSUdaemon> in iocore/cache/CacheRead.cc
> <PSUdaemon> CACHE_INCREMENT_DYN_STAT(cache_read_failure_stat);
> {code}
> This isn't a particularly serious bug, but it does mean that when testing the
> box the Cache Miss count is artificially high.
--
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
