[
https://issues.apache.org/jira/browse/TS-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761064#comment-13761064
]
Leif Hedstrom commented on TS-2168:
-----------------------------------
Right, but go back and read the thread . Since we can't make it conditional on
records.config, doing it only in RecordsConfig.cc makes it impossible to
properly implement the verification features that was requested in a different
ticket (which is a great feature for good user experience).
So, we should keep records.config in sync with RecordsConfig.cc at all time.
That was the whole point of this exercise.
Another option, which I'm sure you won't like, is to remove these configs from
records.config. As you know, we don't have everything in there anyways. This
would in fact be my personal preference until this feature is always enabled at
build time, but I'm not going to argue over this endlessly.
So, lets just make records.config and RecordsConfig.cc always match up; if a
configuration is in records.config, it must always exist in RecordsConfig.cc,
with the same value.
> Confusion about proxy.config.allocator.enable_reclaim setting
> -------------------------------------------------------------
>
> Key: TS-2168
> URL: https://issues.apache.org/jira/browse/TS-2168
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: David Carlin
> Assignee: Leif Hedstrom
> Fix For: 4.1.0
>
> Attachments:
> 0001-TS-2168-Use-if-condition-to-control-reclaimable-free.patch
>
>
> The default records.config in 4.0.1 says the following which is contradictory:
> {noformat}
> # The value of enable_reclaim should be 0 or 1. Default 1, reclaim enabled.
> CONFIG proxy.config.allocator.enable_reclaim INT 0
> {noformat}
> mgmt/RecordsConfig.cc shows the following:
> {RECT_CONFIG, "proxy.config.allocator.enable_reclaim", RECD_INT, "1",
> RECU_NULL, RR_NULL, RECC_NULL, "[0-1]", RECA_NULL}
> So the default is 1, but records.config changes it to 0.
--
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
