You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2016/04/28 01:18:12 UTC

[jira] [Created] (TS-4391) duplicated parent origin retry types

James Peach created TS-4391:
-------------------------------

             Summary: 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


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)