You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/01/03 22:20:51 UTC

[jira] [Commented] (TS-2466) we should NOT increase the version of records.config when change the local parameter

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

Leif Hedstrom commented on TS-2466:
-----------------------------------

Is this related (or a fix?) to the previous TS-2292 commits?

> we should NOT increase the version of records.config when change the local  parameter
> -------------------------------------------------------------------------------------
>
>                 Key: TS-2466
>                 URL: https://issues.apache.org/jira/browse/TS-2466
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Yu Qing
>            Assignee: Yu Qing
>             Fix For: 4.2.0
>
>         Attachments: 0001-TS-2466-should-NOT-increase-the-version-of-records.c.patch
>
>
> the version of records.config increases when we change the local parameter using following methods:
>    1. execute: traffic_line -s  name -v value
>    2. modify the records.config and execute: traffic_line -x
> in cluster mode, the version increasement of records.config means that this file will be synced to other machines in this cluster. when we change the local parameter only, records.config should NOT be synced to other machines. so  the version of records.config should NOT increase in this case.
> the sample for the local parameters in records.config:
> LOCAL proxy.local.cluster.type INT 1
> LOCAL proxy.local.log.collation_mode INT 0



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)