[
https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714224#comment-13714224
]
Hitesh Shah commented on YARN-873:
----------------------------------
I dont think it is that trivial to set -1/-2/-3 ... based on a set of known
issues. bin/yarn is used for multiple different aspects. There are likely a
common set of failures which should return a common error code across all the
usage aspects which could be added on by tool specific failure codes
partitioned to different ranges.
I think going to a simpler -1 for all errors may suffice for now. However, with
this in mind, are you planning to catch all exceptions or just a select few?
> YARNClient.getApplicationReport(unknownAppId) returns a null report
> -------------------------------------------------------------------
>
> Key: YARN-873
> URL: https://issues.apache.org/jira/browse/YARN-873
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.1.0-beta
> Reporter: Bikas Saha
> Assignee: Xuan Gong
> Attachments: YARN-873.1.patch, YARN-873.2.patch, YARN-873.3.patch
>
>
> How can the client find out that app does not exist?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
