[GitHub] [hbase-filesystem] wchevreuil commented on pull request #15: HBASE-24963 [HBOSS] UTs failing when running against hadoop 3.3.
wchevreuil commented on pull request #15: URL: https://github.com/apache/hbase-filesystem/pull/15#issuecomment-685954468 Had pushed a new commit, with a change to EmbeddedZK to make sure it works with hbase versions including HBASE-23993 (like 2.3.1), for example. As mentioned on my previous comments, testing against hbase 2.3.1 works as long as ZK version specified is 3.5.7: `mvn clean install -Dhadoop.profile=3 -Dhadoop3.version=3.3.0 -Dhbase.profile=2 -Dhbase2.version=2.3.1 -Dzookeeper.version=3.5.7` @apurtell @joshelser , mind give it another try? I was thinking maybe worth raise these dependency versions on another jira? 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
[GitHub] [hbase-filesystem] wchevreuil commented on pull request #15: HBASE-24963 [HBOSS] UTs failing when running against hadoop 3.3.
wchevreuil commented on pull request #15: URL: https://github.com/apache/hbase-filesystem/pull/15#issuecomment-685894894 Right, so here some findings: 1) Setting hbase version to 2.3.1 requires updating ZK version in hboss to 3.5.7, otherwise, we get the NCDFE already mentioned above. 2) Additional adjustment is required in EmbeddedZK class to use loopback address, instead of localhost, per the changes in MiniZooKeeperCluster by HBASE-23993. 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
[GitHub] [hbase-filesystem] wchevreuil commented on pull request #15: HBASE-24963 [HBOSS] UTs failing when running against hadoop 3.3.
wchevreuil commented on pull request #15: URL: https://github.com/apache/hbase-filesystem/pull/15#issuecomment-685047520 >When I compile a custom stack based on Hadoop 3.3.0, HBase 2.3.1, and ZooKeeper 3.5.8, such that all of Hadoop, HBase, and ZK versions are harmonized across those components (meaning: Hadoop is built with ZK 3.5.8, HBase is built with Hadoop 3.3.0 hadoop.profile=3.0 and ZK 3.5.8), I still see the ZK related runtime link errors. (NoClassDefFoundError: org/apache/zookeeper/common/X509Exception$SSLContextException) Looked further into this, so the real issue is the NCDFE mentioned by @apurtell earlier. Yeah, hboss is defining a ZK dependency on version `3.4.10`, whilst HBase 2.3.1 is on `3.5.7`. 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
[GitHub] [hbase-filesystem] wchevreuil commented on pull request #15: HBASE-24963 [HBOSS] UTs failing when running against hadoop 3.3.
wchevreuil commented on pull request #15: URL: https://github.com/apache/hbase-filesystem/pull/15#issuecomment-684754172 "Strangerthings here": 1) >I see this when running locally mvn clean verify -Dhadoop.profile=3 -Dhadoop3.version=3.3.0 Tried it locally. First run got same error, but subsequent runs succeeded. 2) > When I compile a custom stack based on Hadoop 3.3.0, HBase 2.3.1, and ZooKeeper 3.5.8, such that all of Hadoop, HBase, and ZK versions are harmonized across those components (meaning: Hadoop is built with ZK 3.5.8, HBase is built with Hadoop 3.3.0 hadoop.profile=3.0 and ZK 3.5.8), I still see the ZK related runtime link errors. (NoClassDefFoundError: org/apache/zookeeper/common/X509Exception$SSLContextException) Got same result. Among the test errors, saw this ` The value of property fs.hboss.sync.zk.connectionString must not be null` message, which makes me suspect the hbase profile specified is missing some properties definition. Looking further into this, will reply later. 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
