[
https://issues.apache.org/jira/browse/TEZ-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated TEZ-2854:
----------------------------------
Description:
This is a source of unending confusion among users. One could argue that
session is not a query, and it can have both failed and successful queries,
blah blah, but for the common case where the user runs exactly one query, the
query fails, and then the session is ended, it seems natural to display the
YARN app as having failed. The user doesn't associate the YARN App with any
kind of session in this case, app is a query, so either there needs to be a
massive reeducation project or the app status should follow the intuitive
understanding of the users. One could even generalize to "all DAGs in session
failed" (or "some DAGs" and make it configurable! :)), but for one query it's a
no-brainer.
was:
This is a source of unending confusion among users. One could argue that
session is not a query, and it can have both failed and successful queries,
blah blah, but for common case where the user runs one query that fails, and
ends the session, it seems natural to display the YARN app as having failed.
One could even generalize to "all DAGs in session failed" (or "some DAGs" and
make it configurable! :)), but for one query it's a no-brainer.
> Tez session where the one and only DAG has failed should be displayed as
> FAILED in YARN
> ---------------------------------------------------------------------------------------
>
> Key: TEZ-2854
> URL: https://issues.apache.org/jira/browse/TEZ-2854
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sergey Shelukhin
>
> This is a source of unending confusion among users. One could argue that
> session is not a query, and it can have both failed and successful queries,
> blah blah, but for the common case where the user runs exactly one query, the
> query fails, and then the session is ended, it seems natural to display the
> YARN app as having failed. The user doesn't associate the YARN App with any
> kind of session in this case, app is a query, so either there needs to be a
> massive reeducation project or the app status should follow the intuitive
> understanding of the users. One could even generalize to "all DAGs in session
> failed" (or "some DAGs" and make it configurable! :)), but for one query it's
> a no-brainer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
