[jira] [Commented] (YARN-8028) Support authorizeUserAccessToQueue in RMWebServices

[ https://issues.apache.org/jira/browse/YARN-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1640#comment-1640 ] Sunil G commented on YARN-8028: --- Approach looks fine. Some minor ones. # Unused imports in 

[jira] [Commented] (YARN-8040) [UI2] yarn new ui web-app does not respect current pathname for REST api

[ https://issues.apache.org/jira/browse/YARN-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402211#comment-16402211 ] Sunil G commented on YARN-8040: --- Hi [~leftnoteasy]. could u pls help to review this. I tested in normal

[jira] [Updated] (YARN-8040) [UI2] yarn new ui web-app does not respect current pathname for REST api

[ https://issues.apache.org/jira/browse/YARN-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-8040: -- Attachment: YARN-8040.001.patch > [UI2] yarn new ui web-app does not respect current pathname for REST api >

[jira] [Created] (YARN-8040) [UI2] yarn new ui web-app does not respect current pathname for REST api

Sunil G created YARN-8040: - Summary: [UI2] yarn new ui web-app does not respect current pathname for REST api Key: YARN-8040 URL: https://issues.apache.org/jira/browse/YARN-8040 Project: Hadoop YARN

[jira] [Commented] (YARN-7461) DominantResourceCalculator#ratio calculation problem when right resource contains zero value

[ https://issues.apache.org/jira/browse/YARN-7461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402037#comment-16402037 ] Sunil G commented on YARN-7461: --- When multiple resource types are considered, then its possible that one such

[jira] [Commented] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397388#comment-16397388 ] Sunil G commented on YARN-7494: --- This was a bit due. Sorry for the delay. Updated as per comments. However

[jira] [Updated] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7494: -- Attachment: YARN-7494.003.patch > Add muti node lookup support for better placement >

[jira] [Updated] (YARN-8022) ResourceManager UI cluster/app/ page fails to render

[ https://issues.apache.org/jira/browse/YARN-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-8022: -- Affects Version/s: (was: 3.2.0) (was: 3.1.0) Target Version/s: 3.1.0 >

[jira] [Commented] (YARN-8008) Admin command to manage global placement constraints

[ https://issues.apache.org/jira/browse/YARN-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392317#comment-16392317 ] Sunil G commented on YARN-8008: --- [~cheersyang] I cancelled patch as patch was not there.   One quick

[jira] [Commented] (YARN-4781) Support intra-queue preemption for fairness ordering policy.

[ https://issues.apache.org/jira/browse/YARN-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391688#comment-16391688 ] Sunil G commented on YARN-4781: --- [~eepayne] Thanks for the reply. Yes, this makes sense for me. I will take

[jira] [Comment Edited] (YARN-7944) [UI2] Remove master node link from headers of application pages

[ https://issues.apache.org/jira/browse/YARN-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391673#comment-16391673 ] Sunil G edited comment on YARN-7944 at 3/8/18 6:23 PM: --- Thanks [~yeshavora] for the

[jira] [Commented] (YARN-7944) [UI2] Remove master node link from headers of application pages

[ https://issues.apache.org/jira/browse/YARN-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391673#comment-16391673 ] Sunil G commented on YARN-7944: --- Thanks [~leftnoteasy]. Committed to trunk and branch-3.1 > [UI2] Remove

[jira] [Updated] (YARN-7944) [UI2] Remove master node link from headers of application pages

[ https://issues.apache.org/jira/browse/YARN-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7944: -- Summary: [UI2] Remove master node link from headers of application pages (was: Remove master node link from

[jira] [Commented] (YARN-7975) Add an optional arg to yarn cluster -list-node-labels to list nodes collection partitioned by labels

[ https://issues.apache.org/jira/browse/YARN-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389327#comment-16389327 ] Sunil G commented on YARN-7975: --- [~shenyinjie], could u pls write some UT cases to verify the case which you

[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=16389324#comment-16389324 ] Sunil G commented on YARN-8000: --- Yes. As mentioned by [~gsaha], if the data is published to ATS correct, UI

[jira] [Commented] (YARN-4781) Support intra-queue preemption for fairness ordering policy.

[ https://issues.apache.org/jira/browse/YARN-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389289#comment-16389289 ] Sunil G commented on YARN-4781: --- Thanks [~eepayne] for bringing this thread alive.. bq.Then, while all 4

[jira] [Commented] (YARN-7944) Remove master node link from headers of application pages

[ https://issues.apache.org/jira/browse/YARN-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383054#comment-16383054 ] Sunil G commented on YARN-7944: --- +1. Committing shortly. > Remove master node link from headers of

[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=16383050#comment-16383050 ] Sunil G commented on YARN-7957: --- Thanks [~gsaha] This makes sense. Filed a Jira under this for UI changes. >

[jira] [Created] (YARN-7993) [UI2] yarn-service page need to consider ServiceState to show stop/delete buttons

Sunil G created YARN-7993: - Summary: [UI2] yarn-service page need to consider ServiceState to show stop/delete buttons Key: YARN-7993 URL: https://issues.apache.org/jira/browse/YARN-7993 Project: Hadoop YARN

[jira] [Updated] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7494: -- Attachment: multi-node-designProposal.png > Add muti node lookup support for better placement >

[jira] [Commented] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382377#comment-16382377 ] Sunil G commented on YARN-7494: --- Updated v2 patch as per design proposal updated as

[jira] [Updated] (YARN-7494) Add muti node lookup support for better placement

[ https://issues.apache.org/jira/browse/YARN-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7494: -- Attachment: YARN-7494.002.patch > Add muti node lookup support for better placement >

[jira] [Commented] (YARN-7637) GPU volume creation command fails when work preserving is disabled at NM

[ https://issues.apache.org/jira/browse/YARN-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16382317#comment-16382317 ] Sunil G commented on YARN-7637: --- Thanks, i ll commit today. > GPU volume creation command fails when work

[jira] [Commented] (YARN-7989) Yarn ui2 configuration tables have the same search and pagination instances

[ https://issues.apache.org/jira/browse/YARN-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381729#comment-16381729 ] Sunil G commented on YARN-7989: --- Thanks. Looks good to me. +1 pending jenkins. > Yarn ui2 configuration

[jira] [Commented] (YARN-7989) Yarn ui2 configuration tables have the same search and pagination instances

[ https://issues.apache.org/jira/browse/YARN-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381700#comment-16381700 ] Sunil G commented on YARN-7989: --- Added you as a contributor and assigned issue to you. Thanks for the patch.

[jira] [Assigned] (YARN-7989) Yarn ui2 configuration tables have the same search and pagination instances

[ https://issues.apache.org/jira/browse/YARN-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-7989: - Assignee: Tarun Parimi > Yarn ui2 configuration tables have the same search and pagination instances >

[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications

[ https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381591#comment-16381591 ] Sunil G commented on YARN-5028: --- Addendum patch looks fine. +1 pending jenkins. > RMStateStore should trim

[jira] [Commented] (YARN-7159) Normalize unit of resource objects in RM and avoid to do unit conversion in critical path

[ https://issues.apache.org/jira/browse/YARN-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380040#comment-16380040 ] Sunil G commented on YARN-7159: --- This is pending for a bit. [~templedf], could u pls help to check latest

[jira] [Commented] (YARN-5592) Add support for dynamic resource updates with multiple resource types

[ https://issues.apache.org/jira/browse/YARN-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380038#comment-16380038 ] Sunil G commented on YARN-5592: --- [~maniraj...@gmail.com] As i can see, {{updateNodeResource}} supports adding

[jira] [Commented] (YARN-5590) Add support for increase and decrease of container resources with resource profiles

[ https://issues.apache.org/jira/browse/YARN-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380031#comment-16380031 ] Sunil G commented on YARN-5590: --- [~maniraj...@gmail.com] We have to extend from 2 resources to all resources

[jira] [Commented] (YARN-3153) Capacity Scheduler max AM resource limit for queues is defined as percentage but used as ratio

[ https://issues.apache.org/jira/browse/YARN-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380029#comment-16380029 ] Sunil G commented on YARN-3153: --- [~maniraj...@gmail.com] Since we are looking for a deprecation of

[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=16378104#comment-16378104 ] Sunil G commented on YARN-7957: --- yes. service should be at correct state like RUNNING (when service is

[jira] [Updated] (YARN-7856) Validate Node Attributes from NM

[ https://issues.apache.org/jira/browse/YARN-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7856: -- Summary: Validate Node Attributes from NM (was: Validation node attributes in NM) > Validate Node Attributes

[jira] [Commented] (YARN-7637) GPU volume creation command fails when work preserving is disabled at NM

[ https://issues.apache.org/jira/browse/YARN-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377155#comment-16377155 ] Sunil G commented on YARN-7637: --- Looks fine , committing shortly. > GPU volume creation command fails when

[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=16377132#comment-16377132 ] Sunil G commented on YARN-7957: --- We need to have a new field for this and use ServiceState enum. And UI can

[jira] [Commented] (YARN-7856) Validation node attributes in NM

[ https://issues.apache.org/jira/browse/YARN-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376597#comment-16376597 ] Sunil G commented on YARN-7856: --- Changes looks fine to me. i can commit this later today > Validation node

[jira] [Commented] (YARN-7965) NodeAttributeManager add/get API is not working properly

[ https://issues.apache.org/jira/browse/YARN-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376435#comment-16376435 ] Sunil G commented on YARN-7965: --- Thanks [~cheersyang]. Missed that, thanks for adding some more cases. I

[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=16375289#comment-16375289 ] Sunil G commented on YARN-7957: --- I think if we have service state which is similar to YarnApplicationState,

[jira] [Commented] (YARN-5151) [YARN-3368] Support kill application from new YARN UI

[ https://issues.apache.org/jira/browse/YARN-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374563#comment-16374563 ] Sunil G commented on YARN-5151: --- There are some related changes happening in YARN-7957, so we are discussing

[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=16374561#comment-16374561 ] Sunil G commented on YARN-7957: --- It seems GET api to check service status was never used in UI. UI was

[jira] [Commented] (YARN-7944) Remove master node link from headers of application pages

[ https://issues.apache.org/jira/browse/YARN-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374233#comment-16374233 ] Sunil G commented on YARN-7944: --- [~yeshavora] Are we using masterNodeURL or container log url anywhere else?

[jira] [Updated] (YARN-7949) [UI2] ArtifactsId should not be a compulsory field for new service

[ https://issues.apache.org/jira/browse/YARN-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7949: -- Summary: [UI2] ArtifactsId should not be a compulsory field for new service (was: ArtifactsId should not be a

[jira] [Updated] (YARN-7675) [UI2] Support loading pre-2.8 version /scheduler REST response for queue page

[ https://issues.apache.org/jira/browse/YARN-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7675: -- Summary: [UI2] Support loading pre-2.8 version /scheduler REST response for queue page (was: The new UI won't

[jira] [Commented] (YARN-7637) GPU volume creation command fails when work preserving is disabled at NM

[ https://issues.apache.org/jira/browse/YARN-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374071#comment-16374071 ] Sunil G commented on YARN-7637: --- Change looks straight forward to me. +1 Pending jenkins. > GPU volume

[jira] [Commented] (YARN-7949) ArtifactsId should not be a compulsory field for new service

[ https://issues.apache.org/jira/browse/YARN-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373958#comment-16373958 ] Sunil G commented on YARN-7949: --- Looks good. Committing shortly. > ArtifactsId should not be a compulsory

[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=16373930#comment-16373930 ] Sunil G commented on YARN-7957: --- Thanks [~gsaha]. I ll check this api and see how we can integrate. > Yarn

[jira] [Updated] (YARN-6858) Attribute Manager to store and provide node attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-6858: -- Summary: Attribute Manager to store and provide node attributes in RM (was: Attribute Manager to store and

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373794#comment-16373794 ] Sunil G commented on YARN-6858: --- Thanks [~Naganarasimha] . Looks good. Committing. [~bibinchundatt], is it

[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=16373085#comment-16373085 ] Sunil G commented on YARN-7957: --- Currently from YARN App states, we can come to know whether app is stopped

[jira] [Updated] (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:all-tabpanel ] Sunil G updated YARN-7957: -- Attachment: YARN-7957.01.patch > Yarn service delete option disappears after stopping application >

[jira] [Assigned] (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:all-tabpanel ] Sunil G reassigned YARN-7957: - Assignee: Sunil G > Yarn service delete option disappears after stopping application >

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372754#comment-16372754 ] Sunil G commented on YARN-6858: --- +1 Committing later today if no objections. > Attribute Manager to store

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372522#comment-16372522 ] Sunil G commented on YARN-6858: --- Yes. +1. pending jenkins. > Attribute Manager to store and provide the

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372454#comment-16372454 ] Sunil G commented on YARN-6858: --- Hi [~Naganarasimha], javadoc error seems valid and one test case failure

[jira] [Commented] (YARN-7871) Node attributes reporting from NM to RM

[ https://issues.apache.org/jira/browse/YARN-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371815#comment-16371815 ] Sunil G commented on YARN-7871: --- Make sense, with this assumption, is this patch good to go in based on your

[jira] [Commented] (YARN-7856) Validation node attributes in NM

[ https://issues.apache.org/jira/browse/YARN-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371814#comment-16371814 ] Sunil G commented on YARN-7856: --- Thanks [~cheersyang]   Few comments. 1. {{equals}} could u pls check a

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371805#comment-16371805 ] Sunil G commented on YARN-6858: --- [~Naganarasimha] Could u pls check [~bibinchundatt]'s comments so that we

[jira] [Commented] (YARN-7949) ArtifactsId should not be a compulsory field for new service

[ https://issues.apache.org/jira/browse/YARN-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371469#comment-16371469 ] Sunil G commented on YARN-7949: --- [~yeshavora] cud u pls submit patch for jenkins. > ArtifactsId should not

[jira] [Commented] (YARN-7223) Document GPU isolation feature

[ https://issues.apache.org/jira/browse/YARN-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371000#comment-16371000 ] Sunil G commented on YARN-7223: --- Looks fine, committing shortly if no objections. > Document GPU isolation

[jira] [Commented] (YARN-7947) Capacity Scheduler intra-queue preemption can NPE for non-schedulable apps

[ https://issues.apache.org/jira/browse/YARN-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369973#comment-16369973 ] Sunil G commented on YARN-7947: --- Thanks [~eepayne] for the finding and the patch.  Looks good to me,

[jira] [Commented] (YARN-5028) RMStateStore should trim down app state for completed applications

[ https://issues.apache.org/jira/browse/YARN-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369091#comment-16369091 ] Sunil G commented on YARN-5028: --- Thanks [~grepas]. Thats a really good change. Does this mean we have to

[jira] [Commented] (YARN-7223) Document GPU isolation feature

[ https://issues.apache.org/jira/browse/YARN-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368854#comment-16368854 ] Sunil G commented on YARN-7223: --- Thanks [~leftnoteasy]. Few comments 1. Under prerequisites, "(When Docker

[jira] [Commented] (YARN-7292) Retrospect Resource Profile Behavior for overriding capability

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366709#comment-16366709 ] Sunil G commented on YARN-7292: --- Sorry [~leftnoteasy], I missed that we cut branch-3.1. Committed to

[jira] [Updated] (YARN-7292) Retrospect Resource Profile Behavior for overriding capability

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7292: -- Target Version/s: 3.1.0, 3.2.0 (was: 3.1.0) > Retrospect Resource Profile Behavior for overriding capability >

[jira] [Updated] (YARN-7292) Retrospect Resource Profile Behavior for overriding capability

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7292: -- Summary: Retrospect Resource Profile Behavior for overriding capability (was: Revisit Resource Profile

[jira] [Commented] (YARN-7292) Revisit Resource Profile Behavior

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16366556#comment-16366556 ] Sunil G commented on YARN-7292: --- +1 committing shortly. > Revisit Resource Profile Behavior >

[jira] [Commented] (YARN-7328) ResourceUtils allows yarn.nodemanager.resource-types.memory-mb and .vcores to override yarn.nodemanager.resource.memory-mb and .cpu-vcores

[ https://issues.apache.org/jira/browse/YARN-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365565#comment-16365565 ] Sunil G commented on YARN-7328: --- jenkins seems fine. I could help commit this tomorrow if no objections. cc/

[jira] [Commented] (YARN-7920) Cleanup configuration of PlacementConstraints

[ https://issues.apache.org/jira/browse/YARN-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364248#comment-16364248 ] Sunil G commented on YARN-7920: --- I think a name like {{placement-processor}} seems more simple for now. We

[jira] [Commented] (YARN-7574) Add support for Node Labels on Auto Created Leaf Queue Template

[ https://issues.apache.org/jira/browse/YARN-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364225#comment-16364225 ] Sunil G commented on YARN-7574: --- Thanks [~suma.shivaprasad] for the patch. Few comments 1. {{//map of

[jira] [Commented] (YARN-7789) Should fail RM if 3rd resource type is configured but RM uses DefaultResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363383#comment-16363383 ] Sunil G commented on YARN-7789: --- Its my bad. I see that its failing for other tests as well. I ll raise a

[jira] [Updated] (YARN-7925) Some NPE errors caused a display errors when setting node labels

[ https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7925: -- Priority: Blocker (was: Major) > Some NPE errors caused a display errors when setting node labels >

[jira] [Commented] (YARN-7925) Some NPE errors caused a display errors when setting node labels

[ https://issues.apache.org/jira/browse/YARN-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361981#comment-16361981 ] Sunil G commented on YARN-7925: --- Thanks [~lingjinjiang] This is a problem. I checked patch. 1. 

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361971#comment-16361971 ] Sunil G commented on YARN-6858: --- Thanks [~Naganarasimha] . In general patch looks fine to me. Some Minor

[jira] [Commented] (YARN-7789) Should fail RM if 3rd resource type is configured but RM uses DefaultResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361955#comment-16361955 ] Sunil G commented on YARN-7789: --- Patch looks fine to me , but test case failure seems related. Could you

[jira] [Commented] (YARN-7292) Revisit Resource Profile Behavior

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361948#comment-16361948 ] Sunil G commented on YARN-7292: --- Thanks [~leftnoteasy]. I am not very sure about that option

[jira] [Comment Edited] (YARN-7292) Revisit Resource Profile Behavior

[ https://issues.apache.org/jira/browse/YARN-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361948#comment-16361948 ] Sunil G edited comment on YARN-7292 at 2/13/18 8:00 AM: Thanks [~leftnoteasy]. I am

[jira] [Commented] (YARN-7920) Cleanup configuration of PlacementConstraints

[ https://issues.apache.org/jira/browse/YARN-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361907#comment-16361907 ] Sunil G commented on YARN-7920: --- Thanks [~leftnoteasy] for the patch.  Refactoring looks fine to me. Few

[jira] [Commented] (YARN-7829) Rebalance UI2 cluster overview page

[ https://issues.apache.org/jira/browse/YARN-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361754#comment-16361754 ] Sunil G commented on YARN-7829: --- I would like to get this in sooner. [~eyang] could you please check whether

[jira] [Commented] (YARN-7675) The new UI won't load for pre 2.8 Hadoop versions because queueCapacitiesByPartition is missing from the scheduler API

[ https://issues.apache.org/jira/browse/YARN-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361755#comment-16361755 ] Sunil G commented on YARN-7675: --- Sorry [~GergelyNovak]. I missed the same. Committing this patch shortly and

[jira] [Commented] (YARN-7881) Add Log Aggregation Status API to the RM Webservice

[ https://issues.apache.org/jira/browse/YARN-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361751#comment-16361751 ] Sunil G commented on YARN-7881: --- Thanks [~GergelyNovak] /apps/\{appid}/logaggregationstatus looks a cleaner

[jira] [Commented] (YARN-6858) Attribute Manager to store and provide the attributes in RM

[ https://issues.apache.org/jira/browse/YARN-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360356#comment-16360356 ] Sunil G commented on YARN-6858: --- Thanks [~Naganarasimha] for the patch. Few comments. 1. {{public abstract

[jira] [Updated] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7827: -- Fix Version/s: 3.1.0 > Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404 >

[jira] [Commented] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357948#comment-16357948 ] Sunil G commented on YARN-7827: --- YARN-7912 is raised to handle KNOX scenario. > Stop and Delete Yarn Service

[jira] [Created] (YARN-7912) While launching Native Service app from UI, consider service owner name from user.name query parameter

Sunil G created YARN-7912: - Summary: While launching Native Service app from UI, consider service owner name from user.name query parameter Key: YARN-7912 URL: https://issues.apache.org/jira/browse/YARN-7912

[jira] [Commented] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357926#comment-16357926 ] Sunil G commented on YARN-7827: --- Thanks [~eyang] bq.It can be refined to an ajax call to resource manager to

[jira] [Commented] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356692#comment-16356692 ] Sunil G commented on YARN-7827: --- Thanks [~eyang]. I changed hadoop.http.cross-origin.allowed-methods to add

[jira] [Commented] (YARN-7906) mvn site fails

[ https://issues.apache.org/jira/browse/YARN-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356583#comment-16356583 ] Sunil G commented on YARN-7906: --- Thanks [~ajisakaa]. Patch looks fine to me. I found few other package.info

[jira] [Commented] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355291#comment-16355291 ] Sunil G commented on YARN-7827: --- # user.name will be asked to user while submitting a new service. user can

[jira] [Updated] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7827: -- Attachment: YARN-7827.002.patch > Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404 >

[jira] [Updated] (YARN-7827) Stop and Delete Yarn Service from RM UI fails with HTTP ERROR 404

[ https://issues.apache.org/jira/browse/YARN-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7827: -- Attachment: Screen Shot 2018-02-07 at 3.51.54 PM.png > Stop and Delete Yarn Service from RM UI fails with HTTP

[jira] [Commented] (YARN-7856) Validation node attributes in NM

[ https://issues.apache.org/jira/browse/YARN-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355281#comment-16355281 ] Sunil G commented on YARN-7856: --- In general approach seems fine. I ll take a closer look. Thanks

[jira] [Commented] (YARN-7871) Node attributes reporting from NM to RM

[ https://issues.apache.org/jira/browse/YARN-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355204#comment-16355204 ] Sunil G commented on YARN-7871: --- Thanks [~cheersyang] Some comments in general: # With this patch, NM could

[jira] [Commented] (YARN-7728) Expose container preemptions related information in Capacity Scheduler queue metrics

[ https://issues.apache.org/jira/browse/YARN-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354019#comment-16354019 ] Sunil G commented on YARN-7728: --- +1 on this patch. Sorry [~eepayne], I missed this earlier. If you have

[jira] [Updated] (YARN-7866) [UI2] Error to be displayed correctly while accessing kerberized cluster without kinit

[ https://issues.apache.org/jira/browse/YARN-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7866: -- Summary: [UI2] Error to be displayed correctly while accessing kerberized cluster without kinit (was: [UI2]

[jira] [Updated] (YARN-7850) [UI2] Log Aggregation status to be displayed in Application Page

[ https://issues.apache.org/jira/browse/YARN-7850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7850: -- Summary: [UI2] Log Aggregation status to be displayed in Application Page (was: New UI does not show status for

[jira] [Assigned] (YARN-5848) public/crossdomain.xml is problematic

[ https://issues.apache.org/jira/browse/YARN-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-5848: - Assignee: Sunil G > public/crossdomain.xml is problematic > - > >

[jira] [Commented] (YARN-5848) public/crossdomain.xml is problematic

[ https://issues.apache.org/jira/browse/YARN-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353649#comment-16353649 ] Sunil G commented on YARN-5848: --- Makes sense. There are two files and one in the

[jira] [Updated] (YARN-5848) public/crossdomain.xml is problematic

[ https://issues.apache.org/jira/browse/YARN-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-5848: -- Attachment: YARN-5848.001.patch > public/crossdomain.xml is problematic > -

[jira] [Commented] (YARN-7860) Fix UT failure TestRMWebServiceAppsNodelabel#testAppsRunning

[ https://issues.apache.org/jira/browse/YARN-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16353631#comment-16353631 ] Sunil G commented on YARN-7860: --- Sorry [~cheersyang]. Somehow I missed this earlier. Could you please help to

[jira] [Updated] (YARN-7860) Fix UT failure TestRMWebServiceAppsNodelabel#testAppsRunning

[ https://issues.apache.org/jira/browse/YARN-7860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7860: -- Attachment: YARN-7860.001.patch > Fix UT failure TestRMWebServiceAppsNodelabel#testAppsRunning >

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