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

Gabor Bota commented on HADOOP-15960:
-------------------------------------

h2. Hadoop results

First test results are on this commit: [commit with test results 
|https://github.com/apache/hadoop/commit/157127e01e35a99b8578e40cb314d3bc0cab897a]
 
 * There were some test failures - but those seem unrelated because of local 
rerun of those tests were successful
 * There were new deprecations - those were addressed with my [updated pull 
request|https://github.com/apache/hadoop/commit/5bb98f60ade6deb5a40033f3cb127901e4837b0a].
 There was one instance that was not trivial and I wanted to trigger a new run 
so I have tests results.
 * The test timed out on Friday after 5 hours: 
[https://builds.apache.org/job/hadoop-multibranch/job/PR-637/]. [~jojochuang] 
helped me with retriggering the test run.

h2. Testing with HBase
 * Since there were no compile and test errors with this build I tried to run 
the HBase tests with a Hadoop build that contains my patch.
 * I tried to run this with HBase/master branch and Hadoop/trunk, but I ran 
into incompatibilities with those versions:
 ** I had issues with the licensing and shading. Fixed both issues temporary 
with bypassing {{check-aggregate-license}} and 
{{hbase-shaded-check-invariants}} for now, but those issues have to be fixed in 
the future in a way the project can accept. These issues are not just because 
of my patch, although updating guava brings even more shadowing issues.
 ** Lot of tests were failing because of something like
{noformat}
 Caused by: java.lang.RuntimeException: Master not initialized after 
200000ms{noformat}
If you look at the surefire logs it turns out that the cause of this is 
something like this:
{noformat}
java.lang.NoSuchMethodException: 
org.apache.hadoop.hdfs.protocol.ClientProtocol.create(java.lang.String, 
org.apache.hadoop.fs.permission.FsPermission, java.lang.String, 
org.apache.hadoop.io.EnumSetWritable, boolean, short, long, 
[Lorg.apache.hadoop.crypto.CryptoProtocolVersion;){noformat}
So we try to get a method which is not there - the method signature has changed 
in hadoop trunk, so it should be updated in hbase.

To test HBase against this guava update I have to fall back to a Hadoop version 
which is tested and supported by HBase. I will backport my commit to the 
branch-3.0.3 to have a stable base with a successful test run.

Meanwhile, I will fix the issues in my patch what is targeted to hadoop trunk 
branch.

> Update guava to 27.0-jre in hadoop-common
> -----------------------------------------
>
>                 Key: HADOOP-15960
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15960
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: common, security
>    Affects Versions: 3.1.0, 3.3.0
>            Reporter: Gabor Bota
>            Assignee: Gabor Bota
>            Priority: Critical
>         Attachments: HADOOP-15960.000.WIP.patch
>
>
> com.google.guava:guava should be upgraded to 27.0-jre due to new CVE's found 
> [CVE-2018-10237|https://nvd.nist.gov/vuln/detail/CVE-2018-10237].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to