[jira] [Updated] (YARN-8122) Component health threshold monitor

[ https://issues.apache.org/jira/browse/YARN-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8122: Attachment: YARN-8122.draft.patch > Component health threshold monitor > --

[jira] [Commented] (YARN-8122) Component health threshold monitor

[ https://issues.apache.org/jira/browse/YARN-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427814#comment-16427814 ] Gour Saha commented on YARN-8122: - Attaching a draft patch. I am working on testing it out and writing

[jira] [Assigned] (YARN-8122) Component health threshold monitor

[ https://issues.apache.org/jira/browse/YARN-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8122: --- Assignee: Gour Saha I am working on a patch for this. Will upload it soon. > Component health

[jira] [Created] (YARN-8122) Component health threshold monitor

Gour Saha created YARN-8122: --- Summary: Component health threshold monitor Key: YARN-8122 URL: https://issues.apache.org/jira/browse/YARN-8122 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427759#comment-16427759 ] Gour Saha commented on YARN-7142: - /cc [~leftnoteasy] > Support placement policy in yarn native services >

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426386#comment-16426386 ] Gour Saha commented on YARN-7142: - Upgrade is in the works and not complete yet. It has been broken into

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142-branch-3.1.004.patch > Support placement policy in yarn native services >

[jira] [Assigned] (YARN-8074) Support placement policy composite constraints in YARN Service

[ https://issues.apache.org/jira/browse/YARN-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8074: --- Assignee: Gour Saha Will provide a patch with the proposed API spec to consume composite constraints

[jira] [Commented] (YARN-8080) YARN native service should support component restart policy

[ https://issues.apache.org/jira/browse/YARN-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419991#comment-16419991 ] Gour Saha commented on YARN-8080: - It will also be great if you can add the example of Tensorflow using

[jira] [Commented] (YARN-8080) YARN native service should support component restart policy

[ https://issues.apache.org/jira/browse/YARN-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419986#comment-16419986 ] Gour Saha commented on YARN-8080: - Also, in YARN-Simplified-V1-API-Layer-For-Services.yaml change 

[jira] [Commented] (YARN-8080) YARN native service should support component restart policy

[ https://issues.apache.org/jira/browse/YARN-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419984#comment-16419984 ] Gour Saha commented on YARN-8080: - [~leftnoteasy], few comments: h5. ServiceMaster.java remove unnecessary

[jira] [Commented] (YARN-8084) Yarn native service classes renaming for easier development?

[ https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419903#comment-16419903 ] Gour Saha commented on YARN-8084: - [~eyang], I agree with you. I would also prefer if existing classes in

[jira] [Commented] (YARN-7939) Yarn Service Upgrade: add support to upgrade a component instance

[ https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419780#comment-16419780 ] Gour Saha commented on YARN-7939: - [~eyang], for all modifications to a service in a service collection,

[jira] [Commented] (YARN-8079) YARN native service should respect source file of ConfigFile inside Service/Component spec

[ https://issues.apache.org/jira/browse/YARN-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16419570#comment-16419570 ] Gour Saha commented on YARN-8079: - [~leftnoteasy] there are few updates you have to make to

[jira] [Commented] (YARN-8084) Yarn native service classes renaming for easier development?

[ https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418113#comment-16418113 ] Gour Saha commented on YARN-8084: - [~leftnoteasy] are you referring to changing api.records.Component to

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418081#comment-16418081 ] Gour Saha commented on YARN-7142: - Thanks [~leftnoteasy]. [~billie.rinaldi] if possible, can you please

[jira] [Commented] (YARN-7939) Yarn Service Upgrade: add support to upgrade a component instance

[ https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418079#comment-16418079 ] Gour Saha commented on YARN-7939: - bq. Sorry, this part was messed up during the original implementation.

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418033#comment-16418033 ] Gour Saha commented on YARN-7142: - Thanks [~leftnoteasy] for the offline comment. I missed changing tags to

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142.004.patch > Support placement policy in yarn native services >

[jira] [Commented] (YARN-7939) Yarn Service Upgrade: add support to upgrade a component instance

[ https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417988#comment-16417988 ] Gour Saha commented on YARN-7939: - Yes, we should use UPGRADING instead of UPGRADE (which is an action

[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=16417980#comment-16417980 ] Gour Saha commented on YARN-8048: - I think it is okay to assume that if a service needs to be started as a

[jira] [Commented] (YARN-8084) Yarn native service classes renaming for easier development?

[ https://issues.apache.org/jira/browse/YARN-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417965#comment-16417965 ] Gour Saha commented on YARN-8084: - For the service.component.Component I suggest to rename it to

[jira] [Commented] (YARN-8079) YARN native service should respect source file of ConfigFile inside Service/Component spec

[ https://issues.apache.org/jira/browse/YARN-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416836#comment-16416836 ] Gour Saha commented on YARN-8079: - I know, that's a feature Slider depends on. Actually my bad for not

[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=16416827#comment-16416827 ] Gour Saha commented on YARN-8048: - {quote} public static final String

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416819#comment-16416819 ] Gour Saha commented on YARN-7142: - [~leftnoteasy], the -1 on findbugs is an extant issue in hadoop-yarn-api

[jira] [Commented] (YARN-8079) YARN native service should respect source file of ConfigFile inside Service/Component spec

[ https://issues.apache.org/jira/browse/YARN-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416815#comment-16416815 ] Gour Saha commented on YARN-8079: - Ah, right. I missed that. In that case, both make sense. However, I

[jira] [Commented] (YARN-8079) YARN native service should respect source file of ConfigFile inside Service/Component spec

[ https://issues.apache.org/jira/browse/YARN-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416623#comment-16416623 ] Gour Saha commented on YARN-8079: - [~leftnoteasy] with reference to 003 patch, why do we need both STATIC

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142.003.patch > Support placement policy in yarn native services >

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416592#comment-16416592 ] Gour Saha commented on YARN-7142: - Uploaded a 003 patch with the following - Fixed the findbug issue and 2

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142.002.patch > Support placement policy in yarn native services >

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: (was: YARN-7142.002.patch) > Support placement policy in yarn native services >

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142.002.patch > Support placement policy in yarn native services >

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416297#comment-16416297 ] Gour Saha commented on YARN-7142: - [~leftnoteasy] thank you for the review. bq. 1) Placement policy

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Description: Placement policy exists in the API but is not implemented yet. I have filed YARN-8074 to move

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Description: Placement policy exists in the API but is not implemented yet. I have filed YARN-8074 to move

[jira] [Created] (YARN-8074) Support placement policy composite constraints in YARN Service

Gour Saha created YARN-8074: --- Summary: Support placement policy composite constraints in YARN Service Key: YARN-8074 URL: https://issues.apache.org/jira/browse/YARN-8074 Project: Hadoop YARN

[jira] [Commented] (YARN-8018) Yarn service: Add support for initiating service upgrade

[ https://issues.apache.org/jira/browse/YARN-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414284#comment-16414284 ] Gour Saha commented on YARN-8018: - Great. LGTM. +1 for the 007 patch, pending jenkins (although I don't

[jira] [Commented] (YARN-8018) Yarn service: Add support for initiating service upgrade

[ https://issues.apache.org/jira/browse/YARN-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413290#comment-16413290 ] Gour Saha commented on YARN-8018: - [~csingh], now I understand that I actually overlooked the clusterName

[jira] [Commented] (YARN-8018) Yarn service: Add support for initiating service upgrade

[ https://issues.apache.org/jira/browse/YARN-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412141#comment-16412141 ] Gour Saha commented on YARN-8018: - Thanks [~csingh] for the new patch. Please address the checkstyle issues

[jira] [Commented] (YARN-8070) Yarn Service API site doc broken due to unwanted character in YarnServiceAPI.md

[ https://issues.apache.org/jira/browse/YARN-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411916#comment-16411916 ] Gour Saha commented on YARN-8070: - [~leftnoteasy], if possible please incorporate this patch for 3.1.0

[jira] [Updated] (YARN-8070) Yarn Service API site doc broken due to unwanted character in YarnServiceAPI.md

[ https://issues.apache.org/jira/browse/YARN-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8070: Attachment: YARN-8070.001.patch > Yarn Service API site doc broken due to unwanted character in >

[jira] [Assigned] (YARN-8070) Yarn Service API site doc broken due to unwanted character in YarnServiceAPI.md

[ https://issues.apache.org/jira/browse/YARN-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8070: --- Assignee: Gour Saha > Yarn Service API site doc broken due to unwanted character in >

[jira] [Created] (YARN-8070) Yarn Service API site doc broken due to unwanted character in YarnServiceAPI.md

Gour Saha created YARN-8070: --- Summary: Yarn Service API site doc broken due to unwanted character in YarnServiceAPI.md Key: YARN-8070 URL: https://issues.apache.org/jira/browse/YARN-8070 Project: Hadoop

[jira] [Commented] (YARN-8018) Yarn service: Add support for initiating service upgrade

[ https://issues.apache.org/jira/browse/YARN-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408946#comment-16408946 ] Gour Saha commented on YARN-8018: - [~csingh], thank you for the patch. I did a first pass review of the 003

[jira] [Updated] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7142: Attachment: YARN-7142.001.patch > Support placement policy in yarn native services >

[jira] [Commented] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407527#comment-16407527 ] Gour Saha commented on YARN-7142: - [~leftnoteasy], based on our offline discussions and on the

[jira] [Updated] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7523: Priority: Critical (was: Major) > Introduce description and version field in Service record >

[jira] [Updated] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7523: Target Version/s: 3.1.0 Fix Version/s: (was: yarn-native-services) > Introduce description and

[jira] [Commented] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393350#comment-16393350 ] Gour Saha commented on YARN-7523: - Ah, my bad. You are right [~billie.rinaldi]. [~leftnoteasy], is it

[jira] [Commented] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392084#comment-16392084 ] Gour Saha commented on YARN-7523: - We have made version mandatory with this patch, which means a Yarnfile

[jira] [Comment Edited] (YARN-8000) Yarn Service: component instance name shows up as component name in container record

[ https://issues.apache.org/jira/browse/YARN-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388259#comment-16388259 ] Gour Saha edited comment on YARN-8000 at 3/7/18 5:40 AM: - [~billie.rinaldi], very

[jira] [Commented] (YARN-8000) Yarn Service: component instance name shows up as component name in container record

[ https://issues.apache.org/jira/browse/YARN-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388259#comment-16388259 ] Gour Saha commented on YARN-8000: - [~billie.rinaldi], very good point. The UI2 does not use the API

[jira] [Commented] (YARN-8000) Yarn Service: component instance name shows up as component name in container record

[ https://issues.apache.org/jira/browse/YARN-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387000#comment-16387000 ] Gour Saha commented on YARN-8000: - +1 for 003 patch. /cc [~billie.rinaldi] > Yarn Service: component

[jira] [Commented] (YARN-8000) Yarn Service: component instance name shows up as component name in container record

[ https://issues.apache.org/jira/browse/YARN-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386989#comment-16386989 ] Gour Saha commented on YARN-8000: - Sorry I missed this - In the description of {{component_instance_name}}

[jira] [Commented] (YARN-8000) Yarn Service: component instance name shows up as component name in container record

[ https://issues.apache.org/jira/browse/YARN-8000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386939#comment-16386939 ] Gour Saha commented on YARN-8000: - [~csingh], the patch looks good. Just one comment - In the builder

[jira] [Commented] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384353#comment-16384353 ] Gour Saha commented on YARN-7523: - +1 for the 002 patch. /cc [~billie.rinaldi], please review and commit

[jira] [Commented] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384284#comment-16384284 ] Gour Saha commented on YARN-7523: - [~csingh], thank you for the patch. It looks good. Few comments - 1. In

[jira] [Commented] (YARN-7991) Use ServiceState values to publish to ATS

[ https://issues.apache.org/jira/browse/YARN-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382496#comment-16382496 ] Gour Saha commented on YARN-7991: - I will work on a patch for this. > Use ServiceState values to publish

[jira] [Assigned] (YARN-7991) Use ServiceState values to publish to ATS

[ https://issues.apache.org/jira/browse/YARN-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7991: --- Assignee: Gour Saha > Use ServiceState values to publish to ATS >

[jira] [Created] (YARN-7991) Use ServiceState values to publish to ATS

Gour Saha created YARN-7991: --- Summary: Use ServiceState values to publish to ATS Key: YARN-7991 URL: https://issues.apache.org/jira/browse/YARN-7991 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-7957) Yarn service delete option disappears after stopping application

[ https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382405#comment-16382405 ] Gour Saha commented on YARN-7957: - I clearly see that we need to add the state DELETED to ServiceState. We

[jira] [Commented] (YARN-7958) ServiceMaster should only wait for recovery of containers with id that match the current application id

[ https://issues.apache.org/jira/browse/YARN-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381355#comment-16381355 ] Gour Saha commented on YARN-7958: - Thanks [~csingh] . I tested patch 003 and all UTs and manual tests

[jira] [Commented] (YARN-7958) ServiceMaster should only wait for recovery of containers with id that match the current application id

[ https://issues.apache.org/jira/browse/YARN-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380816#comment-16380816 ] Gour Saha commented on YARN-7958: - [~csingh] , thank you for the patch. The 002 patch looks good. I am

[jira] [Commented] (YARN-7523) Introduce description and version field in Service record

[ https://issues.apache.org/jira/browse/YARN-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379371#comment-16379371 ] Gour Saha commented on YARN-7523: - Sure. I also suggest that you convert YARN-7512 to a new feature and

[jira] [Commented] (YARN-7957) Yarn service delete option disappears after stopping application

[ https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376517#comment-16376517 ] Gour Saha commented on YARN-7957: - [~sunilg] , YARN Service already has a ServiceState enum. Although not

[jira] [Commented] (YARN-7957) Yarn service delete option disappears after stopping application

[ https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375277#comment-16375277 ] Gour Saha commented on YARN-7957: - [~sunilg], I see. Now, YarnApplicationState does not have a state which

[jira] [Updated] (YARN-7955) Calling stop on an already stopped service says "Successfully stopped service"

[ https://issues.apache.org/jira/browse/YARN-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7955: Attachment: YARN-7955.002.patch > Calling stop on an already stopped service says "Successfully stopped

[jira] [Commented] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373495#comment-16373495 ] Gour Saha commented on YARN-7836: - Thank you [~eyang] > YARN Service component update PUT API should not

[jira] [Assigned] (YARN-7961) Improve status response when yarn application is destroyed

[ https://issues.apache.org/jira/browse/YARN-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7961: --- Assignee: Gour Saha > Improve status response when yarn application is destroyed >

[jira] [Commented] (YARN-7957) Yarn service delete option disappears after stopping application

[ https://issues.apache.org/jira/browse/YARN-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373110#comment-16373110 ] Gour Saha commented on YARN-7957: - [~sunilg] in addition to checking states FAILED/FINISHED/KILLED can we

[jira] [Commented] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373064#comment-16373064 ] Gour Saha commented on YARN-7781: - bq. With the new multi-component flex call, I think the service json

[jira] [Commented] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373006#comment-16373006 ] Gour Saha commented on YARN-7781: - bq. Also it looks like with the single component flex, we are not

[jira] [Updated] (YARN-7955) Calling stop on an already stopped service says "Successfully stopped service"

[ https://issues.apache.org/jira/browse/YARN-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7955: Attachment: YARN-7955.001.patch > Calling stop on an already stopped service says "Successfully stopped

[jira] [Commented] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372344#comment-16372344 ] Gour Saha commented on YARN-7954: - Not sure how to write a test for this patch, since it will involve ATSv2

[jira] [Commented] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372287#comment-16372287 ] Gour Saha commented on YARN-7954: - sorry uploaded the wrong patch > Component status stays "Ready" when

[jira] [Updated] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7954: Attachment: YARN-7954.002.patch > Component status stays "Ready" when yarn service is stopped >

[jira] [Updated] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7954: Attachment: YARN-7954.001.patch > Component status stays "Ready" when yarn service is stopped >

[jira] [Created] (YARN-7955) Calling stop on an already stopped service says "Successfully stopped service"

Gour Saha created YARN-7955: --- Summary: Calling stop on an already stopped service says "Successfully stopped service" Key: YARN-7955 URL: https://issues.apache.org/jira/browse/YARN-7955 Project: Hadoop

[jira] [Updated] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7954: Affects Version/s: 3.1.0 Target Version/s: 3.1.0 > Component status stays "Ready" when yarn service is

[jira] [Assigned] (YARN-7955) Calling stop on an already stopped service says "Successfully stopped service"

[ https://issues.apache.org/jira/browse/YARN-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7955: --- Assignee: Gour Saha > Calling stop on an already stopped service says "Successfully stopped service"

[jira] [Commented] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371878#comment-16371878 ] Gour Saha commented on YARN-7954: - I have a patch for this > Component status stays "Ready" when yarn

[jira] [Assigned] (YARN-7954) Component status stays "Ready" when yarn service is stopped

[ https://issues.apache.org/jira/browse/YARN-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7954: --- Assignee: Gour Saha > Component status stays "Ready" when yarn service is stopped >

[jira] [Commented] (YARN-7940) Service AM gets NoAuth with secure ZK

[ https://issues.apache.org/jira/browse/YARN-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367646#comment-16367646 ] Gour Saha commented on YARN-7940: - The patch looks good. We tested it internally as well. +1 for commit. >

[jira] [Commented] (YARN-7799) YARN Service dependency follow up work

[ https://issues.apache.org/jira/browse/YARN-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367436#comment-16367436 ] Gour Saha commented on YARN-7799: - [~leftnoteasy] what is timeline for 3.1.0? It's not really a critical

[jira] [Commented] (YARN-7936) Add default service AM Xmx

[ https://issues.apache.org/jira/browse/YARN-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366042#comment-16366042 ] Gour Saha commented on YARN-7936: - We tested the patch in our cluster and it fixed this issue. The patch

[jira] [Updated] (YARN-7936) Add default service AM Xmx

[ https://issues.apache.org/jira/browse/YARN-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7936: Description: We were seeing issues in the Service AM where memory usage would go beyond 1gb and AM

[jira] [Updated] (YARN-7936) Add default service AM Xmx

[ https://issues.apache.org/jira/browse/YARN-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7936: Description: We were seeing issues in the Service AM where memory usage would go beyond 1gb and AM container

[jira] [Updated] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7836: Attachment: YARN-7836.003.patch > YARN Service component update PUT API should not use component name from

[jira] [Updated] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7836: Attachment: (was: YARN-7836.003.patch) > YARN Service component update PUT API should not use component

[jira] [Updated] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7836: Attachment: YARN-7836.003.patch > YARN Service component update PUT API should not use component name from

[jira] [Updated] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7836: Attachment: YARN-7836.002.patch > YARN Service component update PUT API should not use component name from

[jira] [Commented] (YARN-7909) YARN service REST API returns charset=null when kerberos enabled

[ https://issues.apache.org/jira/browse/YARN-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359125#comment-16359125 ] Gour Saha commented on YARN-7909: - We see similar issue in unsecure cluster too, like when trying to flex a

[jira] [Updated] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7836: Attachment: YARN-7836.001.patch > YARN Service component update PUT API should not use component name from

[jira] [Comment Edited] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349256#comment-16349256 ] Gour Saha edited comment on YARN-7781 at 2/1/18 8:59 PM: - I filed YARN-7836 for the

[jira] [Commented] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349256#comment-16349256 ] Gour Saha commented on YARN-7781: - I filed YARN-7836 for the component name path not used issue. > Update

[jira] [Commented] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349226#comment-16349226 ] Gour Saha commented on YARN-7781: - Makes sense. +1 for patch 03. > Update YARN-Services-Examples.md to be

[jira] [Commented] (YARN-7781) Update YARN-Services-Examples.md to be in sync with the latest code

[ https://issues.apache.org/jira/browse/YARN-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347942#comment-16347942 ] Gour Saha commented on YARN-7781: - Thanks [~jianhe] . Patch 02 looks good. +1 for commit. > Update

[jira] [Updated] (YARN-7816) YARN Service - Two different users are unable to launch a service of the same name

[ https://issues.apache.org/jira/browse/YARN-7816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-7816: Fix Version/s: 3.1.0 > YARN Service - Two different users are unable to launch a service of the same > name

[jira] [Assigned] (YARN-7142) Support placement policy in yarn native services

[ https://issues.apache.org/jira/browse/YARN-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7142: --- Assignee: Gour Saha Target Version/s: 3.1.0 YARN-6592 has been merged to trunk. I will

[jira] [Assigned] (YARN-7836) YARN Service component update PUT API should not use component name from JSON body

[ https://issues.apache.org/jira/browse/YARN-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-7836: --- Assignee: Gour Saha Target Version/s: 3.1.0 I will work on a patch for this > YARN

<    1   2   3   4   5   6   7   >