[
https://issues.apache.org/jira/browse/BIGTOP-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581043#comment-13581043
]
Bruno Mahé edited comment on BIGTOP-637 at 2/19/13 6:12 AM:
------------------------------------------------------------
So here is the first pass of my take on this ticket (file
0001-BIGTOP-637.-Update-boxgrinder-appliance-for-the-comi.patch from 18/Feb/13
22:09)
I went the way I outlined a few comments ago, meaning I reused the script Mark
contributed in BIGTOP-547 and wrapped it into an init script which is ran
between HDFS and YARN daemons at start up.
And this works great.
But I also note the following:
* BIGTOP-547 was not checked in. So in order to get stuff done, this is
included for now by boxgrinder. But I would like to sort out its situation so
we can check this in and reuse it directly from the packages
* BIGTOP-547 has a few issues. The first one being its use of sudo, which
requires a login shell. Unfortunately login shells are not available from init
scripts. So I had to replace sudo by su. This should be included in BIGTOP-547
* Another issue of BIGTOP-547 is that even after running it, I could not run a
simple pi job as root. It would complain /tmp/hadoop-yarn (something like that)
is not accessible by root. Although jobs run fine as the user hdfs. So
BIGTOP-547 probably need some tweaks to work
* I had to adjust yarn daemon's priorities. They are set by default as the same
as the HDFS ones. Which should also adjust them directly in the packages.
* Somehow I found some yarn/mapreduce initscripts with typo into /etc/init.d
and not belonging to any package (ex:
/etc/init.d/hadoop-mapreduce-historyservere)
* Also, BIGTOP-547 is pretty slow. Not sure we can do anything about it, but it
would be great if we could find a way to speed it up.
So would this approach resolve everyone's concerns?
was (Author: bmahe):
So here is the first pass of my take on this ticket (file
0001-BIGTOP-637.-Update-boxgrinder-appliance-for-the-comi.patch from 18/Feb/13
22:09)
I went the way I outlined a few comments ago, meaning I reused the script Mark
contributed in BIGTOP-547 and wrapped it into an init script which is ran
between HDFS and YARN daemons at start up.
And this works great.
But I also note the following:
* BIGTOP-547 was not checked in. So in order to get stuff done, this is
included for now by boxgrinder. But I would like to sort out its situation so
we can check this in and reuse it directly from the packages
* BIGTOP-547 has a few issues. The first one being its use of sudo, which
requires a login shell. Unfortunately login shells are not available from init
scripts. So I had to replace sudo by su. This should be included in BIGTOP-547
* Another issue of BIGTOP-547 is that even after running it, I could not run a
simple pi job as root. It would complain /tmp/hadoop-yarn (something like that)
is not accessible by root. Although jobs run fine as the user hdfs. So
BIGTOP-547 probably need some tweaks to work
* I had to adjust yarn daemon's priorities. They are set by default as the same
as the HDFS ones. Which should also adjust them directly in the packages.
* Somehow I found some yarn/mapreduce initscripts with typo into /etc/init.d
and not belonging to any package (ex:
/etc/init.d/hadoop-mapreduce-historyservere)
So would this approach resolve everyone's concerns?
> 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:
> 0001-BIGTOP-637.-Update-boxgrinder-appliance-for-the-comi.patch,
> BIGTOP-637-2.patch.txt, 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
