Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4741#issuecomment-75722148
LGTM; this is a good catch. It looks like this issue is present in the
1.2.x as well, since there's no`stageIdToActiveJobIds.remove()` call there,
either. JobProgressListener has a test that is designed to prevent memory
leaks in these collections, but it looks like the test trivially passed for
this collection because it didn't involve a workload that caused the collection
to be populated in the first place.
---
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]
