Naganarasimha G R commented on YARN-3044:

hi [~zjshen], i have already checked it, i am able to reproduce the failure 
even without my patch applied, also i had ran this test case individually with 
my changes and it was fine !  Based on my analysis its caused due to multiple 
issues : 
# setting the timeline auxillary service only for 
{{testDSShellWithoutDomainV2CustomizedFlow}} & 
{{testDSShellWithoutDomainV2CustomizedFlow}} in 
{{TestDistributedShell.setupInternal}} but 
yarn.nodemanager.container-metrics.enable is enabled by default hence metrics 
are always trying to be published.
# {{TimelineClientImpl.putObjects}} once finishes all the retry attempts in 
{{pollTimelineServiceAddress}} and still the {{timelineServiceAddress}} is null 
(not updated) then the next while loop should be run only if the 
{{timelineServiceAddress}} is not null. if not nullpointer exception is thrown 
in {{constructResURI}}

On Null pointer exception all the threads gets expired and thread pool executor 
in ContainersMonitorImpl starts rejecting to launch threads hence the container 
metrics are not getting launched. Will try to provide the patch @ the earliest. 

> [Event producers] Implement RM writing app lifecycle events to ATS
> ------------------------------------------------------------------
>                 Key: YARN-3044
>                 URL: https://issues.apache.org/jira/browse/YARN-3044
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3044-YARN-2928.004.patch, 
> YARN-3044-YARN-2928.005.patch, YARN-3044-YARN-2928.006.patch, 
> YARN-3044-YARN-2928.007.patch, YARN-3044-YARN-2928.008.patch, 
> YARN-3044-YARN-2928.009.patch, YARN-3044-YARN-2928.010.patch, 
> YARN-3044-YARN-2928.011.patch, YARN-3044.20150325-1.patch, 
> YARN-3044.20150406-1.patch, YARN-3044.20150416-1.patch
> Per design in YARN-2928, implement RM writing app lifecycle events to ATS.

This message was sent by Atlassian JIRA

Reply via email to