[
https://issues.apache.org/jira/browse/MAPREDUCE-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981944#action_12981944
]
Todd Lipcon commented on MAPREDUCE-2265:
----------------------------------------
bq. But it is only useful for universal binary tarballs. For RPM's for
instance, you can just put the right one in to place
Sure, but then the RPM install and the tarball install would have a different
layout (or require the user to manually create the symlink to the correct
one... one extra step which is unnecessary)
Is there a particular objection to just having the arch directories with no
symlink, and using the same pattern for this as we already do for native? I
know it will require some changes to how the task controller resolves the conf
dir path, etc, but happy to make and test those.
> 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.
