GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/17925
[SPARK-20205][core] Make sure StageInfo is updated before sending event.
The DAGScheduler was sending a "stage submitted" event before it properly
updated the event's information. This meant that a listener (e.g. the
even logging listener) could record wrong information about the event.
The change slightly changes the semantics of skipped stages (those that
have no pending tasks), making their event contain a submission time. I
think that's more correct given that a "stage submitted" event is being
generated, even if no tasks will be run.
Tested with existing unit tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vanzin/spark SPARK-20205
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17925.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17925
----
commit 0d8f717ea722b2afec68988f8ec9705dd24d784a
Author: Marcelo Vanzin <[email protected]>
Date: 2017-05-09T20:21:41Z
[SPARK-20205][core] Make sure StageInfo is updated before sending event.
The DAGScheduler was sending a "stage submitted" event before it properly
updated the event's information. This meant that a listener (e.g. the
even logging listener) could record wrong information about the event.
The change slightly changes the semantics of skipped stages (those that
have no pending tasks), making their event contain a submission time. I
think that's more correct given that a "stage submitted" event is being
generated, even if no tasks will be run.
----
---
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]
