[
https://issues.apache.org/jira/browse/STORM-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387195#comment-14387195
]
ASF GitHub Bot commented on STORM-593:
--------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/349#issuecomment-87789524
Yes, I see before 861a92eab8740cfc0f83ac4d7ade9a2ab04a8b9b we checked
task->node+port.
I'll file an issue to track, since it is a different problem/fix than
covered by this JIRA issue and pull request.
> No need of rwlock for clojure atom
> -----------------------------------
>
> Key: STORM-593
> URL: https://issues.apache.org/jira/browse/STORM-593
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: xiajun
> Assignee: xiajun
>
> cached-node+port->socket in worker-data is atom, there on need for rwlock
> endpoint-socket-lock to protect cached-node+port->socket. And after use
> rwlock, there will be competition between refresh-connections and message
> send.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
