[
https://issues.apache.org/jira/browse/AMBARI-11728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574758#comment-14574758
]
Dmitry Lysnichenko commented on AMBARI-11728:
---------------------------------------------
We decided to make requirements for initial bootstrap more loose:
- at least one component should be upgraded on each non-client host
- any client-only/unhealthy host is skipped in checks
- at least one healthy/non-client host should be in a cluster during initial
bootstrap
So customer should be able to get to CURRENT version in most cases and solve
any existing issues after that
> Upgrade Ambari from 1.7 to Ambari 2.0. I'm on HDP 2.2.0.0, but the version is
> not showing up in the Stacks and Versions page.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-11728
> URL: https://issues.apache.org/jira/browse/AMBARI-11728
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
>
> I've upgraded from Ambari 1.7 to 2.0 on my own cluster and I'm seeing the
> same problem
> Under ‘stacks and versions’, versions gives no information.
> After going through a number of troubleshooting steps, such as refreshing
> browser cache, restarting services, datanodes, rebooting etc, I think we can
> come to the conclusion that this is a bug.
> The upgrade document mentions this, however the advised actions don’t work.
> If using HDP 2.2 Stack, you must get the cluster hosts to advertise the
> "current version". This can be done by restarting a master or slave component
> (such as a DataNode) on each host to have the host advertise it's version so
> Ambari can record the version. For example, in Ambari Web, navigate to the
> Hosts page and select any Host that has the DataNode component, then restart
> that DataNode component on that single host.
> Actually, we should relax it even more, because some hosts may only have
> client components. So either,
> A. All hosts with at least one master/slave must have at least one component
> advertise the version.
> This means that hosts with only clients don't need to do anything; and if a
> host has say NameNode and DataNode, only one is needed, but all such hosts
> need to advertise a version.
> B. Take the version of the first host to advertise a value. So only one
> component on one host is needed. This is the simplest thing to do, but we
> better not have clusters with a mix of versions, say 2.2.0.0-1 and
> 2.2.0.0-2B. Take the version of the first host to advertise a value. So only
> one component on one host is needed. This is the simplest thing to do, but we
> better not have clusters with a mix of versions, say 2.2.0.0-1 and 2.2.0.0-2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
