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

jay vyas edited comment on BIGTOP-952 at 3/10/14 9:35 PM:
----------------------------------------------------------

- yup ill remove the printlns .
- and, wrt API calls: they could be faster but I ran into issues doing 
recursive copies using the direct copyFromLocal API .  not sure where the logic 
is for recursive/glob copying.  will have to look maybe in FsShell and see how 
it uses the API from globs.  not too hard to do.

Are those the only issues you see?  If so ill clean all this up , test it, and 
proabbly put the patch in by the middle of this week !


was (Author: jayunit100):
- yup ill remove the printlns .
- and, wrt API calls: they could be faster but I ran into issues doing the 
copyFromLocal API .  I can try to look some more into it.

Are those the only issues you see?  If so ill clean all this up , test it, and 
proabbly put the patch in by the middle of this week !

> 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)

Reply via email to