[
https://issues.apache.org/jira/browse/TS-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269118#comment-15269118
]
John Rushford commented on TS-4413:
-----------------------------------
The consistent hash functions lookup(), lookup_available(), and
lookup_by_hashval() take an iterator pointer as an argument and modify this
iterator as part of the search through the map. The state of this iterator
needs to be kept in the HttpTransaction state so that nextParent() if called
works correctly. I saw a segmentation fault when under heavy load while the
hash table was being search for parents. Currently there is only one iterator
per ParentConsistentHash instance. There needs to be an iterator per
HttpTransaction for correct lookups into the hash table.
> Fix potential consistent hash iterator race.
> --------------------------------------------
>
> Key: TS-4413
> URL: https://issues.apache.org/jira/browse/TS-4413
> Project: Traffic Server
> Issue Type: Bug
> Components: Parent Proxy
> Reporter: John Rushford
> Assignee: John Rushford
>
> There is a potential race with the iterators used in parent consistent hash
> lookups. PR follows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
