Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 28 Feb 2012 17:59:46 +0000 (UTC)
From: "Thomas Graves (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1459280548.29171.1330451986496.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <509120321.4934.1328218976779.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3792) job -list displays only the
 jobs submitted by a particular user
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218406#comment-13218406 ] 

Thomas Graves commented on MAPREDUCE-3792:
------------------------------------------

So now if you are a user that doesn't have acl permissions to the job, this causees mapred job -status or any other command that goes to app master to hang since its returning host name of N/A.  The clientServiceDelegate getProxy() is expecting the host to be valid.  We need to fix it so it doesn't hang and somehow gives a useful error message to give the user some reason why these are failing.
                
> job -list displays only the jobs submitted by a particular user
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-3792
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3792
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Ramya Sunil
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: MAPREDUCE-3792.patch
>
>
> "mapred job -list" lists only the jobs submitted by the user who ran the command. This behavior is different from 1.x. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira