hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MAPREDUCE-6545) Test committer.commitJob() behavior during committing when MR AM get failed.
Date Tue, 24 Nov 2015 13:09:11 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Junping Du reassigned MAPREDUCE-6545:
-------------------------------------

    Assignee: Junping Du

> Test committer.commitJob() behavior during committing when MR AM get failed.
> ----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6545
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6545
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Junping Du
>            Assignee: Junping Du
>
> In MAPREDUCE-5485, we are adding additional API (isCommitJobRepeatable) to allow job
commit can tolerate AM failure in some cases (like FileOutputCommitter in v2 algorithm). Although
we have unit test to cover most of flows, we may want a completed end to end test to verify
the whole work flow.
> The scenario include:
> 1. For FileOutputCommitter (or some sub class), emulate a MR AM failure or restart during
commitJob() in progress
> 2. Check different behavior for v1 and v2 (support isCommitJobRepeatable() or not)



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

Mime
View raw message