[
https://issues.apache.org/jira/browse/KYLIN-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yerui Sun updated KYLIN-1910:
-----------------------------
Attachment: KYLIN-1910.patch
Patch attached. More details can be found in
http://kylin.apache.org/blog/2016/06/10/standalone-hbase-cluster/
> Support Separate HBase Cluster with NN HA and Kerberos Authentication
> ---------------------------------------------------------------------
>
> Key: KYLIN-1910
> URL: https://issues.apache.org/jira/browse/KYLIN-1910
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
> Affects Versions: v1.5.3
> Reporter: Yerui Sun
> Assignee: Yerui Sun
> Attachments: KYLIN-1910.patch
>
>
> Since KYLIN-957, we've support separate hbase cluster deployment. However, it
> didn't support hbase cluster with NameNode HA and Kerberos Authentication
> perfectly.
> The key point is the cube building MR job need to access two hdfs cluster,
> the main cluster stored source data and the hbase cluster stored the cube
> result data. The MR task couldn't access hbase cluster with HA qualified
> path, like hdfs://hbase-cluster:8020/path, because that couldn't found
> dfs.nameservices related configs of hbase cluster.
> To solve this problem, we need to read the hbase cluster HA configs and set
> into job conf.
> Another point is about authentication tokens. During job submitting, the
> Resource Manager try to renew all tokens, to ensure can keep tokens alive.
> The hdfs token of hbase cluster renewing would cause exception, because that
> RM couldn't found the hbase cluster HA configs.
> This problem can be resolved with YARN-3021 support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
