[
https://issues.apache.org/jira/browse/YARN-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234867#comment-17234867
]
Eric Badger commented on YARN-9561:
-----------------------------------
I think the short answer is that you need to have openssl-devel installed on
the machine where you are compiling Hadoop.
>From BUILDING.txt
{noformat}
160 * Use -Drequire.openssl to fail the build if libcrypto.so is not found.
161 If this option is not specified and the openssl library is missing,
162 we silently build a version of libhadoop.so that cannot make use of
163 openssl. This option is recommended if you plan on making use of openssl
164 and want to get more repeatable builds.
165 * Use -Dopenssl.prefix to specify a nonstandard location for the libcrypto
166 header files and library files. You do not need this option if you have
167 installed openssl using a package manager.
168 * Use -Dopenssl.lib to specify a nonstandard location for the libcrypto
library
169 files. Similarly to openssl.prefix, you do not need this option if you
have
170 installed openssl using a package manager.
171 * Use -Dbundle.openssl to copy the contents of the openssl.lib directory
into
172 the final tar file. This option requires that -Dopenssl.lib is also
given,
173 and it ignores the -Dopenssl.prefix option. If -Dopenssl.lib isn't
given, the
174 bundling and building will fail.
{noformat}
The crypto library is statically linked to the container-executor during
compilation. I guess it just quietly moves on if it doesn't find it instead of
failing. That's sort of troubling and something I'll look into fixing. But the
answer is to make sure openssl-devel is installed before you compile Hadoop
> Add C changes for the new RuncContainerRuntime
> ----------------------------------------------
>
> Key: YARN-9561
> URL: https://issues.apache.org/jira/browse/YARN-9561
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: YARN-9561.001.patch, YARN-9561.002.patch,
> YARN-9561.003.patch, YARN-9561.004.patch, YARN-9561.005.patch,
> YARN-9561.006.patch, YARN-9561.007.patch, YARN-9561.008.patch,
> YARN-9561.009.patch, YARN-9561.010.patch, YARN-9561.011.patch,
> YARN-9561.012.patch, YARN-9561.013.patch, YARN-9561.014.patch,
> YARN-9561.015.patch
>
>
> This JIRA will be used to add the C changes to the container-executor native
> binary that are necessary for the new RuncContainerRuntime. There should be
> no changes to existing code paths.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
