[jira] [Commented] (YARN-9002) YARN Service keytab does not support s3, wasb, gs and is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682434#comment-16682434 ] Gour Saha commented on YARN-9002: - Thanks a lot [~eyang] > YARN Service keytab does not support s3, wasb,

[jira] [Updated] (YARN-9002) YARN Service keytab does not support s3, wasb, gs and is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-9002: Summary: YARN Service keytab does not support s3, wasb, gs and is restricted to HDFS and local filesystem

[jira] [Commented] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682205#comment-16682205 ] Gour Saha commented on YARN-9002: - Thanks [~eyang] for reviewing. I uploaded 002 patch with imports

[jira] [Updated] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-9002: Attachment: YARN-9002.001.patch > YARN Service keytab location is restricted to HDFS and local filesystem

[jira] [Updated] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-9002: Attachment: YARN-9002-branch-3.1.002.patch > YARN Service keytab location is restricted to HDFS and local

[jira] [Commented] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682166#comment-16682166 ] Gour Saha commented on YARN-9002: - Tested this patch in tandem with the patch in HIVE-20899 on a cluster

[jira] [Updated] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-9002: Attachment: YARN-9002-branch-3.1.001.patch > YARN Service keytab location is restricted to HDFS and local

[jira] [Created] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

Gour Saha created YARN-9002: --- Summary: YARN Service keytab location is restricted to HDFS and local filesystem only Key: YARN-9002 URL: https://issues.apache.org/jira/browse/YARN-9002 Project: Hadoop YARN

[jira] [Assigned] (YARN-9002) YARN Service keytab location is restricted to HDFS and local filesystem only

