You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/09/05 04:37:46 UTC
[jira] [Commented] (MAPREDUCE-6442) Stack trace is missing when
error occurs in client protocol provider's constructor
[ https://issues.apache.org/jira/browse/MAPREDUCE-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731735#comment-14731735 ]
Hudson commented on MAPREDUCE-6442:
-----------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #8408 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8408/])
MAPREDUCE-6442. Stack trace is missing when error occurs in client protocol provider's constructor Contributed by Chang Li. (ozawa: rev 9b685773ec1031e90cc2b8aedb42670721757e22)
* hadoop-mapreduce-project/CHANGES.txt
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/Cluster.java
> Stack trace is missing when error occurs in client protocol provider's constructor
> ----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6442
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6442
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Reporter: Chang Li
> Assignee: Chang Li
> Fix For: 2.7.2
>
> Attachments: MAPREDUCE-6442.2.patch, MAPREDUCE-6442.patch
>
>
> when provider creation fail dump the stack trace rather than just print out the message
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)