[
https://issues.apache.org/jira/browse/TS-4391?focusedWorklogId=26734&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26734
]
ASF GitHub Bot logged work on TS-4391:
--------------------------------------
Author: ASF GitHub Bot
Created on: 22/Aug/16 00:18
Start Date: 22/Aug/16 00:18
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/883
👍
Issue Time Tracking
-------------------
Worklog Id: (was: 26734)
Time Spent: 40m (was: 0.5h)
> Duplicated parent origin retry types
> ------------------------------------
>
> Key: TS-4391
> URL: https://issues.apache.org/jira/browse/TS-4391
> Project: Traffic Server
> Issue Type: Bug
> Components: Parent Proxy
> Reporter: James Peach
> Assignee: John Rushford
> Fix For: 7.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We have:
> {code}
> enum ParentRetry_t {
> PARENT_RETRY_NONE = 0,
> PARENT_RETRY_SIMPLE = 1,
> PARENT_RETRY_UNAVAILABLE_SERVER = 2,
> // both simple and unavailable server retry
> PARENT_RETRY_BOTH = 3
> };
> {code}
> and
> {code}
> enum ParentOriginRetry_t {
> PARENT_ORIGIN_UNDEFINED_RETRY = 0x0,
> PARENT_ORIGIN_SIMPLE_RETRY = 0x1,
> PARENT_ORIGIN_UNAVAILABLE_SERVER_RETRY = 0x2
> };
> {code}
> The parent selection configuration sets values in terms of {{ParentRetry_t}}
> but the transaction state machine checks {{ParentOriginRetry_t}}. We need to
> define these once and use them consistently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
