You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Tarun Parimi (Jira)" <ji...@apache.org> on 2020/07/09 09:28:00 UTC

[jira] [Created] (MAPREDUCE-7283) Timeline v2.0 does not work for jobs running in uber mode

Tarun Parimi created MAPREDUCE-7283:
---------------------------------------

             Summary: Timeline v2.0 does not work for jobs running in uber mode
                 Key: MAPREDUCE-7283
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7283
             Project: Hadoop Map/Reduce
          Issue Type: Bug
    Affects Versions: 3.1.1
            Reporter: Tarun Parimi


ATSv2.0 requires setting up timeline collector address and other related logic when the AM heartbeats to the RM. This is handled in RegularContainerAllocator which is used for normal jobs.

But uber jobs use LocalContainerAllocator which doesn't have this support. As a result the following error is always observed in uber job, when mapreduce.job.emit-timeline-data=true and ATS v2.0 is configured. The job will not publish any data to the timeline service.

{code:java}
2020-05-08 09:52:53,317 ERROR [pool-11-thread-1] org.apache.hadoop.yarn.client.api.impl.TimelineV2ClientImpl: TimelineClient has reached to max retry times : 30, but failed to fetch timeline service address. Please verify Timeline Auxiliary Service is configured in all the NMs
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org