Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4770#issuecomment-76036782
@pankajarora12 Data generated by `DiskBlockManager` cannot be deleted since
it may be used by other executors when using the external shuffle service. You
may be able to optimize to delete these things when not using the external
service, but that sounds like the wrong approach.
If it's the shuffle data that is accumulating, maybe the right fix is for
the block manager to properly clean up shuffle files that are not used anymore.
The executor doesn't have enough information for that, as far as I can tell,
and the driver would need to tell executors when RDDs are gc'ed so that their
shuffle data can be cleaned up. Maybe that's already done, even, but I don't
know.
Well, long story short, this change seems to break dynamic allocation and
anything that uses the external shuffle service, so it really cannot be pushed.
---
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]
