hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-4603) Installation on Solaris needs additional PATH setting
Date Tue, 03 Jan 2012 03:34:21 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178610#comment-13178610

Allen Wittenauer commented on HADOOP-4603:

This is essentially fixed by using the native libraries in newer releases of Hadoop.  The
problem is that the native code is completely non-portable and the committer community has
shown no real desire to make that code portable.  I don't believe we should encourage folks
to run without the native code because the performance is likely to be seriously horrendous.
 (My anecdotal experience says the NN in 0.20.20x is 10-15% slower compared to 0.20.2).

At this point, I'd close this as won't fix, just like I did all of my portability JIRAs (including
some with patches).  I think pretending that we care about portability is sort of silly at
this point when it has been demonstrated over and over that we don't.
> Installation on Solaris needs additional PATH setting
> -----------------------------------------------------
>                 Key: HADOOP-4603
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4603
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.18.2
>         Environment: Solaris 10 x86
>            Reporter: Jon Brisbin
>         Attachments: HADOOP-4603, id_instead_of_whoami.diff
> A default installation as outlined in the docs won't start on Solaris 10 x86. The "whoami"
utility is in path "/usr/ucb" on Solaris 10, which isn't in the standard PATH environment
variable unless the user has added that specifically. The documentation should reflect this.
> Solaris 10 also seemed to throw NPEs if you didn't explicitly set the IP address to bind
the servers to. Simply overriding the IP address fixes the problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message