[
https://issues.apache.org/jira/browse/TS-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-4743:
---------------------------
Summary: Parent use consistent_hash Strategy may cause crash while first
parent is not set (was: parent use consistent_hash Strategy may cause crash
while first parent is not set )
> Parent use consistent_hash Strategy may cause crash while first parent is not
> set
> ----------------------------------------------------------------------------------
>
> Key: TS-4743
> URL: https://issues.apache.org/jira/browse/TS-4743
> Project: Traffic Server
> Issue Type: Bug
> Reporter: xiangdong chen
> Assignee: John Rushford
> Fix For: 7.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> my parent.config
> eg :
> dest_domain=. secondary_parent="192.168.104.229:80|1.0;
> 192.168.104.182:80|1.0" round_robin=consistent_hash
> the crash place is :
> DEBUG: <ParentConsistentHash.cc:167 (selectParent)> (parent_select)
> wrap_around[PRIMARY]: 1, wrap_around[SECONDARY]: 0
> traffic_server: Segmentation fault (Address not mapped to object [0x10])
> ParentConsistentHash.cc:167 code:
> Debug("parent_select", "Selected parent %s is not available, looking up
> another parent.", pRec->hostname);
> Fix the code like
> Debug("parent_select", "Selected parent %s is not available, looking up
> another parent.", pRec ? pRec->hostname:"[NULL]");
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
