Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 18 Aug 2017 07:48:00 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12986061.1467352903000.62528.1503042480684@Atlassian.JIRA>
In-Reply-To: <JIRA.12986061.1467352903000@Atlassian.JIRA>
References: <JIRA.12986061.1467352903000@Atlassian.JIRA> <JIRA.12986061.1467352903114@jira-lw-us.apache.org>
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: Fri, 18 Aug 2017 07:48:07 -0000


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

Rohith Sharma K S commented on YARN-5304:
-----------------------------------------

Hi [~vrushalic] Is this merge blocker? I see this as improvement, so could we remove label?

> 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-atsv2-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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org