Uploaded image for project: 'Apache Storm'
  1. Apache Storm
  2. STORM-2833

Cached Netty Connections can have different keys for the same thing.

    Details

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              revans2 Robert Joseph Evans
              Reporter:
              revans2 Robert Joseph Evans
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1.5h
                1.5h