ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower" <tbeerbo...@hortonworks.com>
Subject Re: Review Request 35140: 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.
Date Thu, 11 Jun 2015 20:13:40 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35140/#review87620
-----------------------------------------------------------

Ship it!


Ship It!

- Tom Beerbower


On June 9, 2015, 2:01 p.m., Dmitro Lisnichenko wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/35140/
> -----------------------------------------------------------
> 
> (Updated June 9, 2015, 2:01 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Sid Wagle, and Tom Beerbower.
> 
> 
> Bugs: AMBARI-11728
>     https://issues.apache.org/jira/browse/AMBARI-11728
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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. 
> 
> ---
> 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
> 
> ----
> I've moved a lot of agent refactor/cleanup to a separate 2.2 jira. Current jira contains
only critical server-side customizations.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java d5847fc

>   ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
8fdc160 
>   ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
ebee2e3 
> 
> Diff: https://reviews.apache.org/r/35140/diff/
> 
> 
> Testing
> -------
> 
> Checked on live clusters (bootstrap and RU)
> -
> -----------------------------------------------------------------------
> Total run:783
> Total errors:0
> Total failures:0
> OK
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views ...................................... SUCCESS [4.421s]
> [INFO] Ambari Metrics Common ............................. SUCCESS [2.462s]
> [INFO] Ambari Server ..................................... SUCCESS [46:56.613s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 47:04.240s
> [INFO] Finished at: Tue Jun 09 15:14:20 EEST 2015
> [INFO] Final Memory: 36M/303M
> [INFO] ------------------------------------------------------------------------
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message