[jira] [Commented] (YARN-4372) Cannot enable system-metrics-publisher inside MiniYARNCluster
[ https://issues.apache.org/jira/browse/YARN-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023169#comment-15023169 ] Vinod Kumar Vavilapalli commented on YARN-4372: --- bq. Even after the patch TestDistributedShell.testDSShellWithoutDomain is failing (test case passes but the in the console logs there were logs for unreachable timlineserver for each smp events). You are right, *sigh*, this is the same bug we ran into at YARN-3087: Guice not letting us run two UI services at the same time. This used to work because Timeline Service started last before this patch. Need to think more, not sure how we can fix this. > 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 > Attachments: YARN-4372-20151119.1.txt > > > [~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 (v6.3.4#6332)
[jira] [Commented] (YARN-4372) Cannot enable system-metrics-publisher inside MiniYARNCluster
[
https://issues.apache.org/jira/browse/YARN-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018418#comment-15018418
]
Naganarasimha G R commented on YARN-4372:
-
hi [~vinodkv],
bq. Can you try my uploaded patch here together with YARN-4350 and see if you
still find issues?
took the latest code from trunk as YARN-2859 is commited, later just added the
below modification in
{{TestDistributedShell}}
{code}
@@ -80,6 +80,7 @@ protected void setupInternal(int numNodeManager) throws
Exception {
conf.setInt(YarnConfiguration.RM_SCHEDULER_MINIMUM_ALLOCATION_MB, 128);
conf.set("yarn.log.dir", "target");
conf.setBoolean(YarnConfiguration.TIMELINE_SERVICE_ENABLED, true);
+conf.setBoolean(YarnConfiguration.RM_SYSTEM_METRICS_PUBLISHER_ENABLED,
true);
conf.set(YarnConfiguration.RM_SCHEDULER,
CapacityScheduler.class.getName());
conf.setBoolean(YarnConfiguration.NODE_LABELS_ENABLED, true);
conf.set("mapreduce.jobhistory.address",
{code}
Even after the patch {{TestDistributedShell.testDSShellWithoutDomain}} is
failing (test case passes but the in the console logs there were logs for
unreachable timlineserver for each smp events). Crossverified the {{resURI}} is
getting set properly in {{TimelineClientImpl}}. This is the same which i had
faced when i was last analyzing and i too had done the similar modifications in
MiniYarnCluster.
Few console logs
{code}
2015-11-20 23:17:15,867 ERROR [AsyncDispatcher event handler]
impl.TimelineClientImpl (TimelineClientImpl.java:doPosting(336)) - Failed to
get the response from the timeline server.
2015-11-20 23:17:15,868 ERROR [AsyncDispatcher event handler]
metrics.SystemMetricsPublisher (SystemMetricsPublisher.java:putEntity(485)) -
Error when publishing entity
[YARN_CONTAINER,container_1448041615020_0001_01_02]
{code}
bq. The separate thread is not an issue as RM will only start after AHS
successfully starts.
Yes you are right, my mistake had just observed that it was started as part of
thread but we are further checking whether the service is started and throwing
exception if necessary.
bq. Even if that store is specified, TimelineDataManager will continue to be
instantiated in the server, so your assumption is wrong that levelDB is not
created. Agree?
Oops had wrongly mentioned *levelDBtimelinestore* but wanted to mention as
{{ApplicationHistoryManagerOnTimelineStore}}.
As any way we are starting Timelinestore so better to have
ApplicationHistoryManagerOnTimelineStore than the almost deprecated
{{yarn.timeline-service.generic-application-history.store-class}} interface .
(not a must fix but better to have)
> 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
> Attachments: YARN-4372-20151119.1.txt
>
>
> [~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
(v6.3.4#6332)
[jira] [Commented] (YARN-4372) Cannot enable system-metrics-publisher inside MiniYARNCluster
[
https://issues.apache.org/jira/browse/YARN-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014894#comment-15014894
]
Hadoop QA commented on YARN-4372:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 6s
{color} | {color:blue} docker + precommit patch detected. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m 7s
{color} | {color:blue} The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute
for instructions. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
55s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 55s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 7s
{color} | {color:green} trunk passed with JDK v1.7.0_85 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 32s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
44s {color} | {color:green} trunk passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m 16s
{color} | {color:red} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common in
trunk has 3 extant Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 17s
{color} | {color:green} trunk passed with JDK v1.7.0_85 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 41s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 41s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 3s
{color} | {color:green} the patch passed with JDK v1.7.0_85 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 3s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
25s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 28s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
43s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 2s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_85 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 52s
{color} | {color:green} hadoop-yarn-common in the patch passed with JDK
v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 58m 27s {color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed with JDK
v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 5m 35s {color}
| {color:red} hadoop-yarn-server-tests in the patch failed with JDK v1.8.0_66.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 7s
{color} | {color:green} hadoop-yarn-common in the patch passed with JDK
v1.7.0_85. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 59m 35s {color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed with JDK
v1.7.0_85. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 5m
[jira] [Commented] (YARN-4372) Cannot enable system-metrics-publisher inside MiniYARNCluster
[
https://issues.apache.org/jira/browse/YARN-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013280#comment-15013280
]
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
(v6.3.4#6332)
