You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/04/17 15:29:58 UTC

[jira] [Created] (AMBARI-10566) Ambari Upgrade from 1.7.0 to 2.0.0 fails to restart ZK server due to missing symlink

Dmitry Lysnichenko created AMBARI-10566:
-------------------------------------------

             Summary: Ambari Upgrade from 1.7.0 to 2.0.0 fails to restart ZK server due to missing symlink
                 Key: AMBARI-10566
                 URL: https://issues.apache.org/jira/browse/AMBARI-10566
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko
             Fix For: 2.0.1


Ambari upgrade from 1.7.0 to 2.0.0 had problems on starting/restarting zookeeper server because /usr/hdp/current/zookeeper-server symlink was not found. The customer remedied the issue by calling "hdp-select set zookeeper-server 2.2.3.0-###" on all of the hosts, which created the symlink.
In Ambari 1.7.0, ZK server was started using the libs from ZK client, so as part of the Ambari Upgrade, we need to first call "hdp-select set zookeeper-server
{version}
"
It's possible that the either exactly one of start/restart command will handle this. Need to verify what the behavior is.



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