[
https://issues.apache.org/jira/browse/AMBARI-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-9579:
---------------------------------------
Attachment: AMBARI-9579.patch
> 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)
