Github user qqsun8819 commented on the pull request:
https://github.com/apache/spark/pull/214#issuecomment-38532473
Thanks for your advice @kayousterhout . And my understand for what you
mean is create a TaskResultGetter-like class, and this class main a threadpool
inside it , and everytime resourceOffer gets a task to serialize , it just
equeue it ,and when serialization finished, it just call TaskScheduler to
handle .For doing this, this two class just achieve asynchronous status. Is
that what you mean? If you think so , I can update my patch according to this
---
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.
---
