Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6294#issuecomment-122071586
@harishreedharan Yeah, my bad. I had a offline discussion with @zsxwing
about this. Our initial attempt to merge this PR into the receiver scheduling
PR #7276 made that PR very complex and hard to reason about with a lot of
locks. So we decided to split the PR back, and solve each one separately. So
the plan is that we are first going to solve this PR without adding any locks.
Then it will be easier to reason about when #7276 is applied, hopefully without
introducing locks as well.
---
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]
