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




ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/role_command_order.json
Lines 2 (patched)
<https://reviews.apache.org/r/60388/#comment253250>

    This file is also needed for HBase in 3.0


- Alejandro Fernandez


On June 23, 2017, 1:13 p.m., Vishal Suvagia wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60388/
> -----------------------------------------------------------
> 
> (Updated June 23, 2017, 1:13 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Gautam Borad, Jayush Luniya, 
> Mugdha Varadkar, Sumit Mohanty, and Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-21256
>     https://issues.apache.org/jira/browse/AMBARI-21256
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> As part of START_ALL of services Ranger-KMS starts after Hbase and Hive 
> causing their start failure.
> In an encrypted cluster where TDE is on, Hbase service seems to be dependent 
> on the Ranger-KMS service, but for a start-all services action Hbase service 
> starts before Ranger-KMS.
> So Hbase master goes down while connecting to KMS, since at the time of Hbase 
> start KMS is down , connection to KMS fails, and Hbase-Master fails to become 
> active.
> This in-turn causes Atlas service start failure which actually depends on 
> HBase and start_all flow fails for HBASE and HIVE.
> 
> Attached patch is for branch-2.5, addendum trunk patch is attached to Apache 
> JIRA.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/role_command_order.json
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/60388/diff/1/
> 
> 
> Testing
> -------
> 
> Verified with installation on Cent-OS 6.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>

Reply via email to