[jira] [Updated] (HBASE-19954) Separate TestBlockReorder into individual tests to avoid ShutdownHook suppression error against hadoop3

["Ted Yu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-19954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-19954:
---------------------------
    Summary: Separate TestBlockReorder into individual tests to avoid ShutdownHook suppression error against hadoop3   (was: ShutdownHook should check whether shutdown hook is tracked by ShutdownHookManager)

> Separate TestBlockReorder into individual tests to avoid ShutdownHook suppression error against hadoop3 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19954
>                 URL: https://issues.apache.org/jira/browse/HBASE-19954
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>         Attachments: 19954.v1.txt, 19954.v2.txt, 19954.v3.txt, 19954.v4.txt
>
>
> Currently ShutdownHook#suppressHdfsShutdownHook() does the following:
> {code}
>       synchronized (fsShutdownHooks) {
>         boolean isFSCacheDisabled = fs.getConf().getBoolean("fs.hdfs.impl.disable.cache", false);
>         if (!isFSCacheDisabled && !fsShutdownHooks.containsKey(hdfsClientFinalizer)
>             && !ShutdownHookManager.deleteShutdownHook(hdfsClientFinalizer)) {
> {code}
> There is no check that ShutdownHookManager still tracks the shutdown hook, leading to potential RuntimeException (as can be observed in hadoop3 Jenkins job).



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