[ 
https://issues.apache.org/jira/browse/HBASE-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495459#comment-15495459
 ] 

Hudson commented on HBASE-16634:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1610 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1610/])
HBASE-16634 Speedup TestExportSnapshot (matteo.bertozzi: rev 
e19632a19abc52a983d444811852bf0f11cd0d0b)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestMobExportSnapshot.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestSecureExportSnapshot.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/MobSnapshotTestingUtils.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/SnapshotTestingUtils.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestFlushSnapshotFromClient.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestMobSecureExportSnapshot.java


> Speedup TestExportSnapshot
> --------------------------
>
>                 Key: HBASE-16634
>                 URL: https://issues.apache.org/jira/browse/HBASE-16634
>             Project: HBase
>          Issue Type: Test
>          Components: snapshots, test
>    Affects Versions: 2.0.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16634-v0.patch, HBASE-16634-v1.patch
>
>
> TestExportSnapshot is a long and heavy test since has to take snapshot, 
> export (via MR), restore them and so on. this in general make the test flaky 
> due to slowness.
> let's try to speed it up a bit by reducing the number of regions of the table 
> we are testing on 9 regions at the moment we can reduce it at least to 2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to