[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=16471744#comment-16471744 ] Rohith Sharma K S commented on YARN-7933: - bq. probably we can remove the change to

[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=16471493#comment-16471493 ] Rohith Sharma K S commented on YARN-8130: - [~haibochen] do you have any more comments? If not we

[jira] [Comment Edited] (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=16470741#comment-16470741 ] Rohith Sharma K S edited comment on YARN-8130 at 5/10/18 5:03 PM: -- Events

[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=16470741#comment-16470741 ] Rohith Sharma K S commented on YARN-8130: - Events are dispatched in FIFO but NMTimelinePublisher

[jira] [Commented] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469967#comment-16469967 ] Rohith Sharma K S commented on YARN-8247: - [~leftnoteasy] [~vinodkv] [~sunilg] Does changing

[jira] [Commented] (YARN-8260) [UI2] Per-application tracking URL is no longer available in YARN UI2

[ https://issues.apache.org/jira/browse/YARN-8260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468493#comment-16468493 ] Rohith Sharma K S commented on YARN-8260: - +1lgtm > [UI2] Per-application tracking URL is no

[jira] [Commented] (YARN-8264) [UI2 GPU] GPU Info tab disappears if we click any sub link under List of Applications or List of Containers

[ https://issues.apache.org/jira/browse/YARN-8264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468471#comment-16468471 ] Rohith Sharma K S commented on YARN-8264: - +1 lgtm, committing shortly > [UI2 GPU] GPU Info tab

[jira] [Commented] (YARN-8239) [UI2] Clicking on Node Manager UI under AM container info / App Attempt page goes to old RM UI

[ https://issues.apache.org/jira/browse/YARN-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468468#comment-16468468 ] Rohith Sharma K S commented on YARN-8239: - +1 committing shortly > [UI2] Clicking on Node Manager

[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=16468465#comment-16468465 ] Rohith Sharma K S commented on YARN-8130: - Updated the patch adding a test that verify stop client

[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.02.patch > Race condition when container events are published for

[jira] [Commented] (YARN-8267) Service DELETE should have same behaviour between secure and non-secure cluster

[ https://issues.apache.org/jira/browse/YARN-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468240#comment-16468240 ] Rohith Sharma K S commented on YARN-8267: - Below are the screen shot of secure and non-secure

[jira] [Updated] (YARN-8267) Service DELETE should have same behaviour between secure and non-secure cluster

[ https://issues.apache.org/jira/browse/YARN-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8267: Attachment: Screen Shot 2018-05-08 at 10.27.06 PM.png > Service DELETE should have same

[jira] [Updated] (YARN-8267) Service DELETE should have same behaviour between secure and non-secure cluster

[ https://issues.apache.org/jira/browse/YARN-8267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8267: Attachment: Screen Shot 2018-05-08 at 10.28.12 PM.png > Service DELETE should have same

[jira] [Created] (YARN-8267) Service DELETE should have same behaviour between secure and non-secure cluster

Rohith Sharma K S created YARN-8267: --- Summary: Service DELETE should have same behaviour between secure and non-secure cluster Key: YARN-8267 URL: https://issues.apache.org/jira/browse/YARN-8267

[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=16468234#comment-16468234 ] Rohith Sharma K S commented on YARN-8130: - bq.  if it is possible to add in a small test case

[jira] [Commented] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468233#comment-16468233 ] Rohith Sharma K S commented on YARN-8247: - bq. is the response status being set when line 80 in the

[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=16467234#comment-16467234 ] Rohith Sharma K S commented on YARN-8130: - Updated the patch with linger period. cc:/ [~vrushalic]

[jira] [Assigned] (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 reassigned YARN-8130: --- Assignee: Rohith Sharma K S > Race condition when container events are published for

[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.01.patch > Race condition when container events are published for

[jira] [Commented] (YARN-8249) Few REST api's in RMWebServices are missing static user check

[ https://issues.apache.org/jira/browse/YARN-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467182#comment-16467182 ] Rohith Sharma K S commented on YARN-8249: - Thanks [~sunilg] for the patch.. Patch looks good. Could

[jira] [Commented] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467080#comment-16467080 ] Rohith Sharma K S commented on YARN-8247: - Updated patch fixing checkstyle errors > Incorrect HTTP

[jira] [Updated] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8247: Attachment: YARN-8247.02.patch > Incorrect HTTP status code returned by ATSv2 for

[jira] [Updated] (YARN-8253) HTTPS Ats v2 api call fails with "bad HTTP parsed"

[ https://issues.apache.org/jira/browse/YARN-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8253: Affects Version/s: 2.9.1 3.0.1 > HTTPS Ats v2 api call fails with

[jira] [Updated] (YARN-8253) HTTPS Ats v2 api call fails with "bad HTTP parsed"

[ https://issues.apache.org/jira/browse/YARN-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8253: Priority: Critical (was: Major) > HTTPS Ats v2 api call fails with "bad HTTP parsed" >

[jira] [Commented] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466960#comment-16466960 ] Rohith Sharma K S commented on YARN-8247: - [~vrushalic] would you please take a look at this? >

[jira] [Updated] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8247: Attachment: YARN-8247.01.patch > Incorrect HTTP status code returned by ATSv2 for

[jira] [Commented] (YARN-8253) HTTPS Ats v2 api call fails with "bad HTTP parsed"

[ https://issues.apache.org/jira/browse/YARN-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466915#comment-16466915 ] Rohith Sharma K S commented on YARN-8253: - +1, pending jenkins > HTTPS Ats v2 api call fails with

[jira] [Assigned] (YARN-8253) HTTPS Ats v2 api call fails with "bad HTTP parsed"

[ https://issues.apache.org/jira/browse/YARN-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8253: --- Assignee: Charan Hebri (was: Rohith Sharma K S) Assigned to you. > HTTPS Ats v2 api

[jira] [Assigned] (YARN-8247) Incorrect HTTP status code returned by ATSv2 for non-whitelisted users

[ https://issues.apache.org/jira/browse/YARN-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8247: --- Assignee: Rohith Sharma K S > Incorrect HTTP status code returned by ATSv2 for

[jira] [Assigned] (YARN-8253) HTTPS Ats v2 api call fails with "bad HTTP parsed"

[ https://issues.apache.org/jira/browse/YARN-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8253: --- Assignee: Rohith Sharma K S > HTTPS Ats v2 api call fails with "bad HTTP parsed" >

[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=16462813#comment-16462813 ] Rohith Sharma K S commented on YARN-7933: - {quote} Does the patch require a domain id for every

[jira] [Commented] (YARN-8239) [UI2] Clicking on Node Manager UI under AM container info / App Attempt page goes to old RM UI

[ https://issues.apache.org/jira/browse/YARN-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461948#comment-16461948 ] Rohith Sharma K S commented on YARN-8239: - I have changed reporter to Sumana. Thanks Sumana.. >

[jira] [Updated] (YARN-8239) [UI2] Clicking on Node Manager UI under AM container info / App Attempt page goes to old RM UI

[ https://issues.apache.org/jira/browse/YARN-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8239: Reporter: Sumana Sathish (was: Sunil G) > [UI2] Clicking on Node Manager UI under AM

[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.04.patch > [atsv2 read acls] Add TimelineWriter#writeDomain >

[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=16458483#comment-16458483 ] Rohith Sharma K S commented on YARN-7933: - Updated the patch with Hbase writer implementation. cc:/

[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.03.patch > [atsv2 read acls] Add TimelineWriter#writeDomain >

[jira] [Commented] (YARN-8234) Improve RM system metrics publisher's performance by pushing events to timeline server in batch

[ https://issues.apache.org/jira/browse/YARN-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458360#comment-16458360 ] Rohith Sharma K S commented on YARN-8234: - [~ziqian hu] thanks for reporting. I would like to know

[jira] [Commented] (YARN-8217) RmAuthenticationFilterInitializer /TimelineAuthenticationFilterInitializer should use Configuration.getPropsWithPrefix instead of iterator

[ https://issues.apache.org/jira/browse/YARN-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456146#comment-16456146 ] Rohith Sharma K S commented on YARN-8217: - patch looks fine to me. Findbug and checkstyle are

[jira] [Commented] (YARN-8205) Application State is not updated to ATS if AM launching is delayed.

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455803#comment-16455803 ] Rohith Sharma K S commented on YARN-8205: - Cherry picked to branch-2 as well. thanks [~sunilg] for

[jira] [Updated] (YARN-8205) Application State is not updated to ATS if AM launching is delayed.

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8205: Fix Version/s: 2.10.0 > Application State is not updated to ATS if AM launching is delayed.

[jira] [Commented] (YARN-8215) ATS v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS from NM

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455802#comment-16455802 ] Rohith Sharma K S commented on YARN-8215: - Cherry picked to branch-2 as well. thanks [~sunilg] for

[jira] [Updated] (YARN-8215) ATS v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS from NM

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8215: Fix Version/s: 2.10.0 > ATS v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS

[jira] [Commented] (YARN-8221) RMWebServices also need to honor yarn.resourcemanager.display.per-user-apps

[ https://issues.apache.org/jira/browse/YARN-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455800#comment-16455800 ] Rohith Sharma K S commented on YARN-8221: - +1 for keeping consistency across the CLI and

[jira] [Commented] (YARN-8215) Ats v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455732#comment-16455732 ] Rohith Sharma K S commented on YARN-8215: - [~sunilg] could you please take a look at it? > Ats v2

[jira] [Commented] (YARN-8215) Ats v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455683#comment-16455683 ] Rohith Sharma K S commented on YARN-8215: - This issues happens when NM is restarted and containers

[jira] [Updated] (YARN-8215) Ats v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8215: Attachment: YARN-8215.01.patch > Ats v2 returns invalid

[jira] [Assigned] (YARN-8215) Ats v2 returns invalid YARN_CONTAINER_ALLOCATED_HOST_HTTP_ADDRESS

[ https://issues.apache.org/jira/browse/YARN-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8215: --- Assignee: Rohith Sharma K S > Ats v2 returns invalid

[jira] [Commented] (YARN-8205) AM launching is delayed, then state is not updated in ATS

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454236#comment-16454236 ] Rohith Sharma K S commented on YARN-8205: - Yes it is related. I have updated 02 patch. We need to

[jira] [Commented] (YARN-8205) AM launching is delayed, then state is not updated in ATS

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453974#comment-16453974 ] Rohith Sharma K S commented on YARN-8205: - [~sunilg] could you take a look at the patch please? >

[jira] [Updated] (YARN-8205) AM launching is delayed, then state is not updated in ATS

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8205: Attachment: YARN-8205.02.patch > AM launching is delayed, then state is not updated in ATS >

[jira] [Updated] (YARN-8205) AM launching is delayed, then state is not updated in ATS

[ https://issues.apache.org/jira/browse/YARN-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8205: Attachment: YARN-8205.01.patch > AM launching is delayed, then state is not updated in ATS >

[jira] [Commented] (YARN-8182) [UI2] Proxy- Clicking on nodes under Nodes HeatMap gives 401 error

[ https://issues.apache.org/jira/browse/YARN-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445764#comment-16445764 ] Rohith Sharma K S commented on YARN-8182: - +1, tested in cluster.. committing shortly > [UI2]

[jira] [Commented] (YARN-8189) [UI2] Nodes page column headers are half truncated

[ https://issues.apache.org/jira/browse/YARN-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445762#comment-16445762 ] Rohith Sharma K S commented on YARN-8189: - +1, tested in cluster.. committing shortly > [UI2]

[jira] [Commented] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.

[ https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445384#comment-16445384 ] Rohith Sharma K S commented on YARN-6827: - Cherry-picked to branch-2 as well. thanks to [~sunilg]

[jira] [Updated] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.

[ https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-6827: Fix Version/s: 2.10.0 > [ATS1/1.5] NPE exception while publishing recovering applications

[jira] [Updated] (YARN-8145) yarn rmadmin -getGroups doesn't return updated groups for user

[ https://issues.apache.org/jira/browse/YARN-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8145: Reporter: Sumana Sathish (was: Rohith Sharma K S) > yarn rmadmin -getGroups doesn't return

[jira] [Commented] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.

[ https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442137#comment-16442137 ] Rohith Sharma K S commented on YARN-6827: - Updated the patch that does transitioningToActive post

[jira] [Updated] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.

[ https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-6827: Attachment: YARN-6827.01.patch > [ATS1/1.5] NPE exception while publishing recovering

[jira] [Assigned] (YARN-6827) [ATS1/1.5] NPE exception while publishing recovering applications into ATS during RM restart.

[ https://issues.apache.org/jira/browse/YARN-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-6827: --- Assignee: Rohith Sharma K S > [ATS1/1.5] NPE exception while publishing recovering

[jira] [Commented] (YARN-8145) yarn rmadmin -getGroups doesn't return updated groups for user

[ https://issues.apache.org/jira/browse/YARN-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441992#comment-16441992 ] Rohith Sharma K S commented on YARN-8145: - test case is passing in local, looks intermittent

[jira] [Commented] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438240#comment-16438240 ] Rohith Sharma K S commented on YARN-8126: - [~sunilg] Could you please help to commit this patch?

[jira] [Commented] (YARN-8156) Increase the default value of yarn.timeline-service.app-collector.linger-period.ms

[ https://issues.apache.org/jira/browse/YARN-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438233#comment-16438233 ] Rohith Sharma K S commented on YARN-8156: - committing shortly > Increase the default value of >

[jira] [Commented] (YARN-8156) Increase the default value of yarn.timeline-service.app-collector.linger-period.ms

[ https://issues.apache.org/jira/browse/YARN-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436890#comment-16436890 ] Rohith Sharma K S commented on YARN-8156: - +lgtm, pending jenkins > Increase the default value of

[jira] [Commented] (YARN-8156) Increase the default value of yarn.timeline-service.app-collector.linger-period.ms

[ https://issues.apache.org/jira/browse/YARN-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436887#comment-16436887 ] Rohith Sharma K S commented on YARN-8156: - {quote}Does the default setting increase to 60 second in

[jira] [Commented] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435894#comment-16435894 ] Rohith Sharma K S commented on YARN-8126: - Thanks [~gsaha]. Reg the white space issue, this could

[jira] [Updated] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8126: Attachment: YARN-8126.002.patch > [Follow up] Support auto-spawning of admin configured

[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=16435049#comment-16435049 ] Rohith Sharma K S commented on YARN-8155: - All is yours.. go ahead.. thanks > Improve the logging

[jira] [Created] (YARN-8156) Increase the default value of yarn.timeline-service.app-collector.linger-period.ms

Rohith Sharma K S created YARN-8156: --- Summary: Increase the default value of yarn.timeline-service.app-collector.linger-period.ms Key: YARN-8156 URL: https://issues.apache.org/jira/browse/YARN-8156

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

Rohith Sharma K S created YARN-8155: --- Summary: Improve the logging in NMTimelinePublisher and TimelineCollectorWebService Key: YARN-8155 URL: https://issues.apache.org/jira/browse/YARN-8155

[jira] [Created] (YARN-8145) yarn rmadmin -getGroups doesn't return updated groups for user

Rohith Sharma K S created YARN-8145: --- Summary: yarn rmadmin -getGroups doesn't return updated groups for user Key: YARN-8145 URL: https://issues.apache.org/jira/browse/YARN-8145 Project: Hadoop

[jira] [Commented] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433482#comment-16433482 ] Rohith Sharma K S commented on YARN-8126: - It make sense to me to add new section though content

[jira] [Commented] (YARN-7941) Transitive dependencies for component are not resolved

[ https://issues.apache.org/jira/browse/YARN-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433360#comment-16433360 ] Rohith Sharma K S commented on YARN-7941: - committing shortly > Transitive dependencies for

[jira] [Commented] (YARN-7941) Transitive dependencies for component are not resolved

[ https://issues.apache.org/jira/browse/YARN-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431811#comment-16431811 ] Rohith Sharma K S commented on YARN-7941: - +lgtm, verified the patch in cluster. {code} 2018-04-10

[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=16431808#comment-16431808 ] Rohith Sharma K S commented on YARN-8130: - This appears due to delay in dispatcher thread. Below is

[jira] [Commented] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431705#comment-16431705 ] Rohith Sharma K S commented on YARN-8126: - bq. If I understand correctly

[jira] [Updated] (YARN-8133) Doc link broken for yarn-service from overview page.

[ https://issues.apache.org/jira/browse/YARN-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8133: Attachment: YARN-8133.02.patch > Doc link broken for yarn-service from overview page. >

[jira] [Commented] (YARN-8131) Provice CLI option to DS for publishing entities into sub application

[ https://issues.apache.org/jira/browse/YARN-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430992#comment-16430992 ] Rohith Sharma K S commented on YARN-8131: - Primarily DS is used for verifying YARN service

[jira] [Assigned] (YARN-8133) Doc link broken for yarn-service from overview page.

[ https://issues.apache.org/jira/browse/YARN-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8133: --- Assignee: Rohith Sharma K S > Doc link broken for yarn-service from overview page. >

[jira] [Commented] (YARN-8131) Provice CLI option to DS for publishing entities into sub application

[ https://issues.apache.org/jira/browse/YARN-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430839#comment-16430839 ] Rohith Sharma K S commented on YARN-8131: - We need to provide an option in DS client CLI, unlike

[jira] [Updated] (YARN-8133) Doc link broken for yarn-service from overview page.

[ https://issues.apache.org/jira/browse/YARN-8133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8133: Attachment: YARN-8133.01.patch > Doc link broken for yarn-service from overview page. >

[jira] [Created] (YARN-8133) Doc link broken for yarn-service from overview page.

Rohith Sharma K S created YARN-8133: --- Summary: Doc link broken for yarn-service from overview page. Key: YARN-8133 URL: https://issues.apache.org/jira/browse/YARN-8133 Project: Hadoop YARN

[jira] [Created] (YARN-8131) Provice CLI option to DS for publishing entities into sub application

Rohith Sharma K S created YARN-8131: --- Summary: Provice CLI option to DS for publishing entities into sub application Key: YARN-8131 URL: https://issues.apache.org/jira/browse/YARN-8131 Project:

[jira] [Updated] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8126: Attachment: YARN-8126.001.patch > [Follow up] Support auto-spawning of admin configured

[jira] [Commented] (YARN-8048) Support auto-spawning of admin configured services during bootstrap of rm/apiserver

[ https://issues.apache.org/jira/browse/YARN-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430120#comment-16430120 ] Rohith Sharma K S commented on YARN-8048: - I have created YARN-8126 to follow up these comments. >

[jira] [Assigned] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-8126: --- Assignee: Rohith Sharma K S > [Follow up] Support auto-spawning of admin configured

[jira] [Commented] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

[ https://issues.apache.org/jira/browse/YARN-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429366#comment-16429366 ] Rohith Sharma K S commented on YARN-8126: - Copy pasting [~gsaha] comments from YARN-8048. 1.

[jira] [Created] (YARN-8126) [Follow up] Support auto-spawning of admin configured services during bootstrap of rm

Rohith Sharma K S created YARN-8126: --- Summary: [Follow up] Support auto-spawning of admin configured services during bootstrap of rm Key: YARN-8126 URL: https://issues.apache.org/jira/browse/YARN-8126

[jira] [Commented] (YARN-8048) Support auto-spawning of admin configured services during bootstrap of rm/apiserver

[ https://issues.apache.org/jira/browse/YARN-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429361#comment-16429361 ] Rohith Sharma K S commented on YARN-8048: - Thanks [~gsaha] for the detailed review. I will create

[jira] [Commented] (YARN-8124) Service Application Master log file can't be found.

[ https://issues.apache.org/jira/browse/YARN-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429179#comment-16429179 ] Rohith Sharma K S commented on YARN-8124: - I am seeing this error in OSX with sample sleep service.

[jira] [Created] (YARN-8124) Service Application Master log file can't be found.

Rohith Sharma K S created YARN-8124: --- Summary: Service Application Master log file can't be found. Key: YARN-8124 URL: https://issues.apache.org/jira/browse/YARN-8124 Project: Hadoop YARN

[jira] [Commented] (YARN-7931) [atsv2 read acls] Include domain table creation as part of schema creator

[ https://issues.apache.org/jira/browse/YARN-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428021#comment-16428021 ] Rohith Sharma K S commented on YARN-7931: - +1 lgtm > [atsv2 read acls] Include domain table

[jira] [Commented] (YARN-8107) NPE when incorrect format is used in ATSv2 filter attributes

[ https://issues.apache.org/jira/browse/YARN-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428013#comment-16428013 ] Rohith Sharma K S commented on YARN-8107: - updated the patch adding invalid expression tests

[jira] [Updated] (YARN-8107) NPE when incorrect format is used in ATSv2 filter attributes

[ https://issues.apache.org/jira/browse/YARN-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8107: Attachment: YARN-8107.002.patch > NPE when incorrect format is used in ATSv2 filter

[jira] [Commented] (YARN-8073) TimelineClientImpl doesn't honor yarn.timeline-service.versions configuration

[ https://issues.apache.org/jira/browse/YARN-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427937#comment-16427937 ] Rohith Sharma K S commented on YARN-8073: - [~vrushalic] shall I cherry-pick to above branches

[jira] [Commented] (YARN-6936) [Atsv2] Retrospect storing entities into sub application table from client perspective

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

[jira] [Commented] (YARN-8107) NPE when incorrect format is used in ATSv2 filter attributes

[ https://issues.apache.org/jira/browse/YARN-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427851#comment-16427851 ] Rohith Sharma K S commented on YARN-8107: - bq. What happens if the filter is multiple conditions

[jira] [Commented] (YARN-6936) [Atsv2] Retrospect storing entities into sub application table from client perspective

[ https://issues.apache.org/jira/browse/YARN-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427348#comment-16427348 ] Rohith Sharma K S commented on YARN-6936: - It should good to go in for

[jira] [Commented] (YARN-8119) [UI2] Timeline Server address' url scheme should be removed while accessing via KNOX

[ https://issues.apache.org/jira/browse/YARN-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427334#comment-16427334 ] Rohith Sharma K S commented on YARN-8119: - +1 lgtm. verified in cluster. > [UI2] Timeline Server

[jira] [Updated] (YARN-8107) NPE when incorrect format is used in ATSv2 filter attributes

[ https://issues.apache.org/jira/browse/YARN-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-8107: Attachment: YARN-8107.001.patch > NPE when incorrect format is used in ATSv2 filter

[jira] [Commented] (YARN-7931) [atsv2 read acls] Include domain table creation as part of schema creator

[ https://issues.apache.org/jira/browse/YARN-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426491#comment-16426491 ] Rohith Sharma K S commented on YARN-7931: - nit: I see that DomainTable class has our names. Lets

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