[jira] [Commented] (YARN-9311) TestRMRestart hangs due to a deadlock

[ https://issues.apache.org/jira/browse/YARN-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1674#comment-1674 ] Rohith Sharma K S commented on YARN-9311: - I just went through YARN-8448 & YARN-8449 patch. This

[jira] [Commented] (YARN-9299) TestTimelineReaderWhitelistAuthorizationFilter ignores Http Errors

[ https://issues.apache.org/jira/browse/YARN-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1633#comment-1633 ] Rohith Sharma K S commented on YARN-9299: - thanks [~Prabhu Joseph] for the patch. +1 and will

[jira] [Commented] (YARN-8625) Aggregate Resource Allocation for each job is not present in ATS

[ https://issues.apache.org/jira/browse/YARN-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1631#comment-1631 ] Rohith Sharma K S commented on YARN-8625: - [~Prabhu Joseph] These metrics holds good for running

[jira] [Commented] (YARN-7266) Timeline Server event handler threads locked

[ https://issues.apache.org/jira/browse/YARN-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777650#comment-16777650 ] Rohith Sharma K S commented on YARN-7266: - Thanks [~Prabhu Joseph] for details.. I would like

[jira] [Commented] (YARN-7266) Timeline Server event handler threads locked

[ https://issues.apache.org/jira/browse/YARN-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774745#comment-16774745 ] Rohith Sharma K S commented on YARN-7266: - Thanks [~Prabhu Joseph] for the patch! Why are we

[jira] [Commented] (YARN-4327) RM can not renew TIMELINE_DELEGATION_TOKEN in secure clusters

[ https://issues.apache.org/jira/browse/YARN-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771594#comment-16771594 ] Rohith Sharma K S commented on YARN-4327: - This appears to be configuration issue. What is the

[jira] [Commented] (YARN-9311) TestRMRestart hangs due to a deadlock

[ https://issues.apache.org/jira/browse/YARN-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771570#comment-16771570 ] Rohith Sharma K S commented on YARN-9311: - It appear recent code/test-code change caused this

[jira] [Commented] (YARN-9233) RM may report allocated container which is killed (but not acquired by AM ) to AM which can cause spark AM confused

[ https://issues.apache.org/jira/browse/YARN-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770893#comment-16770893 ] Rohith Sharma K S commented on YARN-9233: - thanks [~BilwaST] for updating patch.. few comments #

[jira] [Updated] (YARN-8404) Timeline event publish need to be async to avoid Dispatcher thread leak in case ATS is down

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8404: Labels: atsv2 (was: ) > Timeline event publish need to be async to avoid Dispatcher thread

[jira] [Updated] (YARN-8455) Add basic ACL check for all ATS v2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8455: Labels: atsv2 (was: ) > Add basic ACL check for all ATS v2 REST APIs >

[jira] [Updated] (YARN-8512) ATSv2 entities are not published to HBase from second attempt onwards

[ https://issues.apache.org/jira/browse/YARN-8512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8512: Labels: atsv2 (was: ) > ATSv2 entities are not published to HBase from second attempt

[jira] [Updated] (YARN-8630) ATSv2 REST APIs should honor filter-entity-list-by-user in non-secure cluster when ACls are enabled

[ https://issues.apache.org/jira/browse/YARN-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8630: Labels: atsv2 (was: ) > ATSv2 REST APIs should honor filter-entity-list-by-user in

[jira] [Updated] (YARN-8486) yarn.webapp.filter-entity-list-by-user should honor limit filter for TS reader flows api

[ https://issues.apache.org/jira/browse/YARN-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8486: Labels: atsv2 (was: ) > yarn.webapp.filter-entity-list-by-user should honor limit filter

[jira] [Updated] (YARN-8492) ATSv2 HBase tests are failing with ClassNotFoundException

[ https://issues.apache.org/jira/browse/YARN-8492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8492: Labels: atsv2 test (was: test) > ATSv2 HBase tests are failing with ClassNotFoundException

[jira] [Updated] (YARN-8591) [ATSv2] NPE while checking for entity acl in non-secure cluster

[ https://issues.apache.org/jira/browse/YARN-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8591: Labels: atsv2 (was: ) > [ATSv2] NPE while checking for entity acl in non-secure cluster >

[jira] [Updated] (YARN-8950) Compilation fails with dependency convergence error for hbase.profile=2.0

[ https://issues.apache.org/jira/browse/YARN-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8950: Labels: atsv2 (was: ) > Compilation fails with dependency convergence error for

[jira] [Updated] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9034: Labels: atsv2 (was: ) > ApplicationCLI should have option to take clusterId >

[jira] [Updated] (YARN-9251) Build failure for -Dhbase.profile=2.0

[ https://issues.apache.org/jira/browse/YARN-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9251: Labels: atsv2 (was: ) > Build failure for -Dhbase.profile=2.0 >

[jira] [Updated] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9044: Labels: atsv2 (was: ) > LogsCLI should contact ATSv2 for "-am" option >

[jira] [Updated] (YARN-9242) Revert YARN-8270 from branch-3.1 and branch-3.1.2

[ https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9242: Labels: atsv2 (was: ) > Revert YARN-8270 from branch-3.1 and branch-3.1.2 >

[jira] [Commented] (YARN-9233) RM may report allocated container which is killed (but not acquired by AM ) to AM which can cause spark AM confused

[ https://issues.apache.org/jira/browse/YARN-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762412#comment-16762412 ] Rohith Sharma K S commented on YARN-9233: - Its better to skip event from RMContinerImpl to

[jira] [Commented] (YARN-9233) RM may report allocated container which is killed (but not acquired by AM ) to AM which can cause spark AM confused

[ https://issues.apache.org/jira/browse/YARN-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762403#comment-16762403 ] Rohith Sharma K S commented on YARN-9233: - Thanks [~BilwaST] for the patch! bq. Therefore the

[jira] [Commented] (YARN-8219) Add application launch time to ATSV2

[ https://issues.apache.org/jira/browse/YARN-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762349#comment-16762349 ] Rohith Sharma K S commented on YARN-8219: - Verified test in local and it doesn't related to this

[jira] [Commented] (YARN-9224) TimelineDelegationTokenIdentifier.Renewer contacts KDC for every renew/cancel token operation

[ https://issues.apache.org/jira/browse/YARN-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762354#comment-16762354 ] Rohith Sharma K S commented on YARN-9224: - [~tarunparimi] thanks for the patch! Skimming through

[jira] [Commented] (YARN-8219) Add application launch time to ATSV2

[ https://issues.apache.org/jira/browse/YARN-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761437#comment-16761437 ] Rohith Sharma K S commented on YARN-8219: - TestRMRestart timed out.. Can you confirm is it related

[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains

[ https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761436#comment-16761436 ] Rohith Sharma K S commented on YARN-7976: - I am thinking should we hold this JIRA until entity

[jira] [Commented] (YARN-8219) Add application launch time to ATSV2

[ https://issues.apache.org/jira/browse/YARN-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760582#comment-16760582 ] Rohith Sharma K S commented on YARN-8219: - thanks [~abmodi] for the clarification! I do see the

[jira] [Commented] (YARN-6735) Have a way to turn off container metrics from NMs

[ https://issues.apache.org/jira/browse/YARN-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760564#comment-16760564 ] Rohith Sharma K S commented on YARN-6735: - +1 lgtm > Have a way to turn off container metrics

[jira] [Commented] (YARN-7976) [atsv2 read acls] REST API to list domain/domains

[ https://issues.apache.org/jira/browse/YARN-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760550#comment-16760550 ] Rohith Sharma K S commented on YARN-7976: - [~abmodi] Does writer side implementation is done? >

[jira] [Commented] (YARN-3488) AM get timeline service info from RM rather than Application specific configuration.

[ https://issues.apache.org/jira/browse/YARN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760525#comment-16760525 ] Rohith Sharma K S commented on YARN-3488: - Thanks [~abmodi] for the patch. Overall patch looks

[jira] [Commented] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

[ https://issues.apache.org/jira/browse/YARN-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760518#comment-16760518 ] Rohith Sharma K S commented on YARN-9149: - +1 lgtm > yarn container -status misses logUrl when

[jira] [Updated] (YARN-9256) Make ATSv2 compilation default with hbase.profile=2.0

[ https://issues.apache.org/jira/browse/YARN-9256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9256: Attachment: YARN-9256.01.patch > Make ATSv2 compilation default with hbase.profile=2.0 >

[jira] [Updated] (YARN-9256) Make ATSv2 compilation default with hbase.profile=2.0

[ https://issues.apache.org/jira/browse/YARN-9256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9256: Target Version/s: 3.3.0 > Make ATSv2 compilation default with hbase.profile=2.0 >

[jira] [Created] (YARN-9256) Make ATSv2 compilation default with hbase.profile=2.0

Rohith Sharma K S created YARN-9256: --- Summary: Make ATSv2 compilation default with hbase.profile=2.0 Key: YARN-9256 URL: https://issues.apache.org/jira/browse/YARN-9256 Project: Hadoop YARN

[jira] [Commented] (YARN-9251) Build failure for -Dhbase.profile=2.0

[ https://issues.apache.org/jira/browse/YARN-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756840#comment-16756840 ] Rohith Sharma K S commented on YARN-9251: - Thanks [~ajisakaa] for committing patch. > Build

[jira] [Updated] (YARN-9242) Revert YARN-8270 from branch-3.1 and branch-3.1.2

[ https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9242: Summary: Revert YARN-8270 from branch-3.1 and branch-3.1.2 (was: Revert YARN-8270 from

[jira] [Resolved] (YARN-9242) Revert YARN-8270 from branch-3.1

[ https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-9242. - Resolution: Done I have reverted YARN-8270 in branch-3.1 and branch-3.1.2. Also updated

[jira] [Commented] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader

[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753714#comment-16753714 ] Rohith Sharma K S commented on YARN-8270: - In branch-3.1, this was causing error while publishing

[jira] [Updated] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader

[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8270: Fix Version/s: (was: 3.1.2) > Adding JMX Metrics for Timeline Collector and Reader >

[jira] [Updated] (YARN-9242) Revert YARN-8270 from branch-3.1

[ https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9242: Issue Type: Task (was: Bug) > Revert YARN-8270 from branch-3.1 >

[jira] [Moved] (YARN-9242) Revert YARN-8270 from branch-3.1

[ https://issues.apache.org/jira/browse/YARN-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S moved HADOOP-16078 to YARN-9242: -- Target Version/s: 3.1.2 (was: 3.1.2) Key:

[jira] [Commented] (YARN-7761) [UI2] Clicking 'master container log' or 'Link' next to 'log' under application's appAttempt goes to Old UI's Log link

[ https://issues.apache.org/jira/browse/YARN-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752022#comment-16752022 ] Rohith Sharma K S commented on YARN-7761: - +1 lgtm > [UI2] Clicking 'master container log' or

[jira] [Commented] (YARN-9224) TimelineDelegationTokenIdentifier.Renewer contacts KDC for every renew/cancel token operation

[ https://issues.apache.org/jira/browse/YARN-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749766#comment-16749766 ] Rohith Sharma K S commented on YARN-9224: - It means that application submission rate per second is

[jira] [Commented] (YARN-6695) Race condition in RM for publishing container events vs appFinished events causes NPE

[ https://issues.apache.org/jira/browse/YARN-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749560#comment-16749560 ] Rohith Sharma K S commented on YARN-6695: - Yes this is corner case and need to handle it. We can

[jira] [Commented] (YARN-6695) Race condition in RM for publishing container events vs appFinished events causes NPE

[ https://issues.apache.org/jira/browse/YARN-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736704#comment-16736704 ] Rohith Sharma K S commented on YARN-6695: - [~eyang] Publishing container events from RM is

[jira] [Commented] (YARN-6735) Have a way to turn off container metrics from NMs

[ https://issues.apache.org/jira/browse/YARN-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732893#comment-16732893 ] Rohith Sharma K S commented on YARN-6735: - I see that method reportContainerResourceUsage doesn't

[jira] [Commented] (YARN-6149) Allow port range to be specified while starting NM Timeline collector manager.

[ https://issues.apache.org/jira/browse/YARN-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732867#comment-16732867 ] Rohith Sharma K S commented on YARN-6149: - +1 lgtm, I will commit it later of today if no more

[jira] [Comment Edited] (YARN-8567) Fetching yarn logs fails for long running application if it is not present in timeline store

[ https://issues.apache.org/jira/browse/YARN-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732806#comment-16732806 ] Rohith Sharma K S edited comment on YARN-8567 at 1/3/19 9:36 AM: - +1,

[jira] [Commented] (YARN-8567) Fetching yarn logs fails for long running application if it is not present in timeline store

[ https://issues.apache.org/jira/browse/YARN-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732806#comment-16732806 ] Rohith Sharma K S commented on YARN-8567: - +1, patch doesn't seem apply.. would you rebase it? >

[jira] [Commented] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

[ https://issues.apache.org/jira/browse/YARN-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725975#comment-16725975 ] Rohith Sharma K S commented on YARN-9149: - Sure.. assigned to you! > yarn container -status

[jira] [Assigned] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

[ https://issues.apache.org/jira/browse/YARN-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-9149: --- Assignee: Abhishek Modi (was: Rohith Sharma K S) > yarn container -status misses

[jira] [Assigned] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

[ https://issues.apache.org/jira/browse/YARN-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-9149: --- Assignee: Rohith Sharma K S > yarn container -status misses logUrl when integrated

[jira] [Updated] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

[ https://issues.apache.org/jira/browse/YARN-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9149: Description: Post YARN-8303, yarn client can be integrated with ATSv2. But log url and

[jira] [Created] (YARN-9149) yarn container -status misses logUrl when integrated with ATSv2

Rohith Sharma K S created YARN-9149: --- Summary: yarn container -status misses logUrl when integrated with ATSv2 Key: YARN-9149 URL: https://issues.apache.org/jira/browse/YARN-9149 Project: Hadoop

[jira] [Commented] (YARN-9143) Aux service system-class is loading from a wrong property

[ https://issues.apache.org/jira/browse/YARN-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723765#comment-16723765 ] Rohith Sharma K S commented on YARN-9143: - thanks [~cheersyang] for the patch! +1 lgtm.. pending

[jira] [Comment Edited] (YARN-9142) UI cluster nodes page is broken

[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722798#comment-16722798 ] Rohith Sharma K S edited comment on YARN-9142 at 12/17/18 9:17 AM: ---

[jira] [Commented] (YARN-9142) UI cluster nodes page is broken

[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722793#comment-16722793 ] Rohith Sharma K S commented on YARN-9142: - We can see cluster node page is rendering nothing!

[jira] [Commented] (YARN-9142) UI cluster nodes page is broken

[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722798#comment-16722798 ] Rohith Sharma K S commented on YARN-9142: - YARN-8854 could be the reason break! cc:/ [~akhilpb]

[jira] [Created] (YARN-9142) UI cluster nodes page is broken

Rohith Sharma K S created YARN-9142: --- Summary: UI cluster nodes page is broken Key: YARN-9142 URL: https://issues.apache.org/jira/browse/YARN-9142 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-9142) UI cluster nodes page is broken

[ https://issues.apache.org/jira/browse/YARN-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9142: Attachment: ClusterNodePage.png > UI cluster nodes page is broken >

[jira] [Commented] (YARN-9125) Carriage Return character in launch command cause node manager to become unhealthy

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

[jira] [Commented] (YARN-9125) Carriage Return character in launch command cause node manager to become unhealthy

[ https://issues.apache.org/jira/browse/YARN-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721968#comment-16721968 ] Rohith Sharma K S commented on YARN-9125: - [~billie.rinaldi] [~eyang] One doubt, fix is done in

[jira] [Commented] (YARN-9114) [UI2] log service redirect url should also support user name

[ https://issues.apache.org/jira/browse/YARN-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718619#comment-16718619 ] Rohith Sharma K S commented on YARN-9114: - +1 > [UI2] log service redirect url should also

[jira] [Commented] (YARN-9016) DocumentStore as a backend for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707455#comment-16707455 ] Rohith Sharma K S commented on YARN-9016: - bq. Also not sure why some unit tests are getting

[jira] [Commented] (YARN-9016) DocumentStore as a backend for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707440#comment-16707440 ] Rohith Sharma K S commented on YARN-9016: - bq. So the TimelineSchemaCreator can be moved to the

[jira] [Commented] (YARN-9016) DocumentStore as a backend for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706902#comment-16706902 ] Rohith Sharma K S commented on YARN-9016: - Ignore my previous doubt, I was referring older tar.gz

[jira] [Commented] (YARN-9016) DocumentStore as a backend for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706889#comment-16706889 ] Rohith Sharma K S commented on YARN-9016: - I did full build and newly added package jars doesn't

[jira] [Commented] (YARN-9016) DocumentStore as a backend for ATSv2

[ https://issues.apache.org/jira/browse/YARN-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706854#comment-16706854 ] Rohith Sharma K S commented on YARN-9016: - Going through this patch and design, I see one major

[jira] [Updated] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9044: Attachment: YARN-9044.02.patch > LogsCLI should contact ATSv2 for "-am" option >

[jira] [Commented] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698422#comment-16698422 ] Rohith Sharma K S commented on YARN-9044: - [~suma.shivaprasad] [~sunilg] Could you please review

[jira] [Updated] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9044: Attachment: YARN-9044.01.patch > LogsCLI should contact ATSv2 for "-am" option >

[jira] [Assigned] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-9044: --- Assignee: Rohith Sharma K S > LogsCLI should contact ATSv2 for "-am" option >

[jira] [Updated] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

[ https://issues.apache.org/jira/browse/YARN-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9044: Attachment: YARN-9044.01.patch > LogsCLI should contact ATSv2 for "-am" option >

[jira] [Updated] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9034: Attachment: YARN-9034.04.patch > ApplicationCLI should have option to take clusterId >

[jira] [Commented] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695578#comment-16695578 ] Rohith Sharma K S commented on YARN-9034: - I found test error and working on correcting it. >

[jira] [Commented] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695514#comment-16695514 ] Rohith Sharma K S commented on YARN-9034: - UT failure is unrelated to this patch. I checked the UT

[jira] [Created] (YARN-9044) LogsCLI should contact ATSv2 for "-am" option

Rohith Sharma K S created YARN-9044: --- Summary: LogsCLI should contact ATSv2 for "-am" option Key: YARN-9044 URL: https://issues.apache.org/jira/browse/YARN-9044 Project: Hadoop YARN Issue

[jira] [Created] (YARN-9042) Javadoc error in deviceplugin package

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

[jira] [Updated] (YARN-8936) Bump up Atsv2 hbase versions

[ https://issues.apache.org/jira/browse/YARN-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8936: Summary: Bump up Atsv2 hbase versions (was: Update ATSv2 hbase.two.version to 2.0.2) >

[jira] [Updated] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9034: Attachment: YARN-9034.03.patch > ApplicationCLI should have option to take clusterId >

[jira] [Updated] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9034: Attachment: YARN-9034.02.patch > ApplicationCLI should have option to take clusterId >

[jira] [Updated] (YARN-9034) ApplicationCLI should have option to take clusterId

[ https://issues.apache.org/jira/browse/YARN-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-9034: Attachment: YARN-9034.01.patch > ApplicationCLI should have option to take clusterId >

[jira] [Commented] (YARN-8936) Update ATSv2 hbase.two.version to 2.0.2

[ https://issues.apache.org/jira/browse/YARN-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692763#comment-16692763 ] Rohith Sharma K S commented on YARN-8936: - I am OK to bump up to latest stable version. Will

[jira] [Commented] (YARN-6931) Make the aggregation interval in AppLevelTimelineCollector configurable

[ https://issues.apache.org/jira/browse/YARN-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692755#comment-16692755 ] Rohith Sharma K S commented on YARN-6931: - It is good candidate for branch-2. We can backport it

[jira] [Created] (YARN-9034) ApplicationCLI should have option to take clusterId

Rohith Sharma K S created YARN-9034: --- Summary: ApplicationCLI should have option to take clusterId Key: YARN-9034 URL: https://issues.apache.org/jira/browse/YARN-9034 Project: Hadoop YARN

[jira] [Commented] (YARN-8964) UI2 should use clusters/{cluster name} for all ATSv2 REST APIs

[ https://issues.apache.org/jira/browse/YARN-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690215#comment-16690215 ] Rohith Sharma K S commented on YARN-8964: - Skimming through patch, it looks reasonable. But I want

[jira] [Commented] (YARN-8834) Provide Java client for fetching Yarn specific entities from TimelineReader

[ https://issues.apache.org/jira/browse/YARN-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689403#comment-16689403 ] Rohith Sharma K S commented on YARN-8834: - This patch wan't committed to

[jira] [Updated] (YARN-8834) Provide Java client for fetching Yarn specific entities from TimelineReader

[ https://issues.apache.org/jira/browse/YARN-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8834: Fix Version/s: (was: 3.0.3) > Provide Java client for fetching Yarn specific entities

[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=16689340#comment-16689340 ] Rohith Sharma K S commented on YARN-8303: - +1 committing shortly > YarnClient should contact

[jira] [Created] (YARN-9031) YARN UI2 should make use of "yarn.log.server.web-service.url" to fetch container logs

Rohith Sharma K S created YARN-9031: --- Summary: YARN UI2 should make use of "yarn.log.server.web-service.url" to fetch container logs Key: YARN-9031 URL: https://issues.apache.org/jira/browse/YARN-9031

[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=16689304#comment-16689304 ] Rohith Sharma K S commented on YARN-8303: - +1 lgtm.. [~abmodi] test is failing, could you correct

[jira] [Commented] (YARN-9028) TLSv2.0 ats-hbase app flooding Isilon OneFS hdfs.log and ats-hbase region server logs

[ https://issues.apache.org/jira/browse/YARN-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689032#comment-16689032 ] Rohith Sharma K S commented on YARN-9028: - This is vendor specific deployment issue. Please

[jira] [Resolved] (YARN-9028) TLSv2.0 ats-hbase app flooding Isilon OneFS hdfs.log and ats-hbase region server logs

[ https://issues.apache.org/jira/browse/YARN-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-9028. - Resolution: Invalid > TLSv2.0 ats-hbase app flooding Isilon OneFS hdfs.log and ats-hbase

[jira] [Resolved] (YARN-9029) yarn-ats hbase expects OneFS(namenode and datanode) to have a yarn principle

[ https://issues.apache.org/jira/browse/YARN-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-9029. - Resolution: Invalid This is vendor specific deployment issue. Please contact the vendor!

[jira] [Commented] (YARN-8856) TestTimelineReaderWebServicesHBaseStorage tests failing with NoClassDefFoundError

[ https://issues.apache.org/jira/browse/YARN-8856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687700#comment-16687700 ] Rohith Sharma K S commented on YARN-8856: - +1lgtm > TestTimelineReaderWebServicesHBaseStorage

[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=16687689#comment-16687689 ] Rohith Sharma K S commented on YARN-8303: - [~abmodi] We also need to newer option in help message

[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=16687590#comment-16687590 ] Rohith Sharma K S commented on YARN-8303: - Digging more details, it appears

[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=16687572#comment-16687572 ] Rohith Sharma K S commented on YARN-8303: - thanks [~abmodi] for the patch! I see some issues while

[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=16686556#comment-16686556 ] Rohith Sharma K S commented on YARN-8303: - [~abmodi] along with above comments, 2 of checkstyle

[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=16686554#comment-16686554 ] Rohith Sharma K S commented on YARN-8303: - Some comments YarnClientImpl # Most of the API's

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