Hi there! Want to give a heads-up to the work I'm doing: supporting Hadoop 3.3.0.
There are a few commits in the master branch: HBASE-22103 HBASE-23861 HBASE-23833 HBASE-23998 I plan to backport the 5 HBASE commits mentioned above to lower branches: branch-2, branch-2.3. Are there any concerns backporting them to branch-2.2? After these commits, the master branch can build against Hadoop 3.3.0-SNAPSHOT (a RC is about to be voted) with maven clean install -Dhadoop-three.version=3.3.0-SNAPSHOT -Djetty.version=9.4.20.v20190813 Note the jetty version must be updated too otherwise unit tests will fail due to classpath conflict. The build will be slightly easier after HBASE-23811 <https://issues.apache.org/jira/browse/HBASE-23811> and HBASE-23834 <https://issues.apache.org/jira/browse/HBASE-23834> when HBase uses jetty from hbase-thirdparty. JDK8 only. I am yet to test JDK11. I managed to run tests via mvn test, so this includes SmallTests and MediumTests. A few UTs failed but they failed even with Hadoop 3.1.2. So may be my local env issue. If you are interested, here's the list of failed UTs. (1) TestDelegationTokenWithEncryption,TestGenerateDelegationToken --> It appears to be a bug in delegation token. reproducible with Hadoop 3.1.2 too in master branch. (2) TestZooKeeper.testMasterZKSessionRecoveryFailure --> not clear why but reproducible with Hadoop 3.1.2 in master branch. (3) TestSyncTimeRangeTracker.testConcurrentIncludeTimestampCorrectness --> OOM. Passed after increasing heap size. (4) TestRegionServerHostname.testRegionServerHostname --> multi-home. It failed on my virtualbox interface. appears to be a local env issue. (5) TestAlwaysStandByHMaster.testAlwaysStandBy --> reproducible in branch-2.3 but not in branch-2.2. passed if I increase timeout. I will file jiras for these test failures.
