[
https://issues.apache.org/jira/browse/TS-4707?focusedWorklogId=26193&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26193
]
ASF GitHub Bot logged work on TS-4707:
--------------------------------------
Author: ASF GitHub Bot
Created on: 03/Aug/16 20:33
Start Date: 03/Aug/16 20:33
Worklog Time Spent: 10m
Work Description: Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/834
I think I'm ok with this for now, but I really wish we'd done something
similar to TSHttpTxnCacheLookupUrlGet() / TSHttpTxnCacheLookupUrlSet(), but for
the parent selection URL to use. Like
tsapi TSReturnCode TSHttpTxnParentSelectionUrlGet(TSHttpTxn txnp,
TSMBuffer bufp, TSMLoc obj);
tsapi TSReturnCode TSHttpTxnParentSelectionUrlSet(TSHttpTxn txnp,
TSMBuffer bufp, TSMLoc obj);
And then we could either have extended the functionality in the cachekey
plugin (or, make a new plugin). There's generally a problem when a plugin
changes the cache key as well, and the parent selection does not follow the
same lead, the stop-gap solution for that was the ignore query params option.
See
https://issues.apache.org/jira/browse/TS-4025
for some more discussions. My "objection" here is that we're making some
very specific use case changes / features, whereas new APIs, and support for it
in the existing cachekey plugin (which is very feature rich) would solve not
just these two cases, but a lot more.
Issue Time Tracking
-------------------
Worklog Id: (was: 26193)
Time Spent: 50m (was: 40m)
> Parent Consistent Hash Selection - add fname and maxdirs options.
> -----------------------------------------------------------------
>
> Key: TS-4707
> URL: https://issues.apache.org/jira/browse/TS-4707
> Project: Traffic Server
> Issue Type: Improvement
> Components: Parent Proxy
> Reporter: Peter Chou
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This enhancement adds two options, "fname" and "maxdirs", which can be used
> to exclude the file-name and some of the directories in the path. The
> remaining portions of the path are then used as part of the hash computation
> for selecting among multiple parent caches.
> For our usage, it was desirable from an operational perspective to direct all
> components of particular sub-tree to a single parent cache (to simplify
> trouble-shooting, pre-loading, etc.). This can be achieved by excluding the
> query-string, file-name, and right-most portions of the path from the hash
> computation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
