You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/06/08 21:22:00 UTC

[jira] [Resolved] (HBASE-24493) [flakey test] TestExportSnapshot family of tests failing due to timeout in AbstractDelegationTokenSecretManager$ExpiredTokenRemover

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

Michael Stack resolved HBASE-24493.
-----------------------------------
    Fix Version/s: 2.3.0
                   3.0.0-alpha-1
         Assignee: Michael Stack
       Resolution: Fixed

Pushed the disabling of these four test suites. See sub-issue for reenabling when we have handle on yarn history server startup.

> [flakey test] TestExportSnapshot family of tests failing due to timeout in AbstractDelegationTokenSecretManager$ExpiredTokenRemover
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-24493
>                 URL: https://issues.apache.org/jira/browse/HBASE-24493
>             Project: HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 2.3.0
>            Reporter: Nick Dimiduk
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>         Attachments: 0001-HBASE-24493-flakey-test-TestExportSnapshot-family-of.patch, TEST-org.apache.hadoop.hbase.snapshot.TestExportSnapshot.xml
>
>
> I've observed another occurrence of this test timing out, over on https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1786/3/
> The failure message is cryptic, but I think i found the issue. This isn't the {{HBaseClassTestRule}} invoking the timeout, it's something in the test, I think in the mini-cluster.
> There appears to be a timeout set in some kind of secret manager, which is too aggressive for this mini-cluster test. The last component of the mini-cluster, MapReduce, is finally available at T+273501ms -- ~4.5 minutes after process launch. This is how I interpret the log line
> {noformat}
> 2020-06-02 03:20:49,252 INFO  [Thread-223] server.Server(419): Started @273501ms
> {noformat}
> a scant 20ms later we get
> {noformat}
> 2020-06-02 03:20:50,274 ERROR [Thread[Thread-224,5,FailOnTimeoutGroup]] delegation.AbstractDelegationTokenSecretManager$ExpiredTokenRemover(700): ExpiredTokenRemover received java.lang.InterruptedException: sleep interrupted
> 2020-06-02 03:20:50,351 INFO  [Time-limited test] hbase.HBaseTestingUtility(1272): Shutting down minicluster
> {noformat}
> These thread group names have no meaning to me.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)