[
https://issues.apache.org/jira/browse/YARN-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830743#comment-15830743
]
Vrushali C commented on YARN-5304:
----------------------------------
bq. If it is not too much, it would be great if we can add all the necessary
defaults as part of this JIRA. Let me know what you think.
I am not so sure that we can aim to cover "all necessary defaults" as part of
this jira. Some defaults can be added but for some it may be good to add them
after having run them for some time on our clusters. Let me know if you have
any specific setting suggestions (other than hfile one).
> 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: [email protected]
For additional commands, e-mail: [email protected]
