[
https://issues.apache.org/jira/browse/BIGTOP-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580455#comment-13580455
]
Konstantin Boudnik commented on BIGTOP-637:
-------------------------------------------
bq. and with the script in the same directory than the appliance definition
file.
As I said in my comment: boxgrinder preserves the hierarchy. Thus you will have
to put {{start-mr.sh}} into the top directory of the workspace, instead of
{{bigtop-deploy/vm/boxgrinder}}
bq. A script with a higher priority than the Apache Hadoop daemons
The script you're referring to would have to start in the middle of Hadoop
startup sequence. Checking HDFS structures requires _live_ namenode.
bq. Well, this appliance only provides Apache Hadoop right now. So I am not
sure for what a user would use it if not using Apache Hadoop
I am not talking about "other uses". I am talking about bringing 6 HDFS + YARN
daemons in say 2 GB and then trying to run almost anything on such a cluster.
This is dreadful to say the least.
As for the reference to Cloudera VM: this is exactly what I am referring to. It
is literally painful to watch how nothing can get started in this thing. It
crawls on all four.
At any rate - if you see the better way to do this patch: go ahead and do it
the way you want to. I did it the way I think is the best from UX and
maintenance stand points.
> Update boxgrinder appliance for the coming release
> --------------------------------------------------
>
> Key: BIGTOP-637
> URL: https://issues.apache.org/jira/browse/BIGTOP-637
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Bruno Mahé
> Assignee: Konstantin Boudnik
> Fix For: 0.6.0
>
> Attachments: BIGTOP-637.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
