[ 
https://issues.apache.org/jira/browse/TS-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761083#comment-13761083
 ] 

ASF subversion and git services commented on TS-2168:
-----------------------------------------------------

Commit 2c194735ff40ef4272002ff9dde0c3c977d04009 in branch refs/heads/master 
from [~yunkai]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=2c19473 ]

TS-2168: keep records.config in sync with RecordsConfig.cc at all time

According a long discussion on TS-2168 ticket:

"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" -- Leif

Let's remove #if TS_USE_RECLAIMABLE_FREELIST to keep records.config in
sync with RecordsConfig.cc at all time.

Signed-off-by: Yunkai Zhang <[email protected]>

                
> 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

Reply via email to