Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-39129521
@andrewor14 I think cancelStage() has to cancel all jobs that depend on the
stage -- otherwise those jobs would hang. It would be nice if there was a
way to propagate an error message that says something like "This job was
cancelled because one of its stages was cancelled in the UI" back to the
JobListener, so it's clear what happened.
On Mon, Mar 31, 2014 at 12:16 PM, andrewor14
<notificati...@github.com>wrote:
> @pwendell <https://github.com/pwendell> Yeah Spark Streaming also has
> that problem. A streaming job may contain many Spark jobs, so from a
> streaming user's point of view, our breakdown of Spark jobs doesn't make
> much sense. But if you think about it, jumping directly to stages is even
> lower level for streaming users, which is why we are making a custom
> Streaming UI that links to the SparkUI. I could be wrong but I think this
> issue is also common to Shark.
>
> @kayousterhout <https://github.com/kayousterhout> Separating the two
> changes this way makes sense. I have one question for (1): does
> cancelStage() just cancels the current stage, as the name suggests? Or
does
> it cancel all the jobs that depend on that stage?
>
> --
> Reply to this email directly or view it on
GitHub<https://github.com/apache/spark/pull/246#issuecomment-39129206>
> .
>
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
