You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Haibo Chen (JIRA)" <ji...@apache.org> on 2016/09/26 03:31:20 UTC
[jira] [Updated] (YARN-5667) Move HBase backend code in ATS v2
into its separate module
[ https://issues.apache.org/jira/browse/YARN-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Haibo Chen updated YARN-5667:
-----------------------------
Description:
The HBase backend code currently lives along with the core ATS v2 code in hadoop-yarn-server-timelineservice module. Because Resource Manager depends on hadoop-yarn-server-timelineservice, an unnecessary dependency of the RM module on HBase modules is introduced (HBase backend is pluggable, so we do not need to directly pull in HBase jars).
In our internal effort to try ATS v2 with HBase 2.0 which depends on Hadoop 3, we encountered a circular dependency during our builds between HBase2.0 and Hadoop3 artifacts.
{code}
hadoop-mapreduce-client-common, hadoop-yarn-client, hadoop-yarn-server-resourcemanager, hadoop-yarn-server-timelineservice, hbase-server, hbase-prefix-tree, hbase-hadoop2-compat, hadoop-mapreduce-client-jobclient, hadoop-mapreduce-client-common]
{code}
This jira proposes we move all HBase-backend-related code from hadoop-yarn-server-timelineservice into its own module (possible name is yarn-server-timelineservice-storage) so that core RM modules do not depend on HBase modules any more.
was:
The HBase backend code currently lives along with the core ATS v2 code in hadoop-yarn-server-timelineservice module. Because Resource Manager depends on hadoop-yarn-server-timelineservice, an unnecessary dependency of the RM module on HBase modules is introduced (HBase backend is pluggable, so we do not need to directly pull in HBase jars).
In our internal effort to try ATS v2 with HBase 2.0 which depends on Hadoop 3, we encountered a circular dependency during our builds between HBase2.0 and Hadoop3 artifacts.
hadoop-mapreduce-client-common, hadoop-yarn-client, hadoop-yarn-server-resourcemanager, hadoop-yarn-server-timelineservice, hbase-server,
hbase-prefix-tree, hbase-hadoop2-compat, hadoop-mapreduce-client-jobclient, hadoop-mapreduce-client-common]
This jira proposes we move all HBase-backend-related code from hadoop-yarn-server-timelineservice into its own module (possible name is yarn-server-timelineservice-storage) so that core RM modules do not depend on HBase modules any more.
> Move HBase backend code in ATS v2 into its separate module
> -----------------------------------------------------------
>
> Key: YARN-5667
> URL: https://issues.apache.org/jira/browse/YARN-5667
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Haibo Chen
> Assignee: Haibo Chen
>
> The HBase backend code currently lives along with the core ATS v2 code in hadoop-yarn-server-timelineservice module. Because Resource Manager depends on hadoop-yarn-server-timelineservice, an unnecessary dependency of the RM module on HBase modules is introduced (HBase backend is pluggable, so we do not need to directly pull in HBase jars).
> In our internal effort to try ATS v2 with HBase 2.0 which depends on Hadoop 3, we encountered a circular dependency during our builds between HBase2.0 and Hadoop3 artifacts.
> {code}
> hadoop-mapreduce-client-common, hadoop-yarn-client, hadoop-yarn-server-resourcemanager, hadoop-yarn-server-timelineservice, hbase-server, hbase-prefix-tree, hbase-hadoop2-compat, hadoop-mapreduce-client-jobclient, hadoop-mapreduce-client-common]
> {code}
> This jira proposes we move all HBase-backend-related code from hadoop-yarn-server-timelineservice into its own module (possible name is yarn-server-timelineservice-storage) so that core RM modules do not depend on HBase modules any more.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org