[ 
https://issues.apache.org/jira/browse/TS-4707?focusedWorklogId=26199&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26199
 ]

ASF GitHub Bot logged work on TS-4707:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Aug/16 20:04
            Start Date: 04/Aug/16 20:04
    Worklog Time Spent: 10m 
      Work Description: Github user pbchou commented on the issue:

    https://github.com/apache/trafficserver/pull/834
  
    @zwoop I implemented the two API calls that you recommended above (along 
with the two corresponding ts_lua API calls). However, I did not see a graceful 
way to get the URL set via the API calls to the ParentConsistentHash.cc hash 
generation function since it is only passing the request_data and not the 
entire HTTP transaction. As a work-around, I wrote the URL into an "@ATS..." 
MIME field to accomplish the data exchange. The plus to this is that you can 
set the MIME field without using the API (and it does not need to be a valid 
URL if set with this method). The hash generation will just hash the contents 
of this MIME field if it is defined (and ignore the other options maxdirs, 
fname, and qstring). I retained the maxdirs and fname enhancements in the 
earlier commit as I have not yet sold my users on this new approach.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 26199)
    Time Spent: 1h  (was: 50m)

> 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: 1h
>  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)

Reply via email to