[ https://issues.apache.org/jira/browse/TS-4701?focusedWorklogId=30637&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30637 ]
ASF GitHub Bot logged work on TS-4701: -------------------------------------- Author: ASF GitHub Bot Created on: 14/Oct/16 14:24 Start Date: 14/Oct/16 14:24 Worklog Time Spent: 10m Work Description: Github user jrushford closed the pull request at: https://github.com/apache/trafficserver/pull/1084 Issue Time Tracking ------------------- Worklog Id: (was: 30637) Time Spent: 3h (was: 2h 50m) > Add a new latched parent selection strategy. > -------------------------------------------- > > Key: TS-4701 > URL: https://issues.apache.org/jira/browse/TS-4701 > Project: Traffic Server > Issue Type: New Feature > Components: Parent Proxy > Reporter: John Rushford > Assignee: John Rushford > Fix For: 7.1.0, sometime > > Time Spent: 3h > Remaining Estimate: 0h > > For live linear video we are utilizing parent selection to round robin to > origin servers in the event of a origin server failure, parent_is_proxy=false > and round_robin=false. With this round robin strategy, the first parent in > the parent.config list is always selected. In the event of a connection > failure, a new parent is selected from the list. This works fine except that > switching to a new parent is expensive, in that the client has to retune > because the abr manifests between origins are different. A single retune can > be tolerated but, after the parent retry time has elapsed, the round robin > strategy will revert back to the original parent when it becomes available. > This causes a second retune. In order to minimize client retuning, I'd like > to add a new round robin strategy that is similar to round_robin=false but > the new strategy would stay "latched" to the selected parent and remain > "latched" until such time that a connection failure warrants using a new > parent. I propose calling this strategy "latched" as in an electronic latch > that becomes fixed in a particular state when triggered. This strategy would > be a minor modification to ParentRoundRobin and ParentSelection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)