[ https://issues.apache.org/jira/browse/YARN-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-9002: --- Assignee: Gour Saha > YARN Service keytab location is restricted to HDFS and local filesystem only >

[jira] [Commented] (YARN-8682) YARN Service throws NPE when explicit null instead of empty object {} is used

[ https://issues.apache.org/jira/browse/YARN-8682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662524#comment-16662524 ] Gour Saha commented on YARN-8682: - [~csingh] it was encountered by the hive team long time back so I don't

[jira] [Commented] (YARN-8734) Readiness check for remote service belongs to the same user

[ https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629168#comment-16629168 ] Gour Saha commented on YARN-8734: - bq. Yes, component dependencies is also outside of component properties

[jira] [Updated] (YARN-8734) Readiness check for remote service belongs to the same user

[ https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8734: Attachment: Service_dependencies.png Component_dependencies.png > Readiness check for

[jira] [Commented] (YARN-8734) Readiness check for remote service

[ https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624346#comment-16624346 ] Gour Saha commented on YARN-8734: - Yup, it would be great to get [~billie.rinaldi] thoughts on the naming

[jira] [Commented] (YARN-8734) Readiness check for remote service

[ https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624319#comment-16624319 ] Gour Saha commented on YARN-8734: - In that case may be a simpler approach will be to call this property

[jira] [Commented] (YARN-8734) Readiness check for remote service

[ https://issues.apache.org/jira/browse/YARN-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624250#comment-16624250 ] Gour Saha commented on YARN-8734: - [~eyang] this is a pretty useful feature so thanks for taking this up.

[jira] [Created] (YARN-8779) Fix few discrepancies between YARN Service swagger spec and code

Gour Saha created YARN-8779: --- Summary: Fix few discrepancies between YARN Service swagger spec and code Key: YARN-8779 URL: https://issues.apache.org/jira/browse/YARN-8779 Project: Hadoop YARN

[jira] [Created] (YARN-8682) YARN Service throws NPE when explicit null instead of empty object {} is used

Gour Saha created YARN-8682: --- Summary: YARN Service throws NPE when explicit null instead of empty object {} is used Key: YARN-8682 URL: https://issues.apache.org/jira/browse/YARN-8682 Project: Hadoop YARN

[jira] [Updated] (YARN-5738) Allow services to release/kill specific containers

[ https://issues.apache.org/jira/browse/YARN-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-5738: Target Version/s: 3.0.3 Component/s: yarn-native-services > Allow services to release/kill

[jira] [Commented] (YARN-8136) Add version attribute to site doc examples and quickstart

[ https://issues.apache.org/jira/browse/YARN-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568588#comment-16568588 ] Gour Saha commented on YARN-8136: - +1. Patch looks good to me. > Add version attribute to site doc

[jira] [Commented] (YARN-8392) Allow multiple tags for anti-affinity placement policy in service specification

[ https://issues.apache.org/jira/browse/YARN-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564275#comment-16564275 ] Gour Saha commented on YARN-8392: - Thanks [~billie.rinaldi]. Patch 4 looks good. The documentation in

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564250#comment-16564250 ] Gour Saha commented on YARN-8579: - Thanks [~csingh]. [~eyang] please review and commit when you get a

[jira] [Updated] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8579: Attachment: YARN-8579.004.patch > New AM attempt could not retrieve previous attempt component data >

[jira] [Commented] (YARN-8392) Allow multiple tags for anti-affinity placement policy in service specification

[ https://issues.apache.org/jira/browse/YARN-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562621#comment-16562621 ] Gour Saha commented on YARN-8392: - [~billie.rinaldi] thank you for the patch. This symmetric scenario will

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562586#comment-16562586 ] Gour Saha commented on YARN-8579: - Ah, nice catch [~csingh]. That's exactly what the issue was. With the

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560862#comment-16560862 ] Gour Saha commented on YARN-8579: - None of the test failures are related to the code change and all

[jira] [Commented] (YARN-8522) Application fails with InvalidResourceRequestException

[ https://issues.apache.org/jira/browse/YARN-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560421#comment-16560421 ] Gour Saha commented on YARN-8522: - [~Zian Chen] 002 patch looks ok. I don't have a good setup to test

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560415#comment-16560415 ] Gour Saha commented on YARN-8579: - Thanks [~csingh] for the review. I uploaded 003 with your suggestion.

[jira] [Updated] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8579: Attachment: YARN-8579.003.patch > New AM attempt could not retrieve previous attempt component data >

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560197#comment-16560197 ] Gour Saha commented on YARN-8579: - [~csingh], please review the patch when you get a chance. > New AM

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560193#comment-16560193 ] Gour Saha commented on YARN-8579: - Uploaded 002 with a few more asserts in the test. > New AM attempt

[jira] [Updated] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8579: Attachment: YARN-8579.002.patch > New AM attempt could not retrieve previous attempt component data >

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560105#comment-16560105 ] Gour Saha commented on YARN-8429: - Awesome. Thanks again [~eyang]. > Improve diagnostic message when

[jira] [Updated] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8579: Fix Version/s: 3.1.2 3.2.0 > New AM attempt could not retrieve previous attempt

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559134#comment-16559134 ] Gour Saha commented on YARN-8429: - Thanks [~eyang] for the commit. Can you please commit it to branch-3.1

[jira] [Updated] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8579: Attachment: YARN-8579.001.patch > New AM attempt could not retrieve previous attempt component data >

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559122#comment-16559122 ] Gour Saha commented on YARN-8579: - Uploading patch 001 with a fix that I successfully tested in my cluster

[jira] [Commented] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559121#comment-16559121 ] Gour Saha commented on YARN-8579: - I investigated this issue and figured that the root cause is the

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558931#comment-16558931 ] Gour Saha commented on YARN-8429: - Mistakenly had a test commented out in patch 003. Undoing that in patch

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Attachment: YARN-8429.004.patch > Improve diagnostic message when artifact is not set properly >

[jira] [Commented] (YARN-8580) yarn.resourcemanager.am.max-attempts is not respected for yarn services

[ https://issues.apache.org/jira/browse/YARN-8580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556935#comment-16556935 ] Gour Saha commented on YARN-8580: - Actually, this is Yarn Service specific property. So the value 20 is

[jira] [Assigned] (YARN-8579) New AM attempt could not retrieve previous attempt component data

[ https://issues.apache.org/jira/browse/YARN-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8579: --- Assignee: Gour Saha > New AM attempt could not retrieve previous attempt component data >

[jira] [Commented] (YARN-8545) YARN native service should return container if launch failed

[ https://issues.apache.org/jira/browse/YARN-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556267#comment-16556267 ] Gour Saha commented on YARN-8545: - [~csingh] patch 001 looks good to me. +1. > YARN native service should

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551618#comment-16551618 ] Gour Saha commented on YARN-8429: - Patch 003 has the absolute->relative suggested change. > Improve

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Attachment: YARN-8429.003.patch > Improve diagnostic message when artifact is not set properly >

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Attachment: YARN-8429.002.patch > Improve diagnostic message when artifact is not set properly >

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551276#comment-16551276 ] Gour Saha commented on YARN-8429: - Uploaded 002 with a test fix. > Improve diagnostic message when

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Fix Version/s: (was: 3.1.1) 3.1.2 > Improve diagnostic message when artifact is not

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551208#comment-16551208 ] Gour Saha commented on YARN-8429: - [~eyang] please review when you get a chance. It's a usability

[jira] [Commented] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551204#comment-16551204 ] Gour Saha commented on YARN-8429: - [~yeshavora], with this patch the error msg will change to - {code} For

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Fix Version/s: 3.1.1 3.2.0 > Improve diagnostic message when artifact is not set

[jira] [Updated] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8429: Attachment: YARN-8429.001.patch > Improve diagnostic message when artifact is not set properly >

[jira] [Assigned] (YARN-8429) Improve diagnostic message when artifact is not set properly

[ https://issues.apache.org/jira/browse/YARN-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8429: --- Assignee: Gour Saha > Improve diagnostic message when artifact is not set properly >

[jira] [Commented] (YARN-8301) Yarn Service Upgrade: Add documentation

[ https://issues.apache.org/jira/browse/YARN-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548417#comment-16548417 ] Gour Saha commented on YARN-8301: - Great. Patch 4 looks good. Not sure why I see the trailing whitespaces

[jira] [Commented] (YARN-8542) Yarn Service: Add component name to container json

[ https://issues.apache.org/jira/browse/YARN-8542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548375#comment-16548375 ] Gour Saha commented on YARN-8542: - [~csingh] agreed that the API is to request for containers. However,

[jira] [Commented] (YARN-8301) Yarn Service Upgrade: Add documentation

[ https://issues.apache.org/jira/browse/YARN-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548360#comment-16548360 ] Gour Saha commented on YARN-8301: - [~csingh], patch 2 looks good. Let's add to the top of this doc -

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545719#comment-16545719 ] Gour Saha commented on YARN-8299: - Just thinking aloud. Would returning the data in this format make more

[jira] [Commented] (YARN-8301) Yarn Service Upgrade: Add documentation

[ https://issues.apache.org/jira/browse/YARN-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545711#comment-16545711 ] Gour Saha commented on YARN-8301: - Thanks [~csingh] for the doc patch. Overall looks good. Few comments -

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543828#comment-16543828 ] Gour Saha commented on YARN-8299: - One more minor fix in the below comment in ApplicationCLI.java - {code}

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543756#comment-16543756 ] Gour Saha commented on YARN-8299: - testFilterWithState fails locally in my env as well. > Yarn Service

[jira] [Comment Edited] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543694#comment-16543694 ] Gour Saha edited comment on YARN-8299 at 7/13/18 9:00 PM: -- In ApplicationCLI.java

[jira] [Comment Edited] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543694#comment-16543694 ] Gour Saha edited comment on YARN-8299 at 7/13/18 8:56 PM: -- In ApplicationCLI.java

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543694#comment-16543694 ] Gour Saha commented on YARN-8299: - In ApplicationCLI.java can we changed - {code}

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543680#comment-16543680 ] Gour Saha commented on YARN-8299: - Ah, my bad. The patch already supports -components. > Yarn Service

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543676#comment-16543676 ] Gour Saha commented on YARN-8299: - We need -components support, whether we support -states in tandem with

[jira] [Comment Edited] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543663#comment-16543663 ] Gour Saha edited comment on YARN-8299 at 7/13/18 8:28 PM: -- [~csingh] shouldn't we

[jira] [Commented] (YARN-8299) Yarn Service Upgrade: Add GET APIs that returns instances matching query params

[ https://issues.apache.org/jira/browse/YARN-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16543663#comment-16543663 ] Gour Saha commented on YARN-8299: - [~csingh] shouldn't we add a filter "-components

[jira] [Commented] (YARN-8360) Yarn service conflict between restart policy and NM configuration

[ https://issues.apache.org/jira/browse/YARN-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539405#comment-16539405 ] Gour Saha commented on YARN-8360: - Thanks [~suma.shivaprasad], patch 1 looks good to me. +1. > Yarn

[jira] [Commented] (YARN-8485) Priviledged container app launch is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530428#comment-16530428 ] Gour Saha commented on YARN-8485: - bq. This would ensure we don't accidentally call a rogue sudo command I

[jira] [Commented] (YARN-8445) YARN native service doesn't allow service name equals to component name

[ https://issues.apache.org/jira/browse/YARN-8445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528382#comment-16528382 ] Gour Saha commented on YARN-8445: - We might have to revisit this. It seems to be an issue in how we

[jira] [Commented] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512014#comment-16512014 ] Gour Saha commented on YARN-8425: - If you are not reporting a bug or improvement, sending email to

[jira] [Resolved] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha resolved YARN-8425. - Resolution: Not A Bug > Yarn container getting killed due to running beyond physical memory limits >

[jira] [Commented] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511241#comment-16511241 ] Gour Saha commented on YARN-8425: - If _yarn.nodemanager.pmem-check-enabled_ in your cluster is not

[jira] [Commented] (YARN-8276) [UI2] After version field became mandatory, form-based submission of new YARN service doesn't work

[ https://issues.apache.org/jira/browse/YARN-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506187#comment-16506187 ] Gour Saha commented on YARN-8276: - Thank you [~GergelyNovak] for the patch and [~sunilg] for reviewing &

[jira] [Commented] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497334#comment-16497334 ] Gour Saha commented on YARN-8308: - I uploaded patch 003 with the fixes. > Yarn service app fails due to

[jira] [Updated] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8308: Attachment: YARN-8308.003.patch > Yarn service app fails due to issues with Renew Token >

[jira] [Commented] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16497333#comment-16497333 ] Gour Saha commented on YARN-8308: - Thanks for reviewing the patch [~eyang]. I have updated the patch to

[jira] [Updated] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8308: Attachment: YARN-8308.002.patch > Yarn service app fails due to issues with Renew Token >

[jira] [Comment Edited] (YARN-8276) [UI2] After version field became mandatory, form-based submission of new YARN service through UI2 doesn't work

[ https://issues.apache.org/jira/browse/YARN-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496169#comment-16496169 ] Gour Saha edited comment on YARN-8276 at 5/31/18 6:38 AM: -- [~sunilg], can you

[jira] [Updated] (YARN-8276) [UI2] After version field became mandatory, form-based submission of new YARN service through UI2 doesn't work

[ https://issues.apache.org/jira/browse/YARN-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8276: Target Version/s: 3.1.1 > [UI2] After version field became mandatory, form-based submission of new YARN >

[jira] [Updated] (YARN-8276) [UI2] After version field became mandatory, form-based submission of new YARN service through UI2 doesn't work

[ https://issues.apache.org/jira/browse/YARN-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8276: Priority: Critical (was: Major) > [UI2] After version field became mandatory, form-based submission of new

[jira] [Commented] (YARN-8276) [UI2] After version field became mandatory, form-based submission of new YARN service through UI2 doesn't work

[ https://issues.apache.org/jira/browse/YARN-8276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496169#comment-16496169 ] Gour Saha commented on YARN-8276: - [~sunilg], can you please review this. This is critical for 3.1.0. >

[jira] [Updated] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8308: Attachment: YARN-8308.001.patch > Yarn service app fails due to issues with Renew Token >

[jira] [Commented] (YARN-8367) 2 components, one with placement constraint and one without causes NPE in SingleConstraintAppPlacementAllocator

[ https://issues.apache.org/jira/browse/YARN-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496069#comment-16496069 ] Gour Saha commented on YARN-8367: - I am not sure if the UT failure is related, but it succeeds in my

[jira] [Commented] (YARN-8367) 2 components, one with placement constraint and one without causes NPE in SingleConstraintAppPlacementAllocator

[ https://issues.apache.org/jira/browse/YARN-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495948#comment-16495948 ] Gour Saha commented on YARN-8367: - [~cheersyang] thank you for the patch. 001 looks good. I even tested in

[jira] [Commented] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495610#comment-16495610 ] Gour Saha commented on YARN-8350: - Thanks [~billie.rinaldi] for reviewing the patch. The missing space

[jira] [Updated] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8308: Target Version/s: 3.1.1 > Yarn service app fails due to issues with Renew Token >

[jira] [Resolved] (YARN-8309) Diagnostic message for yarn service app failure due token renewal should be improved

[ https://issues.apache.org/jira/browse/YARN-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha resolved YARN-8309. - Resolution: Won't Do > Diagnostic message for yarn service app failure due token renewal should be >

[jira] [Commented] (YARN-8309) Diagnostic message for yarn service app failure due token renewal should be improved

[ https://issues.apache.org/jira/browse/YARN-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494326#comment-16494326 ] Gour Saha commented on YARN-8309: - Once a fix for YARN-8308 is provided this diagnostics message fix won't

[jira] [Assigned] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha reassigned YARN-8308: --- Assignee: Gour Saha > Yarn service app fails due to issues with Renew Token >

[jira] [Commented] (YARN-8308) Yarn service app fails due to issues with Renew Token

[ https://issues.apache.org/jira/browse/YARN-8308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494324#comment-16494324 ] Gour Saha commented on YARN-8308: - will provide a patch for this issue > Yarn service app fails due to

[jira] [Created] (YARN-8367) 2 components, one with placement constraint and one without causes NPE in SingleConstraintAppPlacementAllocator

Gour Saha created YARN-8367: --- Summary: 2 components, one with placement constraint and one without causes NPE in SingleConstraintAppPlacementAllocator Key: YARN-8367 URL: https://issues.apache.org/jira/browse/YARN-8367

[jira] [Commented] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490809#comment-16490809 ] Gour Saha commented on YARN-8350: - Thanks [~billie.rinaldi]. Patch 02 has all the files. > NPE in service

[jira] [Updated] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8350: Attachment: YARN-8350.02.patch > NPE in service AM related to placement policy >

[jira] [Commented] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490802#comment-16490802 ] Gour Saha commented on YARN-8350: - Oops, good catch I missed attaching the file Component.java in the

[jira] [Updated] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8350: Component/s: yarn-native-services > NPE in service AM related to placement policy >

[jira] [Updated] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8350: Target Version/s: 3.1.1 > NPE in service AM related to placement policy >

[jira] [Updated] (YARN-8350) NPE in service AM related to placement policy

[ https://issues.apache.org/jira/browse/YARN-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8350: Attachment: YARN-8350.01.patch > NPE in service AM related to placement policy >

[jira] [Commented] (YARN-7530) hadoop-yarn-services-api should be part of hadoop-yarn-services

[ https://issues.apache.org/jira/browse/YARN-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480659#comment-16480659 ] Gour Saha commented on YARN-7530: - +1 for this change. [~csingh], I am assuming that after the git moves

[jira] [Commented] (YARN-8243) Flex down should remove instance with largest component instance ID first

[ https://issues.apache.org/jira/browse/YARN-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472742#comment-16472742 ] Gour Saha commented on YARN-8243: - Thanks [~billie.rinaldi] and [~suma.shivaprasad] for reviewing. Also

[jira] [Updated] (YARN-8243) Flex down should first remove pending container requests (if any) and then kill running containers

[ https://issues.apache.org/jira/browse/YARN-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha updated YARN-8243: Priority: Critical (was: Major) > Flex down should first remove pending container requests (if any) and

  1   2   3   4   5   6   7   >