Github user squito commented on the issue:
https://github.com/apache/spark/pull/16354
@mridulm @markhamstra @kayousterhout
This is *not* ready to merge -- it needs some cleanup and more tests -- but
I thought that seeing an implementation might help think through the design. I
think the discussion should still center on the overall approach, and that
discussion should probably happen on the jira, not here. (I'll happily fix
code issues if that would help.)
Obviously, this is a pretty big change to the way delay scheduling works;
I'd gladly consider alternative approaches that dont' involve such a large
change in behavior, but I don't see them. IMO this problem is serious enough
that it merits the large behavior change.
---
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]
