[
https://issues.apache.org/jira/browse/YARN-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vrushali C updated YARN-6094:
-----------------------------
Attachment: YARN-6094.001.patch
Uploading patch v001.
The changes that the patch introduces are:
- documentation updates to reflect that this is now a dynamically loaded table
level coprocessor (hence no restart of Region servers needed, nor any additions
of coprocessor class name in hbase-site.xml)
- in FlowRunCoprocessor, the check for isFlowRunRegion is no longer needed
since this coprocessor is only enabled for one table - the flow run table.
- Yarn config now has a new parameter that helps set the location on hdfs for
the coprocessor jar
- unit test changes. Notable change is for createSchema function that has been
added to DataGeneratorForTest. This function now creates the timeline service
schema for the unit tests. It copies the jar to hdfs on the minicluster during
the test execution and then creates the tables.
- Some of the other changes in unit test file DataGeneratorForTest are for
fixing the checkstyle warning of function length > 150.
> Update the coprocessor to be a dynamically loaded one
> -----------------------------------------------------
>
> Key: YARN-6094
> URL: https://issues.apache.org/jira/browse/YARN-6094
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Vrushali C
> Attachments: YARN-6094.001.patch
>
>
> The timeline service v2 code base on yarn now uses hbase 1.2.4 after
> YARN-5976.
> With this version of hbase, system classes (starting with org.apache.hadoop)
> can be loaded as table level coprocessors. Hence we should update the
> timeline service coprocessor to be a dynamically loaded one instead of static
> loading.
> This involves code changes as well as documentation updates for deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
