[
https://issues.apache.org/jira/browse/HBASE-27595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681361#comment-17681361
]
Duo Zhang commented on HBASE-27595:
-----------------------------------
{quote}
Then I think we can just simply distinguish the exceptions, use debug to output
NoSuchFieldException and clarify that it should be caused by the Hadoop version.
Is it ok?
{quote}
I think it is OK.
> ThreadGroup is removed since Hadoop 3.2.4
> -----------------------------------------
>
> Key: HBASE-27595
> URL: https://issues.apache.org/jira/browse/HBASE-27595
> Project: HBase
> Issue Type: Test
> Reporter: tianhang tang
> Assignee: tianhang tang
> Priority: Minor
>
> Found lots of WARNING in UT log:
> {code:java}
> 2023-01-26T05:26:18,869 WARN [FsDatasetAsyncDiskServiceFixer]
> hbase.HBaseTestingUtil$FsDatasetAsyncDiskServiceFixer(617): failed to reset
> thread pool timeout for FsDatasetAsyncDiskService
> java.lang.NoSuchFieldException: threadGroup
> at java.lang.Class.getDeclaredField(Class.java:2411) ~[?:?]
> at
> org.apache.hadoop.hbase.HBaseTestingUtil$FsDatasetAsyncDiskServiceFixer.run(HBaseTestingUtil.java:609)
> ~[test-classes/:?]
> {code}
> FsDatasetAsyncDiskServiceFixer is introduced by
> [HBASE-27148|https://issues.apache.org/jira/browse/HBASE-27148], to prevent
> unexpected kill.
> But Hadoop 3.2.4 has fixed this issue
> [HDFS-16586|https://issues.apache.org/jira/browse/HDFS-16586] and for now
> HBase use 3.2.4 on branch master.
> So I think maybe can remove these code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
