virajjasani commented on pull request #2932: URL: https://github.com/apache/hadoop/pull/2932#issuecomment-824987122
> The reason we use wildfly in the azure and -aws JARs is for performance by picking up those native bindings. if you use wildfly ssl as your socket factory, when openssl binaries are on PATH, then it will be used. > If this change takes that feature away, it's a regression which will hurt performance. Yes, that use of openssl has been brittle in the past, but it is stable now between our wildfly version and openssl 1.1.1 Thanks for the detailed info @steveloughran. It looks wildfly-openssl has more usecases to serve than what I thought of earlier. Do we have any specific tests (or is it even possible to write tests) that validates using openssl binaries available in PATH while using wildfly ssl as socket factory? Perhaps this might be very complicated scenario to test? > What does this repackaging mean in terms of integration with openssl? I afraid I might not have good knowledge here, I was merely relying on unit tests run by QA. For the above mentioned feature, could you please share any doc if you have? Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
