Naganarasimha G R commented on YARN-4372:

Thanks for raising this issue [~vinodkv], yes it would be better to correct the 
order, as in future if we start collecting ATSv2 system events then we will be 
having issues later. Issue i faced when i was testing with correcting the order 
was : the timeline service was having some issue starting the web service 
though the port was correctly set (was not an expert with jersey and guice, 
hence had stopped further analysis there) 

Also one more point(not related to this jira) to note in MiniYARNCluster, we no 
more support old  AHS interfce so basically 
{{yarn.timeline-service.generic-application-history.store-class}} should not be 
configured in {{ApplicationHistoryServerWrapper}} so that levelDBtimelinestore 
is created. which i feel is correct atleast for existing 2.7.x versions. And if 
you agree with it, can we fix it along with this jira as its a small thing ?, 

> Cannot enable system-metrics-publisher inside MiniYARNCluster
> -------------------------------------------------------------
>                 Key: YARN-4372
>                 URL: https://issues.apache.org/jira/browse/YARN-4372
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
> [~Naganarasimha] found this at YARN-2859, see [this 
> comment|https://issues.apache.org/jira/browse/YARN-2859?focusedCommentId=15005746&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15005746].
> The way daemons are started inside MiniYARNCluster, RM is not setup correctly 
> to send information to TimelineService.

This message was sent by Atlassian JIRA

Reply via email to