hbase-issues mailing list archives

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

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

Appy commented on HBASE-16775:

bq. 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?

Yes, it's former. Different test classes (Test*ExportSnapshot) stepping on each other. JUnit
does not run test cases within a single Test*.java class in parallel. They are always sequential.

Your analysis in second comment is absolutely correct. So i'll update the comment and commit.

bq. As a follow up, is there any reason why this should't always be run whenever a miniMR
cluster is setup?
I have the same question. Don't know. Will ask on slack later and create jira.

> 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