[
https://issues.apache.org/jira/browse/HBASE-24131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077665#comment-17077665
]
Michael Stack commented on HBASE-24131:
---------------------------------------
Hmmm. Running standalone I see that the full TestExportSnapshot can take a
short as 3minutes and a few seconds. Guessing then that its access to system
resources that slows us down. Let me see if split helps.
> [Flakey Tests] TestExportSnapshot takes too long; up against 13min max
> ----------------------------------------------------------------------
>
> Key: HBASE-24131
> URL: https://issues.apache.org/jira/browse/HBASE-24131
> Project: HBase
> Issue Type: Bug
> Reporter: Michael Stack
> Priority: Major
>
> TestExportSnapshot fails fairly regularly locally. Looking, its test timeout.
> Looking at how long it ran, its 13minutes plus. Looking at recent successful
> branch-2 run, it passed but it took about 7-8minutes. Let me break up the
> test into to pieces.
> org.junit.runners.model.TestTimedOutException: test timed out after 780
> seconds
> at
> org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:227)
> at
> org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportRetry(TestExportSnapshot.java:267)
> ... I see this in the log:
> ====> TEST TIMED OUT. PRINTING THREAD DUMP. <====
> Test started at:
> 2020-04-06 17:19:21,739 INFO
> ... and the timestamp just above the TIMED OUT was
> 2020-04-06 17:31:01,758
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
