[jira] [Updated] (TS-4747) If the connection of parent is not alive, update the hostdb to mark the server down.

["Bryan Call (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Call updated TS-4747:
---------------------------
    Summary: If the connection of parent is not alive, update the hostdb to mark the server down.  (was: if the connection of parent is not alive, update the hostdb to mark the server down.)

> If the connection of parent is not alive, update the hostdb to mark the server down.
> ------------------------------------------------------------------------------------
>
>                 Key: TS-4747
>                 URL: https://issues.apache.org/jira/browse/TS-4747
>             Project: Traffic Server
>          Issue Type: Improvement
>            Reporter: xiangdong chen
>            Assignee: John Rushford
>             Fix For: 7.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> the parent.config is like this:
> dest_domain=www.cxdtest.com parent=“dnstest1.com:80”;round_bin=strict
> and the dnstest1.com contains two ip:
> 192.168.1.1 （but it was down）
> 192.168.1.2
> if the request go to the parent, and the parent is domain,which contains multi ip. if one ip is down,but we not make the host down ,if the next request is comming, it will choice this ip again. we should make the host down.
> fix code on HttpTransact::handle_response_from_parent(State *s) 
> default: {
>     LookingUp_t next_lookup = UNDEFINED_LOOKUP;
>     DebugTxn("http_trans", "[hrfp] connection not alive");
>     s->state_machine->do_hostdb_update_if_necessary();//added by xdchen, make the host down,line:3606



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)