ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley" <jhur...@hortonworks.com>
Subject Re: Review Request 38220: [Preview] Stop-and-Start Upgrade: apply configs after all services have been stopped
Date Fri, 11 Sep 2015 14:51:24 GMT

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


Why is this change needed for stop-the-world? You've already stopped the hive server and prevented
clients from draining. You should not need to adjust the ports like we do for normal rolling
upgrades.

- Jonathan Hurley


On Sept. 9, 2015, 10:52 a.m., Dmitro Lisnichenko wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38220/
> -----------------------------------------------------------
> 
> (Updated Sept. 9, 2015, 10:52 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Dmytro Grinenko, Jonathan Hurley, and
Nate Cole.
> 
> 
> Bugs: AMBARI-13048
>     https://issues.apache.org/jira/browse/AMBARI-13048
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Goal:
> for STW Upgrade, we'll need to apply configs after all services have been stopped, and
before calling hdp-select set all.
> 
> I think, we have to add separate groups before and after restart of HIVE server to enforce
config application order during UPGRADE and DONGRADE. Looks like that is the only config change
required for 2.2->2.2+ upgrade. Does such upgrade pack definition look good?
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
01022b8 
> 
> Diff: https://reviews.apache.org/r/38220/diff/
> 
> 
> Testing
> -------
> 
> Preview
> 
> 
> Thanks,
> 
> Dmitro Lisnichenko
> 
>


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