hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haibo Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5667) Move HBase backend code in ATS v2 into its separate module
Date Thu, 06 Oct 2016 00:38:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550424#comment-15550424

Haibo Chen commented on YARN-5667:

Thanks for your quick reviews [~vrushalic]. I did not change the hbase version, so I believe
I must have been testing against hbase 1.1.3. In terms of testing done, I enabled coprocessor
in my hbase cluster and ATS v2 in my yarn cluster, ran a few mapreduce example jobs, and then
verified the reader through a few flow and application-level REST requests. Everthing seems
to have worked for me. I could see the metrics for a flow run as well (Is this what you mean
by " Did you recollect the counters aggregated to the flow level"?)

I will update with a layout of what the file structure is like before and after my change.

> 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
>         Attachments: part1.yarn5667.prelim.patch, part2.yarn5667.prelim.patch, part3.yarn5667.prelim.patch,
part4.yarn5667.prelim.patch, part5.yarn5667.prelim.patch
> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message