You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/04/23 17:59:15 UTC
[jira] [Comment Edited] (BIGTOP-1235) Combine BIGTOP-1200 and
BIGTOP-952 with a few minor shell commands that will entirely replace
init-hdfs.sh
[ https://issues.apache.org/jira/browse/BIGTOP-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978352#comment-13978352 ]
jay vyas edited comment on BIGTOP-1235 at 4/23/14 3:57 PM:
-----------------------------------------------------------
Updated task list from mailing list:
- Update puppet provisioners
- Determine what path the provision.groovy script is written to in the real clusters `(/usr/lib/bigtop-utils/)` or somethhing like that?
- Make sure that groovy is indeed available at setup time .
- Test it all by provisioning a hadoop system from scratch, without init-hdfs.sh
- delete init-hdfs.sh
- rename provision.groovy to init-hcfs.groovy
- verify usage of "HCFS_SUPER_USER" parameter so that permissions can different depending on root_user value. the init-hcfs.json file which bigtop ships with needs to go through another round of validation.
was (Author: jayunit100):
Updated task list from mailing list:
Update puppet provisioners
Determine what path the provision.groovy script is written to in the real clusters `(/usr/lib/bigtop-utils/)` or somethhing like that?
Make sure that groovy is indeed available at setup time .
Test it all by provisioning a hadoop system from scratch, without init-hdfs.sh
delete init-hdfs.sh
rename provision.groovy to init-hcfs.groovy
verify usage of "HCFS_SUPER_USER" parameter so that permissions can different depending on root_user value. the init-hcfs.json file which bigtop ships with needs to go through another round of validation.
> Combine BIGTOP-1200 and BIGTOP-952 with a few minor shell commands that will entirely replace init-hdfs.sh
> -----------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1235
> URL: https://issues.apache.org/jira/browse/BIGTOP-1235
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.7.0
> Reporter: jay vyas
> Assignee: jay vyas
> Fix For: 0.8.0
>
>
> BIGTOP-1200 provides file schema in JSON format, for any HCFS related tool to read.
> BIGTOP-952 meanwhile give us fast provisioning by running in a single JVM (without multiple haoop fs -... commands_).
> Thus, when those two are finished, we can replace init-hdfs.sh (with the exception of a few extra shell commands in bottom of that script which still will need to be called).
> So this JIRA will:
> - create a new init-hcfs.groovy script which calls provision.groovy in BIGTOP-952, with init-hcfs.json as input.
> - add in the remaining straggler commands from init-hdfs.sh which dont fit into the generic json format as shell commands.
> - delete init-hdfs.sh entirely
> - update puppet scripts to use init-hcfs.groovy, calling them with the "hdfs" argument.
--
This message was sent by Atlassian JIRA
(v6.2#6252)