[
https://issues.apache.org/jira/browse/BIGTOP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917115#comment-13917115
]
jay vyas edited comment on BIGTOP-952 at 3/1/14 4:41 PM:
---------------------------------------------------------
thanks cos, will do.
is it Okay if we keep this JIRA as a pure groovy file system provisioning one,
and
- leave out the oozie stuff that init-hdfs.sh still contains?
- avoid deleting init-hdfs.sh,for now, as refactoring deployment is really a
separate task.
Then we can tie it all together in a separate JIRA which i think we should very
carefully inject into the code base (as it will completely change bigtop
deployment BIGTOP-1235).
was (Author: jayunit100):
thanks cos, will do. Okay
if we keep this JIRA as a pure groovy file system provisioning one, and leave
out the oozie stuff that init-hdfs.sh still contains?
Then we can tie it all together in a separate JIRA which i think we should very
carefully inject into the code base (as it will completely change bigtop
deployment BIGTOP-1235).
> init-hdfs.sh is dog slow. Let's replace it with a single VM call and better
> layout management
> ---------------------------------------------------------------------------------------------
>
> Key: BIGTOP-952
> URL: https://issues.apache.org/jira/browse/BIGTOP-952
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.5.0
> Reporter: Konstantin Boudnik
> Assignee: Roman Shaposhnik
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: untar.groovy
>
>
> As has been proposed in [this
> patch|https://issues.apache.org/jira/secure/attachment/12575644/untarHdfs.groovy]
> by [~rvs] there's a very efficient way of creating layout in HDFS using a
> tarfile and Groovy script with direct call into DFS APIs.
> Let's making it happen.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
