[
https://issues.apache.org/jira/browse/STORM-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2833.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.1.2
1.2.0
2.0.0
Thanks [~revans2], I merged into master, 1.x, 1.1.x branches.
> Cached Netty Connections can have different keys for the same thing.
> --------------------------------------------------------------------
>
> Key: STORM-2833
> URL: https://issues.apache.org/jira/browse/STORM-2833
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-client
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Labels: pull-request-available
> Fix For: 2.0.0, 1.2.0, 1.1.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> It turns out that if you set {{storm.local.hostname}} on your supervisors
> that the netty caching code might not work. The issue is that when we go to
> add a netty connection to the cache we use the host name provided by the
> scheduling. Which ultimately comes from the {{storm.local.hostname}} setting
> on each of the nodes. But when we go to remove it from the cache, we use the
> resolved INetSocket address for the destination. If the two do not match
> exactly then we can close a connection, but not have it removed from the
> cache, so when we go to try and use it again, the connection is closed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
