[jira] [Commented] (YARN-1890) Too many unnecessary logs are logged while accessing applicationMaster web UI.

[ https://issues.apache.org/jira/browse/YARN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957340#comment-13957340 ] Rohith commented on YARN-1890: -- Since WebAppProxyServlet.doGet() is called for every fetch dat

[jira] [Commented] (YARN-1892) Excessive logging in RM

[ https://issues.apache.org/jira/browse/YARN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957320#comment-13957320 ] Hadoop QA commented on YARN-1892: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (YARN-1892) Excessive logging in RM

[ https://issues.apache.org/jira/browse/YARN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1892: -- Attachment: YARN-1892.2.patch Added a side fix to move "sending container statuses... " in NodeStatusUpdater to

[jira] [Resolved] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

[ https://issues.apache.org/jira/browse/YARN-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhaoyunjiong resolved YARN-1888. Resolution: Not a Problem Thank you Jason Lowe and Karthik Kambatla for your time. Now I agree with

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957196#comment-13957196 ] Hadoop QA commented on YARN-1879: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1898) Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957190#comment-13957190 ] Hudson commented on YARN-1898: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5443 (See [https:

[jira] [Updated] (YARN-1898) Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1898: -- Summary: Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

[jira] [Reopened] (YARN-1830) TestRMRestart.testQueueMetricsOnRMRestart failure

[ https://issues.apache.org/jira/browse/YARN-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reopened YARN-1830: --- https://builds.apache.org/job/PreCommit-YARN-Build/3501//testReport/org.apache.hadoop.yarn.server.resource

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957160#comment-13957160 ] Zhijie Shen commented on YARN-1898: --- The test failure should be unrelated here. It's the

[jira] [Updated] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1879: - Attachment: YARN-1879.2-wip.patch Attached a WIP patch. 1. Added RetryCache support on register

[jira] [Commented] (YARN-1890) Too many unnecessary logs are logged while accessing applicationMaster web UI.

[ https://issues.apache.org/jira/browse/YARN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957128#comment-13957128 ] Jian He commented on YARN-1890: --- Agree with moving the verbose access logging into debug leve

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957122#comment-13957122 ] Xuan Gong commented on YARN-1898: - testcase: org.apache.hadoop.yarn.server.resourcemanager

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957114#comment-13957114 ] Hadoop QA commented on YARN-1898: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957059#comment-13957059 ] Xuan Gong commented on YARN-1898: - bq. The constant should be NON_REDIRECTED_URIS by conven

[jira] [Updated] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Attachment: YARN-1898.3.patch > Standby RM's conf, stack, logLevel and metrics links are redirecting to > A

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957054#comment-13957054 ] Zhijie Shen commented on YARN-1898: --- LGTM. It should cover all the default apps/servlets

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957030#comment-13957030 ] Hadoop QA commented on YARN-1898: - {color:green}+1 overall{color}. Here are the results of

[jira] [Resolved] (YARN-1862) Change mapreduce.jobhistory.done-dir by command line arg seems not working

[ https://issues.apache.org/jira/browse/YARN-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-1862. -- Resolution: Invalid This is a question best asked on the [user@ mailing list|http://hadoop.apache.org/m

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956979#comment-13956979 ] Xuan Gong commented on YARN-1898: - address the latest comments > Standby RM's conf, stack,

[jira] [Updated] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Attachment: YARN-1898.2.patch > Standby RM's conf, stack, logLevel and metrics links are redirecting to > A

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956978#comment-13956978 ] Hadoop QA commented on YARN-1726: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956973#comment-13956973 ] Xuan Gong commented on YARN-1898: - bq. what do you think of maintaining a list of URIs that

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956959#comment-13956959 ] Hadoop QA commented on YARN-1898: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726.patch > ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced > in

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956896#comment-13956896 ] Karthik Kambatla commented on YARN-1898: [~xgong] - what do you think of maintainin

[jira] [Updated] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Attachment: YARN-1898.1.patch add /conf, /stacks, /logLevel, /metrics, /jmx, /logs to RMWebAppFilter > Stan

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956872#comment-13956872 ] Karthik Kambatla commented on YARN-1898: Good catch, [~yeshavora]. > Standby RM

[jira] [Commented] (YARN-1864) Fair Scheduler Dynamic Hierarchical User Queues

[ https://issues.apache.org/jira/browse/YARN-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956875#comment-13956875 ] Ashwin Shankar commented on YARN-1864: -- Hi Sandy, No we won't be able to choose diffe

[jira] [Commented] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956845#comment-13956845 ] Xuan Gong commented on YARN-1898: - Standby RM links /conf, /stacks, /logLevel, /metrics, /

[jira] [Updated] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Description: Standby RM links /conf, /stacks, /logLevel, /metrics, /jmx, /logs is redirected to Active RM.

[jira] [Updated] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Description: Standby RM links /conf, /stacks, /logLevel, /metrics, /jmx is redirected to Active RM. It sho

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956828#comment-13956828 ] Hadoop QA commented on YARN-1726: - {color:green}+1 overall{color}. Here are the results of

[jira] [Assigned] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1898: --- Assignee: Xuan Gong > Standby RM's conf, stack, logLevel and metrics links are redirecting to > Activ

[jira] [Created] (YARN-1898) Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM

Yesha Vora created YARN-1898: Summary: Standby RM's conf, stack, logLevel and metrics links are redirecting to Active RM Key: YARN-1898 URL: https://issues.apache.org/jira/browse/YARN-1898 Project: Hadoop

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726.patch > ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced > in

[jira] [Updated] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1896: -- Description: For FairScheduler, it's very useful to expose MinimumQueueResource and MaximumQueueResource of each

[jira] [Updated] (YARN-1820) I can not run mapreduce

[ https://issues.apache.org/jira/browse/YARN-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huangxing updated YARN-1820: Summary: I can not run mapreduce (was: I can not run mapreduce!!) > I can not run mapreduce > -

[jira] [Commented] (YARN-1888) Not add NodeManager to inactiveRMNodes when reboot NodeManager which have different port

[ https://issues.apache.org/jira/browse/YARN-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956690#comment-13956690 ] Jason Lowe commented on YARN-1888: -- I agree with [~kasha] on this. A nodemanager coming u

[jira] [Commented] (YARN-1889) In Fair Scheduler, avoid creating objects on each call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956521#comment-13956521 ] Hudson commented on YARN-1889: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1718 (See [https://

[jira] [Commented] (YARN-1889) In Fair Scheduler, avoid creating objects on each call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956490#comment-13956490 ] Hudson commented on YARN-1889: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1744 (See [htt

[jira] [Commented] (YARN-1889) In Fair Scheduler, avoid creating objects on each call to AppSchedulable comparator

[ https://issues.apache.org/jira/browse/YARN-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956401#comment-13956401 ] Hudson commented on YARN-1889: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #526 (See [https://b

[jira] [Commented] (YARN-1890) Too many unnecessary logs are logged while accessing applicationMaster web UI.

[ https://issues.apache.org/jira/browse/YARN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956387#comment-13956387 ] Hadoop QA commented on YARN-1890: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queu in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956374#comment-13956374 ] Henry Saputra commented on YARN-1896: - Would be helpful to add more in the description

[jira] [Updated] (YARN-1890) Too many unnecessary logs are logged while accessing applicationMaster web UI.

[ https://issues.apache.org/jira/browse/YARN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1890: - Attachment: YARN-1890.patch Simple patch to clean excessing loggin on every refresh. Log priority is moved to DEB