Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/5743#issuecomment-97192903
This is a reasonable solution, but I think that the actual issue that
TransportRequestHandler has a list of streamIds at all. I think a different
solution would be to have the StreamManager associated streams with channels
(which is a documented guarantee already to StreamManager).
This would involve making StreamManager's getChunk take a TransportClient
(or a "channelId", generated via `channel.toString`), which would update the
StreamState, and then to make connectionTerminated also take this identifier
(iterating over all streams to close associated ones).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
