[
https://issues.apache.org/jira/browse/HBASE-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167346#comment-17167346
]
Wellington Chevreuil commented on HBASE-24793:
----------------------------------------------
[~stack], how about change the code in hbck2 to use HBCKFsUtils.getRootDir?
Yeah, it would still require new release, but I think this would be a recurring
struggle unless we get rid of "IA Private" interfaces references in
operator-tools. We already had HBASE-24626, HBASE-24482 and HBASE-23791 on
similar problems, different classes.
I was already planning to work on removing references to FSUtils from
operator-tools, and put it into the list of forbidden apis similar to what we
done for MetaTableAccessor in HBASE-23934. Can do it as part of this jira, and
then we plan for a new operator tools release?
> [hbase-operator-tools] hbck2 filesystem fails against hbase-2.3.x
> -----------------------------------------------------------------
>
> Key: HBASE-24793
> URL: https://issues.apache.org/jira/browse/HBASE-24793
> Project: HBase
> Issue Type: Bug
> Components: hbck2
> Reporter: Michael Stack
> Priority: Major
>
> {code:java}
> 15:23:15.323 [main] INFO
> org.apache.hadoop.hbase.client.ConnectionImplementation - Closing master
> protocol: MasterService
> Exception in thread "main" java.lang.NoSuchMethodError:
> 'org.apache.hadoop.fs.Path
> org.apache.hadoop.hbase.util.FSUtils.getRootDir(org.apache.hadoop.conf.Configuration)'
> at org.apache.hbase.FileSystemFsck.<init>(FileSystemFsck.java:49)
> at org.apache.hbase.HBCK2.doCommandLine(HBCK2.java:720)
> at org.apache.hbase.HBCK2.run(HBCK2.java:631)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> at org.apache.hbase.HBCK2.main(HBCK2.java:865) {code}
>
> If build hbase-operator-tools against hbase-2.3.x its fine again. Could try
> putting pack the method in hbase-2.3.x or its probably worth a new release of
> hbase-operator-tools (last was 2018 for 1.0.0) but then it wouldn't work
> against 2.1 (but 2.1 is EOL'd so ok)? Probably wouldn't work against 2.2 then
> so maybe put back the method for 2.3?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
