Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
There are some ArithmeticException failures in certain MapReduce test cases, for example:
2021-06-14 14:14:20,078 INFO [main] service.AbstractService (AbstractService.java:noteFailure(267)) - Service org.apache.hadoop.mapreduce.v2.app.MRAppMaster failed in state STARTED java.lang.ArithmeticException: / by zero at org.apache.hadoop.yarn.event.AsyncDispatcher$GenericEventHandler.handle(AsyncDispatcher.java:304) at org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:1015) at org.apache.hadoop.mapreduce.v2.app.job.impl.JobImpl.handle(JobImpl.java:141) at org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobEventDispatcher.handle(MRAppMaster.java:1544) at org.apache.hadoop.mapreduce.v2.app.MRAppMaster.serviceStart(MRAppMaster.java:1263) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:194) at org.apache.hadoop.mapreduce.v2.app.MRApp.submit(MRApp.java:301) at org.apache.hadoop.mapreduce.v2.app.MRApp.submit(MRApp.java:285) at org.apache.hadoop.mapreduce.v2.app.TestMRApp.testUpdatedNodes(TestMRApp.java:223)
We have to set detailsInterval when the async dispatcher is spied. For some reason, despite the fact that serviceInit() is called, this variable remains zero.
Attachments
Issue Links
- duplicates
-
YARN-9817 Fix failing testcases due to not initialized AsyncDispatcher - ArithmeticException: / by zero
- Resolved