[
https://issues.apache.org/jira/browse/YARN-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792922#comment-16792922
]
Prabhu Joseph commented on YARN-9388:
-------------------------------------
The document {{TimelineServiceV2.md}} has to be updated with below information
else users will hit the above issue on using custom table names.
The {{hbase-site.xml}} specified at
{{yarn.timeline-service.hbase.configuration.file}} has to be specified with
below custom table names and restart Yarn Services NodeManager, ResourceManager
and TimelineReader.
{code}
yarn.timeline-service.app-flow.table.name
yarn.timeline-service.entity.table.name
yarn.timeline-service.application.table.name
yarn.timeline-service.subapplication.table.name
yarn.timeline-service.flowactivity.table.name
yarn.timeline-service.flowrun.table.name
yarn.timeline-service.domain.table.name
{code}
> HBaseTimelineSchemaCreator skipExistingTable should honor custom hbase
> tablenames
> ---------------------------------------------------------------------------------
>
> Key: YARN-9388
> URL: https://issues.apache.org/jira/browse/YARN-9388
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: ATSv2
> Affects Versions: 3.2.0, 3.1.2, 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
>
> HBaseTimelineSchemaCreator provides option to configure custom table names
> for timelineservice tables. The option skipExistingTable ignores the tables
> already created with custom tablenames and recreates the tables with default
> table names. The custom table names has to be persisted so that
> skipExistingTable, HBaseTimelineWriterImpl, HBaseTimelineReaderImpl can use
> this. It currently expects to pass all custom table names every time
> TimelineSchemaCreator is used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
