ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishal Suvagia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21256) As part of START_ALL of services Ranger kms starts after hbase and hive causing operation failure
Date Fri, 23 Jun 2017 13:08:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vishal Suvagia updated AMBARI-21256:
------------------------------------
    Attachment: AMBARI-21256_branch-2.5.patch
                AMBARI-21256_trunk.patch

> As part of START_ALL of services Ranger kms starts after hbase and hive causing operation
failure
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21256
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21256
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Vishal Suvagia
>            Assignee: Vishal Suvagia
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21256_branch-2.5.patch, AMBARI-21256_trunk.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message