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 "Rohith Sharma K S (Jira)" <ji...@apache.org> on 2019/08/30 05:52:00 UTC
[jira] [Resolved] (YARN-5304) Ship single node HBase config option
with single startup command
[ https://issues.apache.org/jira/browse/YARN-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S resolved YARN-5304.
-------------------------------------
Resolution: Won't Fix
In ATSv2 weekly call, discussed for cleaning up JIRA which are not going implement. Hence, closing the JIRA as Won't Fix. Feel free to reopen if still same design approach exists.
> Ship single node HBase config option with single startup command
> ----------------------------------------------------------------
>
> Key: YARN-5304
> URL: https://issues.apache.org/jira/browse/YARN-5304
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Joep Rottinghuis
> Assignee: Vrushali C
> Priority: Major
> Labels: YARN-5355
>
> For small to medium Hadoop deployments we should make it dead-simple to use the timeline service v2. We should have a single command to launch and stop the timelineservice back-end for the default HBase implementation.
> A default config with all the values should be packaged that launches all the needed daemons (on the RM node) with a single command with all the recommended settings.
> Having a timeline admin command, perhaps an init command might be needed, or perhaps the timeline service can even auto-detect that and create tables, deploy needed coprocessors etc.
> The overall purpose is to ensure nobody needs to be an HBase expert to get this going. For those cluster operators with HBase experience, they can choose their own more sophisticated deployment.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org