Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 29 Sep 2016 17:39:21 +0000 (UTC)
From: "Vrushali C (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13007476.1474860540000.699659.1475170761480@Atlassian.JIRA>
In-Reply-To: <JIRA.13007476.1474860540000@Atlassian.JIRA>
References: <JIRA.13007476.1474860540000@Atlassian.JIRA> <JIRA.13007476.1474860540562@arcas>
Subject: [jira] [Commented] (YARN-5667) Move HBase backend code in ATS v2
  into its separate module
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Sep 2016 17:40:14 -0000


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

Vrushali C commented on YARN-5667:
----------------------------------

Yes, we are considering moving the coprocessor related code into a separate package in YARN-4985 (not much progress there yet).

I am also considering moving the coprocessor related functionality (ie aggregation) into hbase itself. That way ATS v2 can invoke this aggregation via hbase api calls which might make the dependency dags "easier" to manage. But that remains TBD, so till then we should proceed with moving the coproc related code into a separate package.

> 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