hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-69) RM should throw different exceptions for while querying app/node/queue
Date Fri, 31 Aug 2012 19:49:08 GMT

     [ https://issues.apache.org/jira/browse/YARN-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod Kumar Vavilapalli moved MAPREDUCE-3865 to YARN-69:

          Component/s:     (was: resourcemanager)
                           (was: mrv2)
    Affects Version/s:     (was: 0.23.0)
                  Key: YARN-69  (was: MAPREDUCE-3865)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
> RM should throw different exceptions for while querying app/node/queue
> ----------------------------------------------------------------------
>                 Key: YARN-69
>                 URL: https://issues.apache.org/jira/browse/YARN-69
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
> We should distinguish the exceptions for absent app/node/queue, illegally accessed app/node/queue
etc. Today everything is a {{YarnRemoteException}}. We should extend {{YarnRemoteException}}
to add {{NotFoundException}}, {{AccessControlException}} etc. Today, {{AccessControlException}}
exists but not as part of the protocol descriptions (i.e. only available to Java).

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

View raw message