[jira] [Commented] (YARN-4849) [YARN-3368] cleanup code base, integrate web UI related build to mvn, and add licenses.

[ https://issues.apache.org/jira/browse/YARN-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229715#comment-15229715 ] Hadoop QA commented on YARN-4849: - (!) A patch to the testing environment has been detected. Re-executing

[jira] [Updated] (YARN-4849) [YARN-3368] cleanup code base, integrate web UI related build to mvn, and add licenses.

[ https://issues.apache.org/jira/browse/YARN-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4849: - Attachment: YARN-4849-YARN-3368.7.patch Attached ver.7 patch, addressed all comments from [~sunilg].

[jira] [Commented] (YARN-4794) Distributed shell app gets stuck on stopping containers after App completes

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229688#comment-15229688 ] Rohith Sharma K S commented on YARN-4794: - Thanks [~jianhe] for working on the patch. Nice

[jira] [Updated] (YARN-3196) [Compatibility] Make TS next gen be compatible with the current TS

[ https://issues.apache.org/jira/browse/YARN-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3196: -- Labels: (was: yarn-2928-1st-milestone) > [Compatibility] Make TS next gen be compatible with the

[jira] [Commented] (YARN-4821) have a separate NM timeline publishing interval

[ https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229677#comment-15229677 ] Sangjin Lee commented on YARN-4821: --- I think it would be good if we can get this in, as long as it is not

[jira] [Commented] (YARN-3959) Store application related configurations in Timeline Service v2

[ https://issues.apache.org/jira/browse/YARN-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229676#comment-15229676 ] Sangjin Lee commented on YARN-3959: --- I think it would be nice if we can get this in. [~varun_saxena]? >

[jira] [Commented] (YARN-4736) Issues with HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229673#comment-15229673 ] Sangjin Lee commented on YARN-4736: --- Agreed. Please feel free to remove the label. > Issues with

[jira] [Commented] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229595#comment-15229595 ] Naganarasimha G R commented on YARN-3971: - [~bibinchundatt], Thanks for reopening this jira and yes

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229557#comment-15229557 ] Tao Jie commented on YARN-4855: --- [~sunilg] [~leftnoteasy] [~naganarasimha] Thanks for your comments. I agree

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

[ https://issues.apache.org/jira/browse/YARN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229529#comment-15229529 ] Xuan Gong commented on YARN-4886: - +1 lgtm. pending Jenkins > Add HDFS caller context for

[jira] [Commented] (YARN-4726) [Umbrella] Allocation reuse for application upgrades

[ https://issues.apache.org/jira/browse/YARN-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229494#comment-15229494 ] Arun Suresh commented on YARN-4726: --- [~kasha], we have posted a slightly scoped down version of the doc

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

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

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229486#comment-15229486 ] sandflee commented on YARN-4924: thanks [~nroberts], another thought, seems it's not nessesary for NM to

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229478#comment-15229478 ] Sunil G commented on YARN-4855: --- bq.he need not worry whether the node is temporarily down and he can just

[jira] [Reopened] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt reopened YARN-3971: > Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel > recovery >

[jira] [Commented] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229476#comment-15229476 ] Bibin A Chundatt commented on YARN-3971: [~wangda]/[~Naganarasimha] The issue still exists can we

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229472#comment-15229472 ] Sunil G commented on YARN-4925: --- Thanks [~bibinchundatt]. Yes, NODE_LOCAL and OFF-SWITCH should not be set

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229469#comment-15229469 ] Bibin A Chundatt commented on YARN-4925: [~sunilg] and [~Naganarasimha] Thank you for looking into

[jira] [Commented] (YARN-4794) Distributed shell app gets stuck on stopping containers after App completes

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

[jira] [Commented] (YARN-4552) NM ResourceLocalizationService should check and initialize local filecache dir (and log dir) even if NM recover is enabled.

[ https://issues.apache.org/jira/browse/YARN-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229410#comment-15229410 ] Vinod Kumar Vavilapalli commented on YARN-4552: --- [~djp], let me know if you can update this

[jira] [Updated] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-3461: -- Attachment: YARN-3461-YARN-2928.03.patch Posted patch v.3. {quote} i am not sure why earlier code was

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229408#comment-15229408 ] Wangda Tan commented on YARN-4855: -- Thanks [~Tao Jie] and discussions from [~Naganarasimha], [~sunilg].

[jira] [Updated] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4855: - Assignee: Tao Jie > Should check if node exists when replace nodelabels >

[jira] [Commented] (YARN-2694) Ensure only single node labels specified in resource request / host, and node label expression only specified when resourceName=ANY

[ https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229384#comment-15229384 ] Wangda Tan commented on YARN-2694: -- [~zhz], The major reason of only supporting specify node label in

[jira] [Updated] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-2883: - Attachment: YARN-2883-trunk.010.patch Thanks [~asuresh] for the feedback.

[jira] [Commented] (YARN-2694) Ensure only single node labels specified in resource request / host, and node label expression only specified when resourceName=ANY

[ https://issues.apache.org/jira/browse/YARN-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229313#comment-15229313 ] Zhe Zhang commented on YARN-2694: - Hi [~jianhe], [~leftnoteasy], I have a few questions about this change:

[jira] [Updated] (YARN-4794) Distributed shell app gets stuck on stopping containers after App completes

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4794: -- Attachment: YARN-4794.1.patch > Distributed shell app gets stuck on stopping containers after App completes >

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

[ https://issues.apache.org/jira/browse/YARN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229240#comment-15229240 ] Mingliang Liu commented on YARN-4886: - +1 (non-binding) > Add HDFS caller context for

[jira] [Updated] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

[ https://issues.apache.org/jira/browse/YARN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4886: Attachment: YARN-4886-trunk.001.patch Upload a simple patch to add HDFS caller context information for ATS storage.

[jira] [Created] (YARN-4930) Convenience command to perform a work-preserving stop of the nodemanager

Jason Lowe created YARN-4930: Summary: Convenience command to perform a work-preserving stop of the nodemanager Key: YARN-4930 URL: https://issues.apache.org/jira/browse/YARN-4930 Project: Hadoop YARN

[jira] [Commented] (YARN-4930) Convenience command to perform a work-preserving stop of the nodemanager

[ https://issues.apache.org/jira/browse/YARN-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229060#comment-15229060 ] Jason Lowe commented on YARN-4930: -- Currently admins can accomplish the task via a kill -9 of the

[jira] [Commented] (YARN-4630) Remove useless boxing/unboxing code (Hadoop YARN)

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

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229017#comment-15229017 ] Li Lu commented on YARN-3461: - I looked at the patch and felt OK with it. > Consolidate flow name/version/run

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228955#comment-15228955 ] Varun Saxena commented on YARN-3461: Ok... > Consolidate flow name/version/run defaults >

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228937#comment-15228937 ] Naganarasimha G R commented on YARN-4855: - Thanks [~sunilg] for sharing your views, as i mentioned

[jira] [Commented] (YARN-4807) MockAM#waitForState sleep duration is too long

[ https://issues.apache.org/jira/browse/YARN-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228934#comment-15228934 ] Yufei Gu commented on YARN-4807: [~ka...@cloudera.com], you are right. I have a misunderstanding to the

[jira] [Created] (YARN-4929) Fix unit test cases failed because of removing the minimum wait time for attempt.

Yufei Gu created YARN-4929: -- Summary: Fix unit test cases failed because of removing the minimum wait time for attempt. Key: YARN-4929 URL: https://issues.apache.org/jira/browse/YARN-4929 Project: Hadoop

[jira] [Commented] (YARN-4562) YARN WebApp ignores the configuration passed to it for keystore settings

[ https://issues.apache.org/jira/browse/YARN-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228924#comment-15228924 ] Sergey Shelukhin commented on YARN-4562: That is true only if ssl-server.xml is present :) Yes,

[jira] [Commented] (YARN-4810) NM applicationpage cause internal error 500

[ https://issues.apache.org/jira/browse/YARN-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228925#comment-15228925 ] Naganarasimha G R commented on YARN-4810: - Thanks [~bibinchundatt] for the patch, lgtm +1. Will

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228920#comment-15228920 ] Naganarasimha G R commented on YARN-3461: - Thanks for the patch [~sjlee0] few nits in the patch # i

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228878#comment-15228878 ] Marcin Tustin commented on YARN-3216: - [~sunilg] Yeah, YARN-4751 will be VERY nice to have. [~wangda]

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228874#comment-15228874 ] Naganarasimha G R commented on YARN-3216: - Thanks [~marcin.tustin] its a useful doc and yes

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228860#comment-15228860 ] Sunil G commented on YARN-3216: --- Yes. This is helpful. Thanks Marcin. With the recent progress in YARN-4751,

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228853#comment-15228853 ] Wangda Tan commented on YARN-3216: -- Thanks [~marcin.tustin], that is very helpful! >

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228845#comment-15228845 ] Li Lu commented on YARN-3461: - Hi [~varun_saxena] could you please hold a bit so that I can have a look at the

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228839#comment-15228839 ] Marcin Tustin commented on YARN-3216: - I've written up how we worked around this issue here:

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228836#comment-15228836 ] Sunil G commented on YARN-4925: --- Thanks [~Naganarasimha Garla] for the clarification. One final doubt, in

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228824#comment-15228824 ] Naganarasimha G R commented on YARN-4925: - IIUC, [~bibinchundatt]'s solution was to keep the code

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228803#comment-15228803 ] Sunil G commented on YARN-4925: --- Hi [~bibinchundatt] I have one doubt here. After removing this check, now

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228748#comment-15228748 ] Varun Saxena commented on YARN-3461: [~sjlee0], thanks for updating the patch. It looks good to me

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228743#comment-15228743 ] Steve Loughran commented on YARN-4928: -- an absolute {{/tmp}} path is "probably" mapped into a path on

[jira] [Updated] (YARN-4784) fair scheduler: defaultQueueSchedulingPolicy should not accept fifo as a value

[ https://issues.apache.org/jira/browse/YARN-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4784: --- Attachment: YARN-4784.002.patch [~ka...@cloudera.com], I uploaded a new patch. Would you please take a look?

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228684#comment-15228684 ] Sunil G commented on YARN-4855: --- bq.This would be a incompatible change Yes. I agree with [~Naganarasimha

[jira] [Updated] (YARN-4630) Remove useless boxing/unboxing code (Hadoop YARN)

[ https://issues.apache.org/jira/browse/YARN-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4630: Assignee: Kousuke Saruta > Remove useless boxing/unboxing code (Hadoop YARN) >

[jira] [Commented] (YARN-3461) Consolidate flow name/version/run defaults

[ https://issues.apache.org/jira/browse/YARN-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228509#comment-15228509 ] Sangjin Lee commented on YARN-3461: --- The unit test failures should be unrelated. I have seen those

[jira] [Commented] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228520#comment-15228520 ] Eric Badger commented on YARN-4756: --- [~kasha], does my explanation make sense? Do you have any other

[jira] [Commented] (YARN-4624) NPE in PartitionQueueCapacitiesInfo while accessing Schduler UI

[ https://issues.apache.org/jira/browse/YARN-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228492#comment-15228492 ] Sunil G commented on YARN-4624: --- I think this has gone stale. Lets move forward. In YARN-4304, one of the

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228424#comment-15228424 ] Arpit Agarwal commented on YARN-4928: - >From looking at the test cases I think these paths will be only

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228459#comment-15228459 ] Gergely Novák commented on YARN-4928: - No, you're right, this actually does use the local file system.

[jira] [Updated] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4928: - Assignee: Gergely Novák > Some yarn.server.timeline.* tests fail on Windows attempting to use a test >

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228450#comment-15228450 ] Junping Du commented on YARN-4928: -- Oh. Sorry. My previous comments could be misleading... Yes. It is HDFS

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228418#comment-15228418 ] Junping Du commented on YARN-4928: -- Is absolute path "/tmp" works on Windows? I think we don't want test

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228409#comment-15228409 ] Arpit Agarwal commented on YARN-4928: - +1 from me. [~djp], do you have any comments? > Some

[jira] [Updated] (YARN-4457) Cleanup unchecked types for EventHandler

[ https://issues.apache.org/jira/browse/YARN-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4457: --- Attachment: YARN-4457.004.patch Here's a rebased patch that includes all the changes and fixes

[jira] [Updated] (YARN-4630) Remove useless boxing/unboxing code (Hadoop YARN)

[ https://issues.apache.org/jira/browse/YARN-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated YARN-4630: - Attachment: YARN-4630.1.patch [~ajisakaa] Sorry I've overlooked your feedback. I've just fixed

[jira] [Commented] (YARN-4849) [YARN-3368] cleanup code base, integrate web UI related build to mvn, and add licenses.

[ https://issues.apache.org/jira/browse/YARN-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228320#comment-15228320 ] Sunil G commented on YARN-4849: --- Thank you [~leftnoteasy] for the detailed cleaning up and mvn integration

[jira] [Updated] (YARN-4795) ContainerMetrics drops records

[ https://issues.apache.org/jira/browse/YARN-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4795: --- Attachment: YARN-4795.002.patch Nice catch. Here's a rebased patch that addresses the issues.

[jira] [Updated] (YARN-4514) [YARN-3368] Cleanup hardcoded configurations, such as RM/ATS addresses

[ https://issues.apache.org/jira/browse/YARN-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4514: -- Attachment: YARN-4514-YARN-3368.4.patch Thank you [~leftnoteasy] for the comments. Yes, I agree. Its a valid

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228258#comment-15228258 ] Nathan Roberts commented on YARN-4924: -- Sorry [~sandflee]. I missed your comment about updating

[jira] [Updated] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated YARN-4924: - Assignee: (was: Nathan Roberts) > NM recovery race can lead to container not cleaned up >

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228243#comment-15228243 ] Nathan Roberts commented on YARN-4924: -- Thanks [~sandflee], [~jlowe] for the suggestion. I'll work up

[jira] [Assigned] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts reassigned YARN-4924: Assignee: Nathan Roberts > NM recovery race can lead to container not cleaned up >

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228198#comment-15228198 ] Jason Lowe commented on YARN-4924: -- I agree with [~sandflee] that postponing the finish app event dispatch

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228183#comment-15228183 ] Naganarasimha G R commented on YARN-4855: - Thanks for working on the patch, but would like to know

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

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

[jira] [Updated] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

[ https://issues.apache.org/jira/browse/YARN-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergely Novák updated YARN-4928: Attachment: YARN-4928.001.patch > Some yarn.server.timeline.* tests fail on Windows attempting to

[jira] [Created] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

Gergely Novák created YARN-4928: --- Summary: Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon Key: YARN-4928 URL: https://issues.apache.org/jira/browse/YARN-4928

[jira] [Updated] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4855: -- Attachment: YARN-4855.001.patch > Should check if node exists when replace nodelabels >

[jira] [Commented] (YARN-4906) Capture container start/finish time in container metrics

[ https://issues.apache.org/jira/browse/YARN-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227943#comment-15227943 ] Hudson commented on YARN-4906: -- FAILURE: Integrated in Hadoop-trunk-Commit #9566 (See

[jira] [Commented] (YARN-4769) Add support for CSRF header in the dump capacity scheduler logs and kill app buttons in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227904#comment-15227904 ] Varun Vasudev commented on YARN-4769: - [~jianhe] - can you please review? Thanks! > Add support for

[jira] [Commented] (YARN-4901) MockRM should clear the QueueMetrics when it starts

[ https://issues.apache.org/jira/browse/YARN-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227867#comment-15227867 ] Karthik Kambatla commented on YARN-4901: TestNMReconnect fails with FairScheduler because of this.

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227863#comment-15227863 ] Tao Jie commented on YARN-4855: --- [~Naganarasimha], thanks for reply. We are trying to split resource pool for

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

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

[jira] [Commented] (YARN-4927) TestRMHA#testTransitionedToActiveRefreshFail fails when FairScheduler is the default

[ https://issues.apache.org/jira/browse/YARN-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227786#comment-15227786 ] Rohith Sharma K S commented on YARN-4927: - Thanks Karthik for finding out test failure. Even in