[
https://issues.apache.org/jira/browse/AMBARI-11476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-11476:
-----------------------------------------
Description:
STR:
Installed Ambari 2.1.0 at build 1638
Installed HDP 2.3.0.0 at build 1330 on 4 hosts running CentOS6, with only HDFS,
YARN, MR, ZK, OOZIE
Ran Oozie Service Check, which passed
Enabled NameNode HA
Installed bits for HDP 2.3.0.0 at build 1334
Added oozie config oozie.connection.retry.count in oozie-env
Started RU.
*After Core Masters, there was a Service Check that included Oozie and it
failed.*
*When Oozie Server was restarted that failed.*
This occurs because when Core Masters are upgraded and the round of Service
Checks are ran, the Oozie Service Check does not contain yarn-site.xml in its
config folder.
When Oozie Server is then upgraded, it fails because the tarball of the old
conf folder actually zips the conf folder itself, so when it is unpacked, it
creates /usr/hdp/2.3.0.0-2130/oozie/conf/conf/
was:
STR:
Installed Ambari 2.1.0 at build 1638
Installed HDP 2.3.0.0 at build 1330 on 4 hosts running CentOS6, with only HDFS,
YARN, MR, ZK, OOZIE
Ran Oozie Service Check, which passed
Enabled NameNode HA
Installed bits for HDP 2.3.0.0 at build 1334
Added oozie config oozie.connection.retry.count in oozie-env
Started RU.
*After Core Masters, there was a Service Check that included Oozie and it
failed.*
*When Oozie Server was restarted that failed.*
See logs
> RU from Dal to Dal+ has failures in First Oozie Service Check, then Oozie
> Server Start, because yarn-site.xml missing from hadoop conf and conf folder
> is incorrect
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-11476
> URL: https://issues.apache.org/jira/browse/AMBARI-11476
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.1.0
>
>
> STR:
> Installed Ambari 2.1.0 at build 1638
> Installed HDP 2.3.0.0 at build 1330 on 4 hosts running CentOS6, with only
> HDFS, YARN, MR, ZK, OOZIE
> Ran Oozie Service Check, which passed
> Enabled NameNode HA
> Installed bits for HDP 2.3.0.0 at build 1334
> Added oozie config oozie.connection.retry.count in oozie-env
> Started RU.
> *After Core Masters, there was a Service Check that included Oozie and it
> failed.*
> *When Oozie Server was restarted that failed.*
> This occurs because when Core Masters are upgraded and the round of Service
> Checks are ran, the Oozie Service Check does not contain yarn-site.xml in its
> config folder.
> When Oozie Server is then upgraded, it fails because the tarball of the old
> conf folder actually zips the conf folder itself, so when it is unpacked, it
> creates /usr/hdp/2.3.0.0-2130/oozie/conf/conf/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
