Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 12 Jan 2017 02:12:16 +0000 (UTC)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12986061.1467352903000.3546.1484187136942@Atlassian.JIRA>
In-Reply-To: <JIRA.12986061.1467352903000@Atlassian.JIRA>
References: <JIRA.12986061.1467352903000@Atlassian.JIRA> <JIRA.12986061.1467352903114@arcas>
Subject: [jira] [Commented] (YARN-5304) Ship single node HBase config option
 with single startup command
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 12 Jan 2017 02:12:18 -0000


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

Sangjin Lee commented on YARN-5304:
-----------------------------------

Thanks for the summary [~vrushalic]. It is a good summary of the discussion.

Just to add a couple of more fine points,
- we would package this timeline service specific hbase configuration file in hadoop
- this file would now be required to be present; that would also entail making {{TIMELINE_SERVICE_HBASE_CONFIGURATION_FILE}} a required config and the file it points to required, or {{HBaseTimelineStorageUtils.getTimelineServiceHBaseConf()}} should fail
- bringing up hbase would require using this config file via the {{--config}} option (i.e. {{"hbase --config ...}})

> 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
>              Labels: YARN-5355, yarn-5355-merge-blocker
>
> 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
(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