[
https://issues.apache.org/jira/browse/MAPREDUCE-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411705#comment-13411705
]
Patrick Hunt commented on MAPREDUCE-4416:
-----------------------------------------
I don't believe 4141 is the issue, as that was a build change, not something
that should effect containers.
I might be way off here but have you looked at "yarn.application.classpath" ? I
ran into a similar sounding issue the other day with MAPREDUCE-4250. Ensure
that clover jars are on the application classpath.
> Some tests fail if Clover is enabled
> ------------------------------------
>
> Key: MAPREDUCE-4416
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4416
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Kihwal Lee
> Priority: Critical
> Fix For: 2.0.1-alpha, 3.0.0
>
>
> There are number of tests running under hadoop-mapreduce-client-jobclient
> that fail if Clover is enabled. Whenever a job is launched, AM doesn't start
> because it can't locate the clover jar file.
> I thought MAPREDUCE-4253 had something to do this, but I can reproduce the
> issue on an older revision. Although unrelated, MAPREDUCE-4253 does have a
> problem and it has been reported to the jira.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
