[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553251#comment-15553251
]
Appy commented on HBASE-16775:
------------------------------
Was added in HBASE-10537. The change was about throwing exceptions from mapper
in case of re-triable failures so that MR framework can retry the mapper.
The right test would have been injecting those failures x times (when retry is
set to >x times) and see that export job succeeds. But our testing framework
isn't sophisticated enough so i guess this proxy test was added.
However for reasons in previous comment, doesn't makes sense to keep it around.
Should we remove it [~mbertozzi].
> 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: huaxiang sun
>
> 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
(v6.3.4#6332)
