ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14764) MapReduce, Oozie service check failures after upgrade finished
Date Fri, 22 Jan 2016 08:40:39 GMT

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

Hadoop QA commented on AMBARI-14764:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12783634/AMBARI-14764.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5021//console

This message is automatically generated.

> MapReduce, Oozie service check failures after upgrade finished
> --------------------------------------------------------------
>
>                 Key: AMBARI-14764
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14764
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-14764.patch
>
>
> # MapReduce jobs were failing after upgrading and restarting MapReduce2 service (ClassNotFound
exception). Also Oozie job were failing because of the same reason.
> # This was caused because mapreduce.application.classpath property had the older version
of the LZO codec (/usr/hdp/current/hadoop/lib/hadoop-lzo-0.6.0.<OLD-STACK-VERSION>.jar).
> # During upgrade the path was valid because we had not switched /usr/hdp/current/hadoop
symlink to new version. After upgrade, once the symlink is updated to new stack version and
after restarting MapReduce2 this path becomes invalid.
> # To fix this updated the LZO codec path to /usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar
in mapreduce.application.classpath config property. Also in oozie-env property added export
HADOOP_OPTS="-Dhdp.version=$HDP_VERSION $HADOOP_OPTS”
> Fix:
> # During stack upgrade, update lzo codec path in mapreduce.application.classpath to
> {code}
> /usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar
> {code}
> Also, looks like we also need to update following property for TEZ.
> {code}
> <property>
> <name>tez.cluster.additional.classpath.prefix</name>
> <value>/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar:/etc/hadoop/conf/secure</value>
> <description></description>
> </property>
> {code}
> # Update oozie-env and add
> {code}
> export HADOOP_OPTS="-Dhdp.version=$HDP_VERSION $HADOOP_OPTS"
> {code}
> # Add upgrade pre-checks to validate if any config properties have old-stack-version
hardcodings and report these config properties to be updated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message