[
https://issues.apache.org/jira/browse/HBASE-24493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128430#comment-17128430
]
Michael Stack commented on HBASE-24493:
---------------------------------------
Spent some time looking this morning since one or two of this class of test
continues to fail nightlies on occasion.
Yes, agree the 'ExpiredTokenRemover received java.lang.InterruptedException:
sleep interrupted' is a side-effect. Trying to figure what in YARN launches
the HttpServer2 that I see in my failures is painful; why and where we start
and then stop is not logged. There are notes if you wander web on an overkill
that happens when on ubuntu 16.04 but no SIGTERM in the logs we see.
These tests have been troublesome down over time: HBASE-16671, HBASE-16634,
HBASE-20982 (branch-1), HBASE-24131, HBASE-17913, HBASE-21666, HBASE-16775, and
so on.
Going to disable the flakies for now. Will file subissue to reenable.
> [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
> Priority: Major
> Attachments:
> 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)
