[jira] [Updated] (YARN-5698) [YARN-3368] Launch new YARN UI under hadoop web app port

[ https://issues.apache.org/jira/browse/YARN-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-5698: -- Attachment: YARN-5698-YARN-3368.0003.patch Updating new patch after fixing test case. > [YARN-3368] Launch new

[jira] [Commented] (YARN-5704) Provide config knobs to control enabling/disabling new/work in progress features in container-executor

[ https://issues.apache.org/jira/browse/YARN-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551296#comment-15551296 ] Sidharta Seethana commented on YARN-5704: - [~aw] As you can see from the patch, most of the changes

[jira] [Commented] (YARN-5698) [YARN-3368] Launch new YARN UI under hadoop web app port

[ https://issues.apache.org/jira/browse/YARN-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551319#comment-15551319 ] Hadoop QA commented on YARN-5698: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5677) RM can be in active-active state for an extended period

[ https://issues.apache.org/jira/browse/YARN-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15550993#comment-15550993 ] Karthik Kambatla commented on YARN-5677: The patch looks pretty good. Nice tests. Couple of

[jira] [Commented] (YARN-5453) FairScheduler#update may skip update demand resource of child queue/app if current demand reached maxResource

[ https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551307#comment-15551307 ] Hadoop QA commented on YARN-5453: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551279#comment-15551279 ] Hadoop QA commented on YARN-2009: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5101) YARN_APPLICATION_UPDATED event is parsed in ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with reversed order

[ https://issues.apache.org/jira/browse/YARN-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5101: Target Version/s: 2.8.0 > YARN_APPLICATION_UPDATED event is parsed in >

[jira] [Commented] (YARN-5453) FairScheduler#update may skip update demand resource of child queue/app if current demand reached maxResource

[ https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551422#comment-15551422 ] sandflee commented on YARN-5453: Hi, [~kasha], patch updated, failed test could run pass locally seems not

[jira] [Commented] (YARN-5699) Retrospect container entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551391#comment-15551391 ] Rohith Sharma K S commented on YARN-5699: - I think this is the time to decide should we support

[jira] [Commented] (YARN-5698) [YARN-3368] Launch new YARN UI under hadoop web app port

[ https://issues.apache.org/jira/browse/YARN-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551365#comment-15551365 ] Sunil G commented on YARN-5698: --- [~leftnoteasy], kindly help to check. > [YARN-3368] Launch new YARN UI

[jira] [Commented] (YARN-5388) MAPREDUCE-6719 requires changes to DockerContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551508#comment-15551508 ] Varun Vasudev commented on YARN-5388: - I'm in favour of removing DockerContainerExecutor but it should

[jira] [Commented] (YARN-5025) Container move (relocation) between nodes

[ https://issues.apache.org/jira/browse/YARN-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551451#comment-15551451 ] ASF GitHub Bot commented on YARN-5025: -- GitHub user szape opened a pull request:

[jira] [Updated] (YARN-5556) Support for deleting queues without requiring a RM restart

[ https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-5556: Attachment: YARN-5556.v1.002.patch Hi [~xgong], i have updated the patch with delete for

[jira] [Commented] (YARN-5156) YARN_CONTAINER_FINISHED of YARN_CONTAINERs will always have running state

[ https://issues.apache.org/jira/browse/YARN-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551970#comment-15551970 ] Rohith Sharma K S commented on YARN-5156: - Alternatively eventfilter works fine. Parser need to

[jira] [Updated] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5699: Attachment: 0002-YARN-5699.YARN-5355.patch > Retrospect yarn entity fields which are

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552048#comment-15552048 ] Rohith Sharma K S commented on YARN-5699: - Updated patch by reverting changes made in

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551737#comment-15551737 ] Hadoop QA commented on YARN-5699: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Resolved] (YARN-5571) [Atsv2] Query App REST endpoing need not to expose queryParams such userId/flowname/flowrunid

[ https://issues.apache.org/jira/browse/YARN-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-5571. - Resolution: Won't Fix As per the discussion, these params are for faster look up of

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551803#comment-15551803 ] Naganarasimha G R commented on YARN-5699: - There was a detailed discussion on this and then we

[jira] [Updated] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5699: Attachment: 0001-YARN-5699.YARN-5355.patch updating same patch to branch YARN-5355 >

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551786#comment-15551786 ] Rohith Sharma K S commented on YARN-5699: - bq. Is this intentional ? yes, because the same

[jira] [Commented] (YARN-5156) YARN_CONTAINER_FINISHED of YARN_CONTAINERs will always have running state

[ https://issues.apache.org/jira/browse/YARN-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551901#comment-15551901 ] Varun Saxena commented on YARN-5156: [~rohithsharma], as per current code, container state can either

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551926#comment-15551926 ] Hadoop QA commented on YARN-5699: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5699: Summary: Retrospect yarn entity fields which are publishing in events info fields. (was:

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551754#comment-15551754 ] Varun Saxena commented on YARN-5699: [~rohithsharma], thanks for the patch. In the patch I see you have

[jira] [Updated] (YARN-5571) [Atsv2] Query App REST endpoint need not to expose queryParams such userId/flowname/flowrunid

[ https://issues.apache.org/jira/browse/YARN-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-5571: Summary: [Atsv2] Query App REST endpoint need not to expose queryParams such

[jira] [Updated] (YARN-5699) Retrospect container entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5699: Attachment: 0001-YARN-5699.patch Updated the patch with following changes. Application : #

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551812#comment-15551812 ] Naganarasimha G R commented on YARN-5699: - Had missed YARN-5156 let me check how to include that

[jira] [Commented] (YARN-5156) YARN_CONTAINER_FINISHED of YARN_CONTAINERs will always have running state

[ https://issues.apache.org/jira/browse/YARN-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551837#comment-15551837 ] Rohith Sharma K S commented on YARN-5156: - After YARN-4129, publishing container info from RM is

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551908#comment-15551908 ] Varun Saxena commented on YARN-5699: bq. Otherwise we miss the this information else container_state

[jira] [Comment Edited] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552593#comment-15552593 ] Varun Saxena edited comment on YARN-5585 at 10/6/16 5:30 PM: - bq. Given

[jira] [Commented] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552696#comment-15552696 ] Sunil G commented on YARN-2009: --- HI [~eepayne] Thanks for sharing the details of the usecase .I have checked

[jira] [Updated] (YARN-5677) RM can be in active-active state for an extended period

[ https://issues.apache.org/jira/browse/YARN-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5677: --- Attachment: YARN-5677.005.patch And here's a quick update to address the checkstyle complaint.

[jira] [Created] (YARN-5714) ContainerExecutor does not order environment map

Remi Catherinot created YARN-5714: - Summary: ContainerExecutor does not order environment map Key: YARN-5714 URL: https://issues.apache.org/jira/browse/YARN-5714 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553303#comment-15553303 ] Eric Payne commented on YARN-2009: -- Thanks, [~sunilg], for your reply. - -

[jira] [Commented] (YARN-5677) RM can be in active-active state for an extended period

[ https://issues.apache.org/jira/browse/YARN-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553123#comment-15553123 ] Hadoop QA commented on YARN-5677: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remi Catherinot updated YARN-5714: -- Description: when dumping the launch container script, environment variables are dumped based

[jira] [Updated] (YARN-4998) Minor cleanup to UGI use in AdminService

[ https://issues.apache.org/jira/browse/YARN-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4998: --- Attachment: YARN-4998.002.patch Rebased > Minor cleanup to UGI use in AdminService >

[jira] [Assigned] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joep Rottinghuis reassigned YARN-4061: -- Assignee: Joep Rottinghuis (was: Li Lu) > [Fault tolerance] Fault tolerant writer for

[jira] [Commented] (YARN-5677) RM can be in active-active state for an extended period

[ https://issues.apache.org/jira/browse/YARN-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552676#comment-15552676 ] Hadoop QA commented on YARN-5677: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552548#comment-15552548 ] Rohith Sharma K S commented on YARN-5585: - bq. Then the entity id order is really the earliest

[jira] [Commented] (YARN-5667) Move HBase backend code in ATS v2 into its separate module

[ https://issues.apache.org/jira/browse/YARN-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552577#comment-15552577 ] Sangjin Lee commented on YARN-5667: --- It now builds cleanly. Thanks. I am still looking into the changes,

[jira] [Commented] (YARN-5556) Support for deleting queues without requiring a RM restart

[ https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552992#comment-15552992 ] Naganarasimha G R commented on YARN-5556: - Triggered the build manually not sure why it dint

[jira] [Commented] (YARN-4206) Add life time value in Application report and web UI

[ https://issues.apache.org/jira/browse/YARN-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552580#comment-15552580 ] Gour Saha commented on YARN-4206: - It will be very helpful from an end-user perspective to provide the

[jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552593#comment-15552593 ] Varun Saxena commented on YARN-5585: bq. Given entities are sorted in ascending order, at some extent

[jira] [Updated] (YARN-5677) RM can be in active-active state for an extended period

[ https://issues.apache.org/jira/browse/YARN-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5677: --- Attachment: YARN-5677.004.patch Patch to address comments. > RM can be in active-active state

[jira] [Created] (YARN-5715) introduce entity prefix for return and sort order

Sangjin Lee created YARN-5715: - Summary: introduce entity prefix for return and sort order Key: YARN-5715 URL: https://issues.apache.org/jira/browse/YARN-5715 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-5715) introduce entity prefix for return and sort order

[ https://issues.apache.org/jira/browse/YARN-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553462#comment-15553462 ] Sangjin Lee commented on YARN-5715: --- During the call, I was thinking we might want to have a separate

[jira] [Updated] (YARN-5715) introduce entity prefix for return and sort order

[ https://issues.apache.org/jira/browse/YARN-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5715: -- Attachment: YARN-5715-YARN-5355.01.patch Moving over the existing patch by [~rohithsharma] from

[jira] [Assigned] (YARN-5715) introduce entity prefix for return and sort order

[ https://issues.apache.org/jira/browse/YARN-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-5715: --- Assignee: Rohith Sharma K S > introduce entity prefix for return and sort order >

[jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552144#comment-15552144 ] Varun Saxena commented on YARN-5585: bq. I was thinking to use same REST API for both by using

[jira] [Comment Edited] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552144#comment-15552144 ] Varun Saxena edited comment on YARN-5585 at 10/6/16 3:01 PM: - bq. I was

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552187#comment-15552187 ] Rohith Sharma K S commented on YARN-5699: - Updated patch also fixes a another bug i.e always NM

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552370#comment-15552370 ] Varun Saxena commented on YARN-5561: Thanks [~rohithsharma] for the patch. # We do not store

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552387#comment-15552387 ] Hadoop QA commented on YARN-5561: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5707) Add manager class for resource profiles

[ https://issues.apache.org/jira/browse/YARN-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552409#comment-15552409 ] Varun Vasudev commented on YARN-5707: - [~wangda] - is it ok if I go ahead and commit the patch? > Add

[jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552438#comment-15552438 ] Sangjin Lee commented on YARN-5585: --- bq. Entity IDs' can be anything. Even a completely alphabetical

[jira] [Commented] (YARN-5713) Update jackson from 1.9.13 to 2.x in hadoop-yarn

[ https://issues.apache.org/jira/browse/YARN-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552436#comment-15552436 ] Hadoop QA commented on YARN-5713: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5561: Attachment: 0001-YARN-5561.YARN-5355.patch > [Atsv2] : Support for ability to retrieve

[jira] [Commented] (YARN-5101) YARN_APPLICATION_UPDATED event is parsed in ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with reversed order

[ https://issues.apache.org/jira/browse/YARN-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552265#comment-15552265 ] Hudson commented on YARN-5101: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10556 (See

[jira] [Moved] (YARN-5713) Update jackson from 1.9.13 to 2.x in hadoop-yarn

[ https://issues.apache.org/jira/browse/YARN-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka moved HADOOP-13677 to YARN-5713: -- Target Version/s: 3.0.0-alpha2 (was: 3.0.0-alpha2)

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552237#comment-15552237 ] Hadoop QA commented on YARN-5699: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552332#comment-15552332 ] Varun Saxena commented on YARN-5699: Thanks [~rohithsharma] for the latest patch. Few comments: # In

[jira] [Commented] (YARN-5699) Retrospect yarn entity fields which are publishing in events info fields.

[ https://issues.apache.org/jira/browse/YARN-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552342#comment-15552342 ] Varun Saxena commented on YARN-5699: For tracking URL part though, AHS will not be enabled with ATSv2