Github user jpeach commented on a diff in the pull request:

    https://github.com/apache/trafficserver/pull/1084#discussion_r82291438
  
    --- 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 --
    
    s/unavilable/unavailable/


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to