[
https://issues.apache.org/jira/browse/AMBARI-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316884#comment-14316884
]
Hudson commented on AMBARI-9579:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1738 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1738/])
AMBARI-9579. After upgrading Ambari 1.6.1 to 1.7, the directory of zookeeper
server get changed to /hadoop/zookeeper (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fad54e324da628568b3a6aad3243ce36a62a3894)
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java
> After upgrading Ambari 1.6.1 to 1.7, the directory of zookeeper server get
> changed to /hadoop/zookeeper
> -------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9579
> URL: https://issues.apache.org/jira/browse/AMBARI-9579
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-9579.patch
>
>
> PROBLEM: After upgrading Ambari 1.6.1 to 1.7, the directory of zookeeper
> server get changed to /hadoop/zookeeper
> BUSINESS IMPACT: Customer is upgrading Ambari on an HA cluster. Due to this
> bug, customer was not able to start HDFS after upgrade, and was mislead to
> perform a -formatZK to workaround the issue.
> STEPS TO REPRODUCE:
> 1. Deploy a Ambari 1.6.1 cluster
> (I believe this is regardless of HDP version, but I used a HDP 2.1.3)
> 2. Set zookeeper server directory to something other than /hadoop/zookeeper
> 3. Upgrade Ambari to 1.7
> 4. Observe that zookeeper directory got change back to /hadoop/zookeeper
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
