[
https://issues.apache.org/jira/browse/TS-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561515#comment-14561515
]
Sudheer Vinukonda edited comment on TS-2944 at 5/27/15 7:09 PM:
----------------------------------------------------------------
[~dcarlin] just found that the *crc* log field is now showing *TCP_MEM_HIT* in
place of *TCP_HIT*. This breaks some tools that we have that are dependent on
the log field values - Wondering if this is an incompatible change to make in a
dot release. We are yet to update to 5.3 from 5.0, but, this change means, we
will need to update the tools. Besides, TS-3036 added a new log field *chm*,
which seems to give similar (and better!) info.
was (Author: sudheerv):
@dcarlin just found that the *crc* log field is now showing *TCP_MEM_HIT* in
place of *TCP_HIT*. This breaks some tools that we have that are dependent on
the log field values - Wondering if this is an incompatible change to make in a
dot release. We are yet to update to 5.3 from 5.0, but, this change means, we
will need to update the tools. Besides, TS-3036 added a new log field *chm*,
which seems to give similar (and better!) info.
> remove proxy.config.http.record_tcp_mem_hit
> -------------------------------------------
>
> Key: TS-2944
> URL: https://issues.apache.org/jira/browse/TS-2944
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cleanup, Configuration
> Reporter: James Peach
> Assignee: James Peach
> Priority: Minor
> Fix For: 5.1.0
>
>
> {{proxy.config.http.record_tcp_mem_hit}} is not documented and does not
> appear to be very useful. There's no reason to not record RAM cache hits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
