Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/5572#issuecomment-105257082
@squito you said:
> con: newly cached blocks, effectively adding some replication, but using
extra memory. Users will most > likely find that extra caching quite
unexpected, and also won't have any way to undo it.
I agree that it uses extra memory. But as we only keep a copy of remote
block for all rdd1 partitions, it might use less memory than just unrolling the
rdd2 partition in multiple tasks? As these remote blocks are cached with spark,
I think user can using `unpersist` to explicitly remove them too?
---
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]
