[
https://issues.apache.org/jira/browse/BIGTOP-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920438#comment-13920438
]
jay vyas commented on BIGTOP-952:
---------------------------------
Hi cos: some questions before i resubmit. FYI the formatting should be much
better this time since now i have a dev setup that does hadoop style formatting
properly.
- okay ill move it to bigtop-utils and yes there is definetly some more cleanup
i can do .
- i think it can be a script : i can add the groovy shebang.
Now a question for you:
- the manual classpath setting is just an example of how to invoke. how do you
feel if we wait to decide on the exact right way we invoke for provisioning
later on, in BIGTOP-1235 ? Ive intentionally created that JIRA so that we can
get this functional utility as a first pass , and then refine it with a more
global view of the system later.
> 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: jay vyas
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: BIGTOP-952-tested-refined.patch,
> BIGTOP-952-tested.patch, provision2.groovy, 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.2#6252)
