[jira] [Commented] (YARN-8155) Improve ATSv2 client logging in RM and NM publisher

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512147#comment-16512147 ] Rohith Sharma K S commented on YARN-8155: - committed to trunk/branch-3.1/branch-3.0.. branch-2

[jira] [Updated] (YARN-8155) Improve ATSv2 client logging in RM and NM publisher

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8155: Summary: Improve ATSv2 client logging in RM and NM publisher (was: Improve the logging in

[jira] [Updated] (YARN-8155) Improve ATSv2 client logging in RM and NM publisher

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8155: Issue Type: Improvement (was: Bug) > Improve ATSv2 client logging in RM and NM publisher >

[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512030#comment-16512030 ] Rohith Sharma K S commented on YARN-8155: - Committing shortly.. > Improve the logging in

[jira] [Reopened] (YARN-8302) ATS v2 should handle HBase connection issue properly

[ https://issues.apache.org/jira/browse/YARN-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reopened YARN-8302: - Reopening the JIRA to discuss and figure out alternative approach other than reducing retry

[jira] [Commented] (YARN-8411) Enable stopped system services to be started during RM start

[ https://issues.apache.org/jira/browse/YARN-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510593#comment-16510593 ] Rohith Sharma K S commented on YARN-8411: - thanks [~billie.rinaldi] for the patch. It looks good

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510588#comment-16510588 ] Rohith Sharma K S commented on YARN-8405: - bq. Could you also cherry pick to branch-2.9? Done >

[jira] [Updated] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8405: Fix Version/s: 2.9.2 > RM zk-state-store.parent-path ACLs has been changed since

[jira] [Updated] (YARN-8413) Flow activity page is failing with "Timeline server failed with an error"

[ https://issues.apache.org/jira/browse/YARN-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8413: Fix Version/s: 3.1.1 3.2.0 > Flow activity page is failing with

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509513#comment-16509513 ] Rohith Sharma K S commented on YARN-8405: - test failures are unrelated to patch.. committing

[jira] [Commented] (YARN-8413) Flow activity page is failing with "Timeline server failed with an error"

[ https://issues.apache.org/jira/browse/YARN-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509514#comment-16509514 ] Rohith Sharma K S commented on YARN-8413: - +1 lgtm > Flow activity page is failing with "Timeline

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508491#comment-16508491 ] Rohith Sharma K S commented on YARN-8405: - Ahh.. I see it :-) Apologies for missing it. +1

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508412#comment-16508412 ] Rohith Sharma K S commented on YARN-8405: - thanks [~elgoiri] for patch! My concern on patch is

[jira] [Commented] (YARN-8303) YarnClient should contact TimelineReader for application/attempt/container report

[ https://issues.apache.org/jira/browse/YARN-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507256#comment-16507256 ] Rohith Sharma K S commented on YARN-8303: - All is yours:-) Go ahead.. > YarnClient should contact

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506794#comment-16506794 ] Rohith Sharma K S commented on YARN-8405: - [~elgoiri] would you please update the patch with test

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505866#comment-16505866 ] Rohith Sharma K S commented on YARN-8405: - thanks [~elgoiri] for the patch. # Since

[jira] [Updated] (YARN-8397) Thread leak in ActivitiesManager

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8397: Summary: Thread leak in ActivitiesManager (was: ActivitiesManager thread doesn't handles

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504937#comment-16504937 ] Rohith Sharma K S commented on YARN-8405: - HADOOP-14741 added ZKCuratorManager. The method in

[jira] [Updated] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8386: Fix Version/s: 3.1.1 3.2.0 > App log can not be viewed from Logs tab in

[jira] [Commented] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504871#comment-16504871 ] Rohith Sharma K S commented on YARN-8386: - committed to trunk/branch-3.1.. branch-3.0

[jira] [Commented] (YARN-8386) App log can not be viewed from Logs tab in secure cluster

[ https://issues.apache.org/jira/browse/YARN-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504857#comment-16504857 ] Rohith Sharma K S commented on YARN-8386: - +1, tested the patch in secure cluster and non-secure

[jira] [Updated] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8405: Affects Version/s: 2.9.0 > RM zk-state-store.parent-path acls has been changed since

[jira] [Updated] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8405: Target Version/s: 2.10.0, 3.1.1 > RM zk-state-store.parent-path acls has been changed since

[jira] [Updated] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8405: Affects Version/s: 3.1.0 > RM zk-state-store.parent-path acls has been changed since

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504659#comment-16504659 ] Rohith Sharma K S commented on YARN-8405: - Below is the difference *Before* : {code} [zk:

[jira] [Created] (YARN-8405) RM zk-state-store.parent-path acls has been changed since HADOOP-14773

Rohith Sharma K S created YARN-8405: --- Summary: RM zk-state-store.parent-path acls has been changed since HADOOP-14773 Key: YARN-8405 URL: https://issues.apache.org/jira/browse/YARN-8405 Project:

[jira] [Commented] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504401#comment-16504401 ] Rohith Sharma K S commented on YARN-8404: - cc :/ [~naganarasimha...@apache.org] [~jlowe]

[jira] [Commented] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504313#comment-16504313 ] Rohith Sharma K S commented on YARN-8404: - Attached patch that retain original behavior that is

[jira] [Updated] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8404: Attachment: YARN-8404.01.patch > RM Event dispatcher is blocked if ATS1/1.5 server is not

[jira] [Updated] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8404: Summary: RM Event dispatcher is blocked if ATS1/1.5 server is not running. (was: RM

[jira] [Commented] (YARN-8404) RM Recovery is delayed much if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504271#comment-16504271 ] Rohith Sharma K S commented on YARN-8404: - Making TimelineServiceV1Publisher#appFinished

[jira] [Moved] (YARN-8404) RM Recovery is delayed much if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S moved MAPREDUCE-7106 to YARN-8404: Key: YARN-8404 (was: MAPREDUCE-7106) Project:

[jira] [Updated] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8399: Fix Version/s: (was: 3.0.3) 3.2.0 > NodeManager is giving 403 GSS

[jira] [Updated] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8399: Target Version/s: 2.10.0, 3.2.0, 3.1.1, 3.0.3 (was: 3.1.1) > NodeManager is giving 403 GSS

[jira] [Updated] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8399: Fix Version/s: 3.0.3 3.1.1 > NodeManager is giving 403 GSS exception

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504259#comment-16504259 ] Rohith Sharma K S commented on YARN-8399: - I committed to trunk/branch-3.1.. patch apply to

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504228#comment-16504228 ] Rohith Sharma K S commented on YARN-8399: - forgot to commit yesterday, committing it now >

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503617#comment-16503617 ] Rohith Sharma K S commented on YARN-8399: - +1 committing shortly > NodeManager is giving 403 GSS

[jira] [Commented] (YARN-8401) Yarnui2 not working with out internet connection

[ https://issues.apache.org/jira/browse/YARN-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503604#comment-16503604 ] Rohith Sharma K S commented on YARN-8401: - [~sunilg] I remember similar issue we were faced for

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503346#comment-16503346 ] Rohith Sharma K S commented on YARN-8399: - +1 > NodeManager is giving 403 GSS exception post

[jira] [Commented] (YARN-6904) [ATSv2] Fix findbugs warnings

[ https://issues.apache.org/jira/browse/YARN-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503179#comment-16503179 ] Rohith Sharma K S commented on YARN-6904: - This JIRA we can close as it was happening in YARN-5355

[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502937#comment-16502937 ] Rohith Sharma K S commented on YARN-8155: - looks fine to me.. [~vrushalic] [~haibochen] would you

[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode

[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502364#comment-16502364 ] Rohith Sharma K S commented on YARN-8399: - Should we make this change at auxiliary service level?

[jira] [Commented] (YARN-8396) Click on an individual container continuously spins and doesn't load the page

[ https://issues.apache.org/jira/browse/YARN-8396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501840#comment-16501840 ] Rohith Sharma K S commented on YARN-8396: - thank to [~sunilg] for the patch! > Click on an

[jira] [Commented] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501737#comment-16501737 ] Rohith Sharma K S commented on YARN-8397: - Findbug error is from fair scheduler, not related to

[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501603#comment-16501603 ] Rohith Sharma K S commented on YARN-8155: - TimelineServiceV2Publisher printing exception message

[jira] [Assigned] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8397: --- Assignee: Rohith Sharma K S > ActivitiesManager thread doesn't handles

[jira] [Commented] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501582#comment-16501582 ] Rohith Sharma K S commented on YARN-8397: - There were 2 issues which got fixed in this patch. #

[jira] [Updated] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8397: Attachment: YARN-8397.01.patch > ActivitiesManager thread doesn't handles

[jira] [Created] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

Rohith Sharma K S created YARN-8397: --- Summary: ActivitiesManager thread doesn't handles InterruptedException Key: YARN-8397 URL: https://issues.apache.org/jira/browse/YARN-8397 Project: Hadoop

[jira] [Commented] (YARN-8397) ActivitiesManager thread doesn't handles InterruptedException

[ https://issues.apache.org/jira/browse/YARN-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501568#comment-16501568 ] Rohith Sharma K S commented on YARN-8397: - This is due to ActivitiesManager#serviceStop interrupt

[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499958#comment-16499958 ] Rohith Sharma K S commented on YARN-8155: - thanks Abhishek Modi for patch. it looks reasonable to

[jira] [Commented] (YARN-8319) More YARN pages need to honor yarn.resourcemanager.display.per-user-apps

[ https://issues.apache.org/jira/browse/YARN-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498857#comment-16498857 ] Rohith Sharma K S commented on YARN-8319: - [~sunilg] if it is applicable for branch-2, please feel

[jira] [Commented] (YARN-8372) ApplicationAttemptNotFoundException should be handled correctly by Distributed Shell App Master

[ https://issues.apache.org/jira/browse/YARN-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497823#comment-16497823 ] Rohith Sharma K S commented on YARN-8372: - Thanks [~suma.shivaprasad] for the patch. Approach

[jira] [Updated] (YARN-8383) TimelineServer 1.5 start fails with NoClassDefFoundError

[ https://issues.apache.org/jira/browse/YARN-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8383: Target Version/s: 2.8.5 I see this behavior only 2.8.4 but not in 2.9.x release line. It

[jira] [Created] (YARN-8383) TimelineServer 1.5 start fails with NoClassDefFoundError

Rohith Sharma K S created YARN-8383: --- Summary: TimelineServer 1.5 start fails with NoClassDefFoundError Key: YARN-8383 URL: https://issues.apache.org/jira/browse/YARN-8383 Project: Hadoop YARN

[jira] [Commented] (YARN-8368) yarn app start cli should print applicationId

[ https://issues.apache.org/jira/browse/YARN-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496188#comment-16496188 ] Rohith Sharma K S commented on YARN-8368: - Thanks [~billie.rinaldi] for review and committing the

[jira] [Commented] (YARN-8380) Support shared mounts in docker runtime

[ https://issues.apache.org/jira/browse/YARN-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496185#comment-16496185 ] Rohith Sharma K S commented on YARN-8380: - Just fyi.. Whenever docker volume is mounted with

[jira] [Commented] (YARN-8372) ApplicationAttemptNotFoundException should be handled correctly by Distributed Shell App Master

[ https://issues.apache.org/jira/browse/YARN-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494690#comment-16494690 ] Rohith Sharma K S commented on YARN-8372: - DS app master should handle shutdown request properly

[jira] [Commented] (YARN-8369) Javadoc build failed due to "bad use of '>'"

[ https://issues.apache.org/jira/browse/YARN-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492584#comment-16492584 ] Rohith Sharma K S commented on YARN-8369: - On further compiling java doc, it fails at

[jira] [Resolved] (YARN-8371) Javadoc error in ResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-8371. - Resolution: Duplicate > Javadoc error in ResourceCalculator >

[jira] [Commented] (YARN-8292) Fix the dominant resource preemption cannot happen when some of the resource vector becomes negative

[ https://issues.apache.org/jira/browse/YARN-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492565#comment-16492565 ] Rohith Sharma K S commented on YARN-8292: - This causes java doc errors in trunk and branch-3.1. See

[jira] [Updated] (YARN-8371) Javadoc error in ResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8371: Target Version/s: 3.2.0, 3.1.1 > Javadoc error in ResourceCalculator >

[jira] [Updated] (YARN-8371) Javadoc error in ResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8371: Priority: Critical (was: Major) > Javadoc error in ResourceCalculator >

[jira] [Created] (YARN-8371) Javadoc error in ResourceCalculator

Rohith Sharma K S created YARN-8371: --- Summary: Javadoc error in ResourceCalculator Key: YARN-8371 URL: https://issues.apache.org/jira/browse/YARN-8371 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-8068) Application Priority field causes NPE in app timeline publish when Hadoop 2.7 based clients to 2.8+

[ https://issues.apache.org/jira/browse/YARN-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8068: Issue Type: Sub-task (was: Bug) Parent: YARN-8347 > Application Priority field

[jira] [Updated] (YARN-8368) yarn app start cli should print applicationId

[ https://issues.apache.org/jira/browse/YARN-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8368: Attachment: YARN-8368.02.patch > yarn app start cli should print applicationId >

[jira] [Updated] (YARN-8368) yarn app start cli should print applicationId

[ https://issues.apache.org/jira/browse/YARN-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8368: Attachment: YARN-8368.01.patch > yarn app start cli should print applicationId >

[jira] [Assigned] (YARN-8368) yarn app start cli should print applicationId

[ https://issues.apache.org/jira/browse/YARN-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8368: --- Assignee: Rohith Sharma K S > yarn app start cli should print applicationId >

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489047#comment-16489047 ] Rohith Sharma K S commented on YARN-8346: - back ported to 2.9 as well. > Upgrading to 3.1 kills

[jira] [Updated] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8346: Fix Version/s: 2.9.2 > Upgrading to 3.1 kills running containers with error "Opportunistic

[jira] [Commented] (YARN-8319) More YARN pages need to honor yarn.resourcemanager.display.per-user-apps

[ https://issues.apache.org/jira/browse/YARN-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488667#comment-16488667 ] Rohith Sharma K S commented on YARN-8319: - +1, will commit it shortly > More YARN pages need to

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488526#comment-16488526 ] Rohith Sharma K S commented on YARN-8346: - committing shortly > Upgrading to 3.1 kills running

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488439#comment-16488439 ] Rohith Sharma K S commented on YARN-8346: - Thanks [~jlowe] for quick turnaround. I verified the

[jira] [Commented] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

[ https://issues.apache.org/jira/browse/YARN-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487175#comment-16487175 ] Rohith Sharma K S commented on YARN-8346: - In class ContainerScheduler#enqueueContainer, for

[jira] [Created] (YARN-8346) Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full"

Rohith Sharma K S created YARN-8346: --- Summary: Upgrading to 3.1 kills running containers with error "Opportunistic container queue is full" Key: YARN-8346 URL: https://issues.apache.org/jira/browse/YARN-8346

[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478908#comment-16478908 ] Rohith Sharma K S commented on YARN-8155: - [~abmodi] do you have time to update the patch? >

[jira] [Updated] (YARN-8297) Incorrect ATS Url used for Wire encrypted cluster

[ https://issues.apache.org/jira/browse/YARN-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8297: Attachment: (was: Ambari.txt) > Incorrect ATS Url used for Wire encrypted cluster >

[jira] [Updated] (YARN-8297) Incorrect ATS Url used for Wire encrypted cluster

[ https://issues.apache.org/jira/browse/YARN-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8297: Attachment: Ambari.txt > Incorrect ATS Url used for Wire encrypted cluster >

[jira] [Commented] (YARN-8297) Incorrect ATS Url used for Wire encrypted cluster

[ https://issues.apache.org/jira/browse/YARN-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478880#comment-16478880 ] Rohith Sharma K S commented on YARN-8297: - OK, +1 committing shortly > Incorrect ATS Url used for

[jira] [Commented] (YARN-8293) In YARN Services UI, "User Name for service" should be completely removed in secure clusters

[ https://issues.apache.org/jira/browse/YARN-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478844#comment-16478844 ] Rohith Sharma K S commented on YARN-8293: - thanks [~sunilg] for the patch. I tested the patch and

[jira] [Commented] (YARN-8297) Incorrect ATS Url used for Wire encrypted cluster

[ https://issues.apache.org/jira/browse/YARN-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478841#comment-16478841 ] Rohith Sharma K S commented on YARN-8297: - One doubt in patch, Ajax call is made with async true.

[jira] [Resolved] (YARN-8302) ATS v2 should handle HBase connection issue properly

[ https://issues.apache.org/jira/browse/YARN-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-8302. - Resolution: Won't Fix Closing the JIRA as won't fix since it is related to configuration

[jira] [Commented] (YARN-8302) ATS v2 should handle HBase connection issue properly

[ https://issues.apache.org/jira/browse/YARN-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478532#comment-16478532 ] Rohith Sharma K S commented on YARN-8302: - If HBase is down for any reasons, hbase client will

[jira] [Comment Edited] (YARN-5742) Serve aggregated logs of historical apps from timeline service

[ https://issues.apache.org/jira/browse/YARN-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477177#comment-16477177 ] Rohith Sharma K S edited comment on YARN-5742 at 5/16/18 9:46 AM: -- I have

[jira] [Commented] (YARN-5742) Serve aggregated logs of historical apps from timeline service

[ https://issues.apache.org/jira/browse/YARN-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477177#comment-16477177 ] Rohith Sharma K S commented on YARN-5742: - I have created a separate JIRA for pulling put log

[jira] [Created] (YARN-8304) Provide generic log servlet for serving logs

Rohith Sharma K S created YARN-8304: --- Summary: Provide generic log servlet for serving logs Key: YARN-8304 URL: https://issues.apache.org/jira/browse/YARN-8304 Project: Hadoop YARN Issue

[jira] [Created] (YARN-8303) YarnClient should contact TimelineReader for application/attempt/container report

Rohith Sharma K S created YARN-8303: --- Summary: YarnClient should contact TimelineReader for application/attempt/container report Key: YARN-8303 URL: https://issues.apache.org/jira/browse/YARN-8303

[jira] [Updated] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain

[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7933: Attachment: YARN-7933.06.patch > [atsv2 read acls] Add TimelineWriter#writeDomain >

[jira] [Commented] (YARN-8302) ATS v2 should handle HBase connection issue properly

[ https://issues.apache.org/jira/browse/YARN-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476872#comment-16476872 ] Rohith Sharma K S commented on YARN-8302: - Thanks [~yeshavora] for creating the issue. I am able to

[jira] [Commented] (YARN-8302) ATS v2 should handle HBase connection issue properly

[ https://issues.apache.org/jira/browse/YARN-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476873#comment-16476873 ] Rohith Sharma K S commented on YARN-8302: - cc:/ [~vrushalic] [~haibo.chen] > ATS v2 should handle

[jira] [Commented] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475340#comment-16475340 ] Rohith Sharma K S commented on YARN-8130: - thanks to [~haibochen] and [~vrushalic] for the review.

[jira] [Updated] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8130: Fix Version/s: 3.0.3 3.1.1 2.10.0 > Race condition

[jira] [Commented] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain

[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474013#comment-16474013 ] Rohith Sharma K S commented on YARN-7933: - bq. Isn't it the case that a TimelineClient must be

[jira] [Commented] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472786#comment-16472786 ] Rohith Sharma K S commented on YARN-8130: - Test failures are unrelated to this patch.

[jira] [Commented] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472274#comment-16472274 ] Rohith Sharma K S commented on YARN-8130: - make sense.. updated the patch as per comments.

[jira] [Updated] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8130: Attachment: YARN-8130.03.patch > Race condition when container events are published for

[jira] [Commented] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472189#comment-16472189 ] Rohith Sharma K S commented on YARN-8130: - Do you mean we register another event type in

[jira] [Commented] (YARN-8130) Race condition when container events are published for KILLED applications

[ https://issues.apache.org/jira/browse/YARN-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472177#comment-16472177 ] Rohith Sharma K S commented on YARN-8130: - bq. we just generate a new event upon

[jira] [Updated] (YARN-7933) [atsv2 read acls] Add TimelineWriter#writeDomain

[ https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-7933: Attachment: YARN-7933.05.patch > [atsv2 read acls] Add TimelineWriter#writeDomain >

<    1   2   3   4   5   6   7   8   9   10   >