Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 15 Aug 2012 05:39:38 +1100 (NCT)
From: "Mayank Bansal (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <891365558.8813.1344969578169.JavaMail.jiratomcat@arcas>
In-Reply-To: <395460184.51569.1340642384196.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (MAPREDUCE-4367) mapred job -kill tries to
 connect to history server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mayank Bansal commented on MAPREDUCE-4367:
------------------------------------------

Found the JIRA which addresses above issue
MAPREDUCE-4470

Thanks,
Mayank
                
> mapred job -kill tries to connect to history server
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-4367
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4367
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client, mrv2
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Assignee: Mayank Bansal
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: MAPREDUCE-4367-trunk-v1.patch, MAPREDUCE-4367-trunk-v2.patch
>
>
> The {{mapred job -kill}} command attempts to connect to the history server, even though it is unrelated to the process of killing a job.

--
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