Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/10846
Ok, so this is actually two bugs:
- more forcefully respecting the "retainedStages" config; now the code
might actually stop showing active stages on the web ui, right? Not sure how
big of an issue that is. I guess that was a possibility in the previous code
too, so probably ok.
- adding a new conf to stop caching of hadoop conf objects; it seems like
there's a more fundamental problem in that after something is cached with
`HadoopRDD.putCachedMetadata`, it never goes away.
So your new config avoids that issue, but it seems like there should be
code that "uncaches" those values when the HadoopRDD instance is collected.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
