[
https://issues.apache.org/jira/browse/TS-4701?focusedWorklogId=30248&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30248
]
ASF GitHub Bot logged work on TS-4701:
--------------------------------------
Author: ASF GitHub Bot
Created on: 06/Oct/16 21:47
Start Date: 06/Oct/16 21:47
Worklog Time Spent: 10m
Work Description: Github user jrushford commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/1084#discussion_r82292764
--- Diff: doc/admin-guide/files/parent.config.en.rst ---
@@ -207,6 +207,13 @@ The following list shows the possible actions and
their allowed values.
The other traffic is unaffected. Once the downed parent becomes
available, the traffic distribution returns to the pre-down
state.
+ - ``latched`` - The first parent in the list is marked as primary and
is
+ always chosen until connection errors cause it to be marked down.
When
+ this occurs the next parent in the list then becomes primary. The
primary
+ will wrap back to the first parent in the list when it is the last
parent
+ in the list and is marked down due to a connection error. Newly
chosen
+ primary parents marked as unavilable will then be restored if the
failure
--- End diff --
thanks, i've fixed that.
Issue Time Tracking
-------------------
Worklog Id: (was: 30248)
Time Spent: 1h 50m (was: 1h 40m)
> 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: sometime
>
> Time Spent: 1h 50m
> 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)
