hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
Date Wed, 12 Apr 2017 13:25:41 GMT

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

Jonathan Hsieh commented on HBASE-16775:

Hey Appy, to clarify, when you say they are running parallely, do you mean that TestExportSnapshot#testConsecutiveExport
and TestMobExportSnapshot# testConsecutiveExport were stepping on each other when run in parallel
or do you mean the different test cases within each Test*ExportSnapshot class (e.g. TestExportSnapshot#testConsecutiveExport
and TestExportSnapshot#testExportFileSystemStateWithSkipTemp ) were stepping on each other?

I think from the failure report here it is the former case.

> Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry

> ----------------------------------------------------------------------------------------------
>                 Key: HBASE-16775
>                 URL: https://issues.apache.org/jira/browse/HBASE-16775
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: huaxiang sun
>            Assignee: Appy
>         Attachments: disable.patch, HBASE-16775.master.001.patch, HBASE-16775.master.002.patch,
HBASE-16775.master.003.patch, HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not taken by the
mapper job, so the retry is actually 0. Debugging to see why this is the case.

This message was sent by Atlassian JIRA

View raw message