Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3259#issuecomment-63123006
Ah, good catch regarding the `promise` field. I don't like the idea of
relying on HashedWheelTimer in order to fix this issue; it would be better to
prevent the capture of a message reference, since that's going to be a less
brittle fix. I'll see if there's a clean way to refactor this so that
TimerTask doesn't hold a promise reference.
---
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]
