[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981947#action_12981947
 ] 

Owen O'Malley commented on MAPREDUCE-2265:
------------------------------------------

I want a consistent layout between tarballs and RPMs.

I don't want to include the platform name simply because then all of the 
scripts need to consistently figure out the platform name. If we can have the 
resolution done once at install time, that is much less cumbersome. It will 
also leak into bin and lib.

For universal tar balls, I think that a post-untar setup script makes the most 
sense. I guess you could also have different hadoop home directories in the 
tarball with symlinks between them.

> task-controller and jsvc should install into sbin/<platform>/ directory
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2265
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2265
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: build, task-controller, tasktracker
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>
>
> Currently the task-controller and jsvc "live" in the bin/ directory 
> regardless of build platform. This is incorrect since these components are 
> native compiled code and thus are built for a particular architecture. So, 
> when we ship a build of 22, we will want to ship both 32-bit and 64-bit 
> artifacts so users can use these components without rebuilding on their own.
> Additionally, it doesn't make sense for them to be in bin/ since they're not 
> user-facing in any way (i.e a user would never directly invoke them). So I 
> would propose putting them in an sbin directory.
> The final proposed path is $HADOOP_HOME/sbin/<platform>/{jsvc,task-controller}
> Note this is not an incompatible change since these components were not 
> present in any prior apache release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to