[
https://issues.apache.org/jira/browse/TC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001390#comment-16001390
]
ASF GitHub Bot commented on TC-262:
-----------------------------------
Github user jschmerge commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
The parameter is actually rather nicely documented with examples in the ATS
documentation:
https://docs.trafficserver.apache.org/en/latest/admin-guide/files/storage.config.en.html#linux-example
This patch just exposes the configuration item as a knob in traffic-ops.
> Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next
> release
> -----------------------------------------------------------------------------------
>
> Key: TC-262
> URL: https://issues.apache.org/jira/browse/TC-262
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops
> Reporter: John Schmerge
> Priority: Minor
>
> This patch adds three new parameters to control/configure the seed
> strings for the consistent hash used for cachekey->drive mapping in
> ATS... This allows an arbitrary string to be assigned as the key for
> drives instead of relying on the OS's device node name as the seed for
> the hash. The three parameters added are:
> Drive_Hash_Id
> RAM_Drive_Hash_Id
> SSD_Drive_Hash_Id
> And they specify the id keys for spinning, ram, and ssd devices.
> If this parameter is missing from the TO config for a server, the
> generated file ommits any specification of the id parameter (preserving
> the previous file generation behavior).
> Also note that the csv id strings for these three new parameters should
> order their entries to match the order of the Drive_Letters parameter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